# PermitSnag (remote · api.permitsnag.com)

Permits and campgrounds in the US, Canada, NZ and Australia: rules, dates, openings and alerts.

- Trust score: 77/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

> **Recent critical change**: Authorization (2026-11-09). See the changelog below before you install this server.

## Components

- remote · `api.permitsnag.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/com-permitsnag-permits/api.md), [page](https://verifymcp.io/servers/com-permitsnag-permits/api)

## Channel facts

- Endpoint: `https://api.permitsnag.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (cancel_alert).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-permitsnag-permits 'https://api.permitsnag.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-permitsnag-permits": {
      "url": "https://api.permitsnag.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-permitsnag-permits": {
      "type": "http",
      "url": "https://api.permitsnag.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-permitsnag-permits]
url = "https://api.permitsnag.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-permitsnag-permits": {
      "type": "remote",
      "url": "https://api.permitsnag.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-permitsnag-permits --url 'https://api.permitsnag.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-permitsnag-permits:
    url: "https://api.permitsnag.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-permitsnag-permits": {
      "Transport": "http",
      "Url": "https://api.permitsnag.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-permitsnag-permits -t streamable-http -u 'https://api.permitsnag.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-permitsnag-permits": {
      "type": "http",
      "url": "https://api.permitsnag.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-11 (score 77, 0)

- [security] Stability: 0.97 → pass

### 2026-11-10 (score 77, 0)

- [functional] Stability: pass → 0.97

### 2026-11-09 (score 77, −7)

- [critical regression] Authorization: partial → fail
- [security] 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
- [functional regression] Schema quality: 192 → 218
- [functional] New tool “create_alert”
- [functional] New tool “list_my_alerts”
- [cosmetic] “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

### 2026-11-07 (score 84, +1)

- [functional improvement] Endpoint reachability: unreachable → reachable

### 2026-11-06 (score 83, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-04 (score 82, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: 0.80 → unverified
- [security regression] HSTS header: fail → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-11-03 (score 82, +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.

### 2026-11-01 (score 81, +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.

## MCP tools (9)

### `search_permits` (~268 tokens)

Search backcountry and wilderness permits

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.

Input parameters:

- `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, required): 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.

Output parameters:

- `country` (string|null): The country filter, or null for all four.
- `query` (string): The search as asked.
- `region` (string|null): The province, state or territory filter outside the US, as a slug, or null.
- `results` (array)
- `state` (string|null): The two-letter US state filter, or null.

### `get_permit_details` (~154 tokens)

Backcountry permit rules and dates

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).

Input parameters:

- `permit` (string, required): The permit id or slug from search_permits, or its permitsnag.com page URL.

Output parameters:

- `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.

### `search_campgrounds` (~248 tokens)

Search campgrounds

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.

Input parameters:

- `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, required): 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.

Output parameters:

- `country` (string|null): The country filter, or null for all four.
- `query` (string)
- `region` (string|null): The province, state or territory filter outside the US, as a slug, or null.
- `results` (array)
- `state` (string|null): The two-letter US state filter, or null.

### `get_campground_details` (~142 tokens)

Campground details

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).

Input parameters:

- `campground` (string, required): The campground id from search_campgrounds.

Output parameters:

- `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)

### `check_availability` (~352 tokens)

Check recorded openings for a permit or campground

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.

Input parameters:

- `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, required): First date, YYYY-MM-DD, read as the place's own local calendar day (for a campground, the night you arrive).

Output parameters:

- `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)

### `get_booking_link` (~265 tokens)

Booking link for a permit or campground

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.

Input parameters:

- `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.

Output parameters:

- `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.

### `list_my_alerts` (~78 tokens)

Your PermitSnag alerts

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.

Output parameters:

- `awaitingPayment` (array): Alerts set up here that wait for a payment. Present only when there are some.
- `campgrounds` (array)
- `permits` (array)

### `create_alert` (~358 tokens)

Set up a PermitSnag alert

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.

Input parameters:

- `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.

Output parameters:

- `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`

### `cancel_alert` (~98 tokens)

Turn off a PermitSnag alert

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.

Input parameters:

- `alertId` (string, required): The alert id from list_my_alerts.

Output parameters:

- `alert` (object)
- `pageUrl` (string)
- `reason` (string): Why the request was refused, as a short code.
- `status`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-permitsnag-permits/api#diagnostics

## Score history

- 2026-11-21: 77
- 2026-11-20: 77
- 2026-11-19: 77
- 2026-11-18: 77
- 2026-11-17: 77
- 2026-11-16: 77
- 2026-11-15: 77
- 2026-11-14: 77
- 2026-11-13: 77
- 2026-11-12: 77
- 2026-11-11: 77
- 2026-11-10: 77
- 2026-11-09: 77
- 2026-11-08: 84
- 2026-11-07: 84
- 2026-11-06: 83
- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 79
- 2026-10-28: 79
- 2026-10-27: 79
- 2026-10-26: 78
- 2026-10-25: 78
- 2026-10-24: 77
- 2026-10-23: 77

## Common questions

### 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.

## Links

- Remote endpoint: https://api.permitsnag.com/mcp
- Website: https://permitsnag.com/developers
- Changelog RSS feed: https://verifymcp.io/servers/com-permitsnag-permits/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-permitsnag-permits/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-permitsnag-permits/api.json
- HTML version of this page: https://verifymcp.io/servers/com-permitsnag-permits/api
