PermitSnag
REMOTE · API.PERMITSNAG.COM
Permits and campgrounds in the US, Canada, NZ and Australia: rules, dates, openings and alerts.
Available components
Last scanned (17 hours ago)
Scores higher than 67% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Maps and Location
Recent critical change
Authorization (9 Nov 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (cancel_alert). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1963 tokens (~218/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 9 Nov 26 −7
- Authorization: partial → fail ▼ critical
- Stability: 0.97 → pass security
- New tool “cancel_alert”, which the server declares destructive security
- Tool “check_availability” rewrote its description, which is the text the model reads security
- Tool “get_booking_link” rewrote its description, which is the text the model reads security
- Tool “get_campground_details” rewrote its description, which is the text the model reads security
- Tool “get_permit_details” rewrote its description, which is the text the model reads security
- Tool “search_campgrounds” rewrote its description, which is the text the model reads security
- Tool “search_permits” rewrote its description, which is the text the model reads security
- Schema quality: 192 → 218 ▼ functional
- New tool “create_alert” functional
- New tool “list_my_alerts” functional
- “search_campgrounds” added an optional parameter “country” cosmetic
- “search_campgrounds” added an optional parameter “region” cosmetic
- “search_permits” added an optional parameter “country” cosmetic
- “search_permits” added an optional parameter “region” cosmetic
- “search_campgrounds” reworded the description of “state” cosmetic
- “search_permits” reworded the description of “state” cosmetic
- Tool “get_campground_details” changed its title: US campground details → Campground details cosmetic
- Tool “get_permit_details” changed its title: US backcountry permit rules and dates → Backcountry permit rules and dates cosmetic
- Tool “search_campgrounds” changed its title: Search US campgrounds → Search campgrounds cosmetic
- Tool “search_permits” changed its title: Search US backcountry and wilderness permits → Search backcountry and wilderness permits cosmetic
- 7 Nov 26 +1
- Endpoint reachability: unreachable → reachable ▲ functional
- 6 Nov 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.80 → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://api.permitsnag.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.permitsnag.com | CN=YR1,O=Let's Encrypt,C=US | 17 Nov 2026 | 15 Feb 2027 | RSA 2048 | SHA256-RSA | 52fa6581bff17293c05f8cff355e5fe0d34 |
| SANs: api.permitsnag.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.permitsnag.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| permitsnag.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.permitsnag.com/mcp | Verified | 400 | |
| http (plaintext) | http://api.permitsnag.com/mcp | HTTPS enforced | 301 | https://api.permitsnag.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cancel_alert Turn off a PermitSnag alert ~98
Turn off one alert in the person's own linked PermitSnag account, by the alert id list_my_alerts gives. PermitSnag stops checking it and sends no more openings for it; it can be turned back on from the website. It never cancels a booking, a permit application or a paid plan. Turning off an alert that is already off changes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| alertId | string | yes | The alert id from list_my_alerts. |
| Name | Type | Req | Description |
|---|---|---|---|
| alert | object | – | – |
| pageUrl | string | – | – |
| reason | string | – | Why the request was refused, as a short code. |
| status | – | yes | – |
No examples provided.
check_availability Check recorded openings for a permit or campground ~352
Shows what PermitSnag has recorded for one backcountry permit or one campground (US, Canada, New Zealand or Australia) over a range of up to 62 days. Answers come from PermitSnag's own stored checks of the booking site, not a live look, and nothing is booked. Each date has one state: observed_opening (an opening seen recently, with when it was last seen), observed_no_match (a recent check that saw no opening, with its time), stale (the newest check is older than staleAfterHours, with its time), unknown (no usable check of that date), unreleased (not on sale yet, by the agency's release rule or the booking site), off_season (outside the agency's published season), closed (closed by the agency) or unsupported (PermitSnag does not check this place). Neither stale nor unknown means sold out. Permit dates are shown as they stood 15 minutes ago. For a permit split into zones or entry points, our checks may cover only some of them, so a date with no opening seen comes back as unknown, never as observed_no_match.
| Name | Type | Req | Description |
|---|---|---|---|
| campground | string | – | The campground id from search_campgrounds. Give this or permit, not both. |
| endDate | string | – | Last date, YYYY-MM-DD, inclusive. Defaults to startDate. The range covers at most 62 days, counting both ends. |
| permit | string | – | The permit id or slug from search_permits. Give this or campground, not both. |
| startDate | string | yes | First date, YYYY-MM-DD, read as the place's own local calendar day (for a campground, the night you arrive). |
| Name | Type | Req | Description |
|---|---|---|---|
| alert | object | – | – |
| checkedAt | string | – | – |
| dates | object | – | – |
| days | array | – | – |
| depth | – | – | – |
| found | – | – | Present, and false, only when nothing matched. |
| freshness | object | – | – |
| partialScope | boolean | – | Permits only: true when our checks may cover only some zones or entry points, so no date is called "no opening". |
| past | – | – | Present only when every asked date has passed. |
| publicDelayMinutes | number | – | Permits only: dates are described as they stood this many minutes ago. |
| scanRoute | – | – | How PermitSnag reaches this permit for cancellation openings: direct, through a zone or starting area, through its entry points, or none. |
| source | – | – | – |
| staleAfterHours | number | – | Hours. A check older than this is never reported as observed; it is reported as stale (or as unknown, when partialScope hides a check that saw no opening). |
| subject | object | – | – |
No examples provided.
create_alert Set up a PermitSnag alert ~358
Set up an opening alert in the person's own linked PermitSnag account, for ONE permit (give permit, startDate, endDate, partySize) or ONE campground (give campground, checkInStart, checkInEnd, nights, and optionally sitesNeeded). PermitSnag then sends the person an alert when a matching opening appears. Use the permit or campground id from search_permits or search_campgrounds. Starting areas, night-by-night plans and groups of trailheads are set up on the website instead. The same request sent twice sets up one alert. It never books, pays or enters a lottery. When the account needs a purchase for this alert, the answer may hold the alert and give payment links for the person to open and pay on a checkout page; the alert then turns on by itself once paid. Nothing is ever charged from this tool.
| Name | Type | Req | Description |
|---|---|---|---|
| campground | string | – | The campground id. Give this or permit, not both. |
| checkInEnd | string | – | Campground alert: the last acceptable check-in day, YYYY-MM-DD. |
| checkInStart | string | – | Campground alert: the first acceptable check-in day, YYYY-MM-DD. |
| endDate | string | – | Permit alert: the last day the person could start, YYYY-MM-DD. |
| nights | integer | – | Campground alert: nights in a row. |
| partySize | integer | – | Permit alert: number of people. |
| permit | string | – | The permit id or slug. Give this or campground, not both. |
| sitesNeeded | integer | – | Campground alert: sites needed together. Default 1. |
| startDate | string | – | Permit alert: the first day the person could start, YYYY-MM-DD. |
| Name | Type | Req | Description |
|---|---|---|---|
| alert | object | – | – |
| holdId | string | – | awaiting_payment only: the held alert. It turns on by itself when one of paymentLinks is paid. |
| linksExpireAt | string | – | awaiting_payment only: when the payment links stop working. |
| pageUrl | string | – | The PermitSnag page for this place. |
| paymentLinks | array | – | – |
| reason | string | – | Why the request was refused, as a short code. |
| status | – | yes | – |
No examples provided.
get_booking_link Booking link for a permit or campground ~265
Returns the link to the official booking page for one backcountry permit or one campground in the US, Canada, New Zealand or Australia. For some permits the link also carries the first date and the number of people you give, but the booking site may not use them, so the person checks or picks the dates and group size on that page. For a campground, the person picks or checks the dates on the booking page. For some places it returns the agency's own page or the PermitSnag page instead of a booking page. It only returns a link and a sentence about it; it does not book, pay or enter a lottery.
| Name | Type | Req | Description |
|---|---|---|---|
| campground | string | – | The campground id. Give this or permit, not both. |
| endDate | string | – | Optional last date, YYYY-MM-DD. Sent in the link for a few booking sites; the site may ignore it. |
| partySize | integer | – | Optional number of people. Sent in the link for some permit booking sites; the site may ignore it. |
| permit | string | – | The permit id or slug. Give this or campground, not both. |
| startDate | string | – | Optional first date, YYYY-MM-DD. Sent in the link for some booking sites; the site may ignore it. |
| Name | Type | Req | Description |
|---|---|---|---|
| datePrefill | – | – | Whether the asked date reaches the booking page. |
| destination | – | – | – |
| executesNothing | – | – | This tool only returns a link. |
| found | – | – | Present, and false, only when nothing matched. |
| providerHomeUrl | string|null | – | Permits only: the booking site's front page, when that is all we can name. |
| subject | object | – | – |
| url | string | – | The page to open. |
No examples provided.
get_campground_details Campground details ~142
Get the details of one campground in the US, Canada, New Zealand or Australia: 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. To set one up in the person's own PermitSnag account, use create_alert (it asks the person to sign in to PermitSnag).
| Name | Type | Req | Description |
|---|---|---|---|
| campground | string | yes | The campground id from search_campgrounds. |
| Name | Type | Req | Description |
|---|---|---|---|
| alert | object | – | – |
| amenities | array | – | – |
| bookingSystem | string | – | – |
| bookingUrl | string|null | – | – |
| checkedAt | string | – | – |
| country | – | – | The country: US, CA (Canada), NZ (New Zealand) or AU (Australia). |
| depth | – | – | site_level: our checks count individual sites. campground_level: the booking system reports the campground as a whole. |
| description | string|null | – | – |
| found | – | – | Present, and false, only when nothing matched. |
| id | string | – | – |
| maxStayNights | integer|null | – | – |
| name | string | – | – |
| pageUrl | string | – | – |
| priceRange | object|null | – | – |
| provider | string | – | – |
| region | string|null | – | Outside the US, the province, state or territory as a slug. |
| releaseRule | object|null | – | When sites go on sale, from the listing itself. |
| reservationWindowDays | integer|null | – | – |
| season | object | – | The agency's season or closure state, with agency words in quoted fields. |
| siteTypes | array | – | – |
| state | string|null | – | The US state; null outside the US. |
| totalSites | integer|null | – | – |
No examples provided.
get_permit_details Backcountry permit rules and dates ~154
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. To set one up in the person's own PermitSnag account, use create_alert (it asks the person to sign in to PermitSnag).
| Name | Type | Req | Description |
|---|---|---|---|
| permit | string | yes | The permit id or slug from search_permits, or its permitsnag.com page URL. |
| Name | Type | Req | Description |
|---|---|---|---|
| agencyDates | array | – | Upcoming dates from an agency source (lottery opens, closes, results, claims). |
| alert | object | – | – |
| checkedAt | string | – | When this answer was composed, ISO 8601. |
| country | – | – | The country: US, CA (Canada), NZ (New Zealand) or AU (Australia). |
| description | string|null | – | – |
| found | – | – | Present, and false, only when nothing matched. |
| groupSizeLimit | integer|null | – | – |
| id | string | – | – |
| issuance | string | – | How the permit is issued, in plain words. |
| name | string | – | – |
| officialUrl | string|null | – | The agency's own permit page. |
| pageUrl | string | – | – |
| park | string|null | – | – |
| region | string|null | – | Outside the US, the province, state or territory as a slug. |
| releaseRules | array | – | The agency schedule for when dates go on sale. |
| scanRoute | – | – | How PermitSnag reaches this permit for cancellation openings: direct, through a zone or starting area, through its entry points, or none. |
| season | object | – | The agency's season or closure state, with agency words in quoted fields. |
| slug | string | – | – |
| usState | string|null | – | The two-letter US state; null outside the US. |
No examples provided.
list_my_alerts Your PermitSnag alerts ~78
List the alerts turned on in the person's own linked PermitSnag account: each permit or campground, its dates, how often PermitSnag checks it and when it was last checked, plus the alert id that cancel_alert needs. Also lists alerts saved by create_alert that are waiting for a payment, with their payment links. Read only.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| awaitingPayment | array | – | Alerts set up here that wait for a payment. Present only when there are some. |
| campgrounds | array | yes | – |
| permits | array | yes | – |
No examples provided.
search_campgrounds Search campgrounds ~248
Find campgrounds in the US, Canada, New Zealand and Australia by name, area, state or province, across Recreation.gov, state and provincial park and national 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. An opening alert is set up with create_alert.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional country: US, CA (Canada), NZ (New Zealand) or AU (Australia). Omit to search all four. |
| limit | integer | – | How many results, 1 to 10. Default 5. |
| query | string | yes | A campground name or area, like "Upper Pines" or "Big Sur". |
| region | string | – | Optional province, state or territory outside the US, by name or abbreviation, like British Columbia, BC, Tasmania or NSW. |
| state | string | – | Optional two-letter US state code, like CA for California. It limits the search to the US. |
| Name | Type | Req | Description |
|---|---|---|---|
| country | string|null | – | The country filter, or null for all four. |
| query | string | yes | – |
| region | string|null | – | The province, state or territory filter outside the US, as a slug, or null. |
| results | array | yes | – |
| state | string|null | yes | The two-letter US state filter, or null. |
No examples provided.
search_permits Search backcountry and wilderness permits ~268
Find backcountry and wilderness permits in the US, Canada, New Zealand and Australia by name, park, trail or area, for hikes, Great Walks, climbs, river and canoe trips and overnight trips in national, state and provincial 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. An opening alert is set up with create_alert.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional country: US, CA (Canada), NZ (New Zealand) or AU (Australia). Omit to search all four. |
| limit | integer | – | How many results, 1 to 10. Default 5. |
| query | string | yes | A permit, trail, park or area name, like "Mount Whitney" or "Enchantments". |
| region | string | – | Optional province, state or territory outside the US, by name or abbreviation, like British Columbia, BC, Tasmania or NSW. |
| state | string | – | Optional two-letter US state code, like CA for California. It limits the search to the US. |
| Name | Type | Req | Description |
|---|---|---|---|
| country | string|null | – | The country filter, or null for all four. |
| query | string | yes | The search as asked. |
| region | string|null | – | The province, state or territory filter outside the US, as a slug, or null. |
| results | array | yes | – |
| state | string|null | yes | The two-letter US state filter, or null. |
No examples provided.
How do I install the PermitSnag MCP server?
PermitSnag is a hosted endpoint at https://api.permitsnag.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.permitsnag.com
claude mcp add --transport http com-permitsnag-permits 'https://api.permitsnag.com/mcp'
What is the PermitSnag MCP server?
PermitSnag is an MCP server listed in the public MCP registry as com.permitsnag/permits. Permits and campgrounds in the US, Canada, NZ and Australia: rules, dates, openings and alerts. This page covers its hosted endpoint (https://api.permitsnag.com/mcp).
Is the PermitSnag MCP server safe to use?
PermitSnag scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the PermitSnag MCP server expose?
PermitSnag exposes 9 tools: search_permits, get_permit_details, search_campgrounds, get_campground_details, check_availability, and 4 more. Their descriptions and schemas cost roughly 1,963 tokens of context every time the server is loaded.
Does the PermitSnag MCP server require authentication?
No. We connected to PermitSnag without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PermitSnag MCP server still maintained?
PermitSnag is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the PermitSnag MCP server?
VerifyMCP ran 13 checks on PermitSnag, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.