Open State: Camping - Parks Canada MCP server
io.github.JCrossman/open-state-camping·v1.0.7Find and prepare Parks Canada reservations while keeping the citizen in control.
0 stars35 downloads/wk
Reviews
Write oneNobody has reviewed Open State: Camping - Parks Canada yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Open State: Camping - Parks Canada tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it
- Code scan1 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 13 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Open State: Camping - Parks Canada compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 92/100
- higher than 95% of 48,255 servers
- Downloads a week
- 35
- more than 25% of 12,191 servers with a package
Install Open State: Camping - Parks Canada in Claude Code, Cursor or VS Code
Runs npx -y @open-state/camping on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add open-state-camping -- npx -y @open-state/camping
What the publisher says
From the Open State: Camping - Parks Canada repository's README, as published. We do not edit it. Read it on GitHub
Open State: Camping — Parks Canada
Part of The Open State, a reference implementation of the Civic Access Protocol. This lets a citizen reach Parks Canada reservations through their own AI assistant, in plain language, while keeping their credentials and their control.
Your services. Your assistant. Your access.
It is a local MCP bundle (.mcpb) you add to your assistant on your own machine. It runs over stdio, searches Parks Canada's public availability, and prepares a booking right up to the payment screen in your own session. It never sees your password or payment details. Session cookies are encrypted on your device; you directly approve consequential actions and pay yourself.
For the binding rules and design, see The Open State: CONSTITUTION.md, AGENTS.md, docs/00-overview.md, docs/01-architecture.md. The verified Parks Canada API contract is in docs/parks-canada-api-findings.md.
What it does
All four Parks Canada booking families — search and book, end-to-end:
Plain-language tools, grouped:
searchsites (with a category of campsite / group / accommodation), searchdayuse, searchbackcountry, getsitedetails, listequipmenttypes, resolve_dates.
- Search / discovery: searchparks, searchpark_availability,
yourself; the session is stored encrypted in a local vault. disconnectaccount, connectionstatus.
- Account (your session): connectaccount opens your own* browser to sign in
then assembles the cart and drives it to the payment screen only after your approval. You review and pay (Constitution Art. 2).
- Booking: prepare_booking shows the exact action in a trusted host form,
and get pinged when a cancellation opens a site.
- Alerts: createalert / listalerts / delete_alert — watch a campground
plain language (fees, change/cancel deadlines and refunds, check-in times, no-shows, and that park entry isn't included). The assistant also surfaces the key deadline and fee right in the booking preview, so you confirm with the terms in front of you.
- Policies: getreservationpolicies — Parks Canada's reservation rules in
Accessibility is the point. Where Parks Canada exposes an accessibility attribute, sites are flagged per-site and filterable (accessible_only); output is written to read cleanly with a screen reader (Constitution Art. 3).
Build
Part of the repo-root pnpm workspace: packages/core (provider, booking cart, availability) and packages/bundle (the MCP server + the .mcpb), on @open-state/kit for the session vault and citizen-driven sign-in.
# at the repository root
pnpm install
pnpm -r buildRun (local, stdio)
node packages/bundle/standalone/server.jsThe server speaks MCP over stdio and waits for an assistant to connect.
Install from npm
Node.js 20 or newer is required. Configure any stdio MCP client to run:
npx --yes @open-state/camping@1.0.7For upgrades, change the pinned version and restart the client. To uninstall, remove the MCP client configuration. Local state is intentionally retained; after disconnecting, delete ~/.open-state-camping to remove alerts and all remaining data. See PRIVACY.md.
Install in Claude Desktop (the .mcpb)
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Open State: Camping - Parks Canada: common questions
- Is Open State: Camping - Parks Canada MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the Open State: Camping - Parks Canada safety report
- How do I install Open State: Camping - Parks Canada?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Open State: Camping - Parks Canada need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Open State: Camping - Parks Canada maintained?
- The last commit was 54 days ago (2026-09-11). The latest release is v1.0.7.
- How does Open State: Camping - Parks Canada compare with other MCP servers?
- safety score 92/100 (higher than 95% of 48,255 servers); downloads a week 35 (more than 25% of 12,191 servers with a package). Full comparison.