accueil / serveurs / Recherche & Web / com.permitsnag/permits
com.permitsnag/permits
serveur MCP (Model Context Protocol) · permitsnag 1.0.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que com.permitsnag/permits est sûr ?
Au dernier audit MCP Hub, le serveur MCP « com.permitsnag/permits » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 6 outils
- check_availability≈ 1556 tokens
Shows what PermitSnag has recorded for one US backcountry permit or one campground 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.
Paramètres, retour & exemple (4)
Paramètrespermit· string · optionnel
The permit id or slug from search_permits. Give this or campground, not both.endDate· string · optionnel
Last date, YYYY-MM-DD, inclusive. Defaults to startDate. The range covers at most 62 days, counting both ends.startDate· string · requis
First date, YYYY-MM-DD, read as the place's own local calendar day (for a campground, the night you arrive).campground· string · optionnel
The campground id from search_campgrounds. Give this or permit, not both.
Exemple d'appel{"name": "check_availability", "arguments": {"startDate": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"days": [], "past": "texte", "alert": {}, "dates": {}, "depth": "permit_level", "found": "texte", "source": "texte", "subject": {}, "checkedAt": "texte", "freshness": {}, "scanRoute": "direct", "partialScope": true}} - get_booking_link≈ 738 tokens
Returns the link to the official booking page for one US backcountry permit or one campground. 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.
Paramètres, retour & exemple (5)
Paramètrespermit· string · optionnel
The permit id or slug. Give this or campground, not both.endDate· string · optionnel
Optional last date, YYYY-MM-DD. Sent in the link for a few booking sites; the site may ignore it.partySize· integer · optionnel
Optional number of people. Sent in the link for some permit booking sites; the site may ignore it.startDate· string · optionnel
Optional first date, YYYY-MM-DD. Sent in the link for some booking sites; the site may ignore it.campground· string · optionnel
The campground id. Give this or permit, not both.
Exemple d'appel{"name": "get_booking_link", "arguments": {"permit": "texte", "endDate": "texte", "partySize": 1, "startDate": "texte", "campground": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"url": "texte", "found": "texte", "subject": {}, "datePrefill": "applied", "destination": "booking_page", "executesNothing": "texte", "providerHomeUrl": "texte"}} - get_campground_details≈ 1247 tokens
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.
Paramètres, retour & exemple (1)
Paramètrescampground· string · requis
The campground id from search_campgrounds.
Exemple d'appel{"name": "get_campground_details", "arguments": {"campground": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "name": "texte", "alert": {}, "depth": "site_level", "found": "texte", "state": "texte", "season": {}, "pageUrl": "texte", "provider": "texte", "amenities": [], "checkedAt": "texte", "siteTypes": []}} - get_permit_details≈ 1301 tokens
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.
Paramètres, retour & exemple (1)
Paramètrespermit· string · requis
The permit id or slug from search_permits, or its permitsnag.com page URL.
Exemple d'appel{"name": "get_permit_details", "arguments": {"permit": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "name": "texte", "park": "texte", "slug": "texte", "alert": {}, "found": "texte", "season": {}, "pageUrl": "texte", "usState": "texte", "issuance": "texte", "checkedAt": "texte", "scanRoute": "direct"}} - search_campgrounds≈ 525 tokens
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.
Paramètres, retour & exemple (3)
Paramètreslimit· integer · optionnel
How many results, 1 to 10. Default 5.query· string · requis
A campground name or area, like "Upper Pines" or "Big Sur".state· string · optionnel
Optional two-letter US state code to narrow results, like CA.
Exemple d'appel{"name": "search_campgrounds", "arguments": {"query": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"query": "texte", "state": "texte", "results": []}} - search_permits≈ 626 tokens
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.
Paramètres, retour & exemple (3)
Paramètreslimit· integer · optionnel
How many results, 1 to 10. Default 5.query· string · requis
A permit, trail, park or area name, like "Mount Whitney" or "Enchantments".state· string · optionnel
Optional two-letter US state code to narrow results, like CA.
Exemple d'appel{"name": "search_permits", "arguments": {"query": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"query": "texte", "state": "texte", "results": []}}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».