permitsnag
Registry code: 31cc7da5291f1487
US backcountry permit and campground rules, dates and recorded openings. Read-only, no sign-in.
from a public catalogue that lists it, not from the operator
- endpoint
- https://api.permitsnag.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is permitsnag live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is permitsnag free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does permitsnag have?
- 6 tools: search_permits, search_campgrounds, get_booking_link, check_availability, get_campground_details, get_permit_details.
- Is permitsnag safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 6 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
search_permits unknown never probed
Find US backcountry and wilderness permits by name, park, trail or area, for hikes, climbs, river trips and overnight trips in national parks, national forests and state parks. Use this when someone asks how to get a permit or which permit a trip needs. Returns up to 10 permits with their PermitSnag page and whether PermitSnag scans them for cancellation openings. It does not check dates; use check_availability for that, and get_permit_details for the rules of one permit.
{ "type": "object", "required": [ "query" ], "properties": { "limit": { "type": "integer", "maximum": 10, "minimum": 1, "description": "How many results, 1 to 10. Default 5." }, "query": { "type": "string", "maxLength": 120, "minLength": 2, "description": "A permit, trail, park or area name, like \"Mount Whitney\" or \"Enchantments\"." }, "state": { "type": "string", "pattern": "^[A-Za-z]{2}$", "description": "Optional two-letter US state code to narrow results, like CA." } }, "additionalProperties": false }arguments 26 linessearch_campgrounds unknown never probed
Find campgrounds in the US by name, area or state, across Recreation.gov and state park booking systems. Use this when someone wants a place to camp or asks about a specific campground. Returns up to 10 campgrounds with their PermitSnag page, their booking system, and whether PermitSnag can send an alert when a site opens. It does not check dates; use check_availability for that.
{ "type": "object", "required": [ "query" ], "properties": { "limit": { "type": "integer", "maximum": 10, "minimum": 1, "description": "How many results, 1 to 10. Default 5." }, "query": { "type": "string", "maxLength": 120, "minLength": 2, "description": "A campground name or area, like \"Upper Pines\" or \"Big Sur\"." }, "state": { "type": "string", "pattern": "^[A-Za-z]{2}$", "description": "Optional two-letter US state code to narrow results, like CA." } }, "additionalProperties": false }arguments 26 linesget_booking_link unknown never probed
Get the official booking page for one US backcountry permit or one campground, with the dates filled in where the booking site allows it. Use it when the person is ready to book or apply. It only returns a link and a sentence about it; it does not book, pay or enter a lottery.
{ "type": "object", "properties": { "permit": { "type": "string", "maxLength": 200, "description": "The permit id or slug. Give this or campground, not both." }, "endDate": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "Optional last date, YYYY-MM-DD." }, "partySize": { "type": "integer", "maximum": 60, "minimum": 1, "description": "Optional number of people." }, "startDate": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "Optional first date, YYYY-MM-DD." }, "campground": { "type": "string", "maxLength": 200, "description": "The campground id. Give this or permit, not both." } }, "additionalProperties": false }arguments 32 linescheck_availability unknown 1h ago
Check what PermitSnag has recorded for one US backcountry permit or one campground on specific dates, up to 62 days. Use it when someone asks whether a permit or campsite is open or available on certain dates. Answers come from PermitSnag's own recent checks of the booking site, each with the time it was checked; it is not a live look, and nothing is booked. A date we have not checked recently comes back as unknown, never as sold out. Also says when dates are not on sale yet, out of season or closed.
{ "type": "object", "required": [ "startDate" ], "properties": { "permit": { "type": "string", "maxLength": 200, "description": "The permit id or slug from search_permits. Give this or campground, not both." }, "endDate": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "Last date, YYYY-MM-DD, inclusive. Defaults to startDate. At most 62 days after startDate." }, "startDate": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "First date, YYYY-MM-DD, read as the place's own local calendar day (for a campground, the night you arrive)." }, "campground": { "type": "string", "maxLength": 200, "description": "The campground id from search_campgrounds. Give this or permit, not both." } }, "additionalProperties": false }arguments 29 linesget_campground_details unknown 1h ago
Get the details of one US campground: its booking system, how far ahead sites go on sale, site count and types, stay limits, season and closures. Use it after search_campgrounds, or when the person names a specific campground. Says whether PermitSnag can send an alert when a site opens, and whether our checks count individual sites or only the campground as a whole.
{ "type": "object", "required": [ "campground" ], "properties": { "campground": { "type": "string", "maxLength": 200, "description": "The campground id from search_campgrounds." } }, "additionalProperties": false }arguments 14 linesget_permit_details unknown 1h ago
Get the rules for one US backcountry or wilderness permit: how it is issued (reservation, lottery or in person), its season, lottery and release dates, closures, group size limit, and the official agency page. Use it after search_permits, or when the person names a specific permit. Every date comes from an agency source; a date we cannot source is left out. Says whether PermitSnag can send an alert when the permit opens.
{ "type": "object", "required": [ "permit" ], "properties": { "permit": { "type": "string", "maxLength": 200, "description": "The permit id or slug from search_permits, or its permitsnag.com page URL." } }, "additionalProperties": false }arguments 14 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id31cc7da5291f1487.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/31cc7da5291f1487/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/31cc7da5291f1487?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.