Home / MCP registry index / ca.parksopen/parksopen
Parks Open
ca.parksopen/parksopen in the official MCP registry.
Endpoint https://parksopen.ca/api/mcp.
The registry describes it as: Live BC Parks campsite and day-pass status with freshness and official booking links.
We read its 8 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
parksopen_search_campsites parksopen_park_availability_calendar parksopen_find_open_parks parksopen_check_alerts parksopen_check_weather parksopen_check_day_passes parksopen_park_info parksopen_get_booking_link
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ca-parksopen-parksopen)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.