Skip to content

PermitSnag MCP server

com.permitsnag/permitspermitsnag.comstreamable-httpv1.1.0Scanned

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

9 tools: 1 can delete or cancel things, 1 change things and 7 only read.

Tools: 1 delete, 0 irreversible, 1 write, 7 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the PermitSnag MCP server can do

The PermitSnag MCP server is published by permitsnag.com, a domain the MCP Registry verified. It has 9 tools. It can delete or cancel things (1 tool: cancel_alert) and create or change data (1 tool: create_alert). 7 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 9, 2026, version 1.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Deletes or cancels 1Claude Code: deny
  • cancel_alertTurn off one alert in the person's own linked PermitSnag account, by the alert id list_my_alerts gives.No findings

    Why it is in this group

    • The name "cancel_alert" says "cancel": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Turn off a PermitSnag alert
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
Changes things 1Claude Code: ask
  • create_alertSet 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,…No findings

    Why it is in this group

    • The name "create_alert" says "create": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Set up a PermitSnag alert
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 7Show 7 read-only tools
  • check_availabilityShows 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.No findings

    Why it is in this group

    • The description's first verb is "show": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check recorded openings for a permit or campground
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_campground_detailsGet 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 clo…No findings

    Why it is in this group

    • The name "get_campground_details" says "get": a word for reading.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Campground details
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_permit_detailsGet 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, …No findings

    Why it is in this group

    • The name "get_permit_details" says "get": a word for reading.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Backcountry permit rules and dates
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_my_alertsList 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…No findings

    Why it is in this group

    • The name "list_my_alerts" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Your PermitSnag alerts
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_campgroundsFind 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.No findings

    Why it is in this group

    • The name "search_campgrounds" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Search campgrounds
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_permitsFind 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 overnig…No findings

    Why it is in this group

    • The name "search_permits" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Search backcountry and wilderness permits
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:44 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://api.permitsnag.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://api.permitsnag.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 destructive, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.permitsnag.com/mcp: tools/list returned 9 tools to an anonymous client, including cancel_alert (destructive), create_alert (write)

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • Tools that change things, listed without credentials: 0 to 2
    • RFC 9728 protected resource metadata: none to https://api.permitsnag.com/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://api.permitsnag.com
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 0 -> 2; RFC 9728 protected resource metadata: none -> https://api.permitsnag.com/.well-known/oauth-protected-resource/mcp; Authorization servers: none -> https://…View diff
    • Tools that change things, listed without credentials: 0 to 2
    • RFC 9728 protected resource metadata: none to https://api.permitsnag.com/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://api.permitsnag.com
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no
  2. Tools3 added, 6 changed.+3 added~6 changedView diff

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__permits__search_permits",
      "mcp__permits__get_permit_details",
      "mcp__permits__search_campgrounds",
      "mcp__permits__get_campground_details",
      "mcp__permits__check_availability",
      "mcp__permits__get_booking_link",
      "mcp__permits__list_my_alerts"
    ],
    "ask": [
      "mcp__permits__create_alert"
    ],
    "deny": [
      "mcp__permits__cancel_alert"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as permits. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.permitsnag/permits/verify?hash=f727f36242e87eece901fcf1a8b8e2a7bf82b175f35862ee10e2356deabc458e" | jq -e '.changed == false'

Pinned hash f727f36242e8, from Nov 9, 2026, 19:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.permitsnag/permits/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.permitsnag/permits
[![Anlyon Radar](https://radar.anlyon.com/badge/com.permitsnag/permits.svg)](https://radar.anlyon.com/servers/com.permitsnag/permits)

Source: MCP Registry. Synced Nov 9, 2026, 20:17 UTC.

PermitSnag MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the PermitSnag MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the PermitSnag MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: cancel_alert.

Can the PermitSnag MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the PermitSnag MCP server have?

9 tools: 1 destructive, 1 write, 7 read. cancel_alert, create_alert, search_permits, get_permit_details, search_campgrounds, get_campground_details, check_availability, get_booking_link and 1 more.

Does the PermitSnag MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the PermitSnag MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the PermitSnag MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.