status.live national parks
REMOTE · STATUS.LIVE
US and Canadian national park alerts, closures, road events, campgrounds open today and conditions.
Available components
Last scanned (3 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Maps and Location
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability73
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 416 tokens (~138/item across 3 items; 3 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 Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage78
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 33% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 20. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 13. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 65
First indexed and scored.
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 18 Oct 2026 · Probed https://status.live/nationalparks/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=status.live | CN=WE1,O=Google Trust Services,C=US | 8 Oct 2026 | 6 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 92ea705d3a84484a13943f2e810d4260 |
| SANs: status.live, api.status.live, *.api.status.live | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of status.live. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| live. | present | 36322 | 8 | Verified |
| status.live. | absent | 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://status.live/nationalparks/mcp | Verified | 200 | |
| http (plaintext) | http://status.live/nationalparks/mcp | Inconclusive | 405 |
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 →
nationalparks_find_campgrounds Find national park campgrounds ~92
National Park Service campgrounds nearest a point, with whether each is open today by its published schedule, site counts and reservation links. Schedules only: check nationalparks_get_park_status for current alerts.
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | yes | – |
| limit | integer | – | – |
| longitude | number | yes | – |
| max_km | number | – | – |
| open_today_only | boolean | – | – |
No output schema declared.
No examples provided.
nationalparks_get_park_status Get national park status ~207
Right now at one park. For US parks: the National Park Service's current alerts (closures, dangers, fire bans, water outages), National Weather Service warnings, air quality (US AQI), active wildfires within 50 km, road events inside the park and access-road conditions where available, which campgrounds and visitor centers are open today by their published schedules, webcams, sunrise/sunset and moon phase, and a model weather forecast. For Canadian parks: Parks Canada bulletins, Environment Canada weather alerts, satellite fire hotspots, air quality, road conditions where available, and the forecast. Live parts come with an as-of time. Accepts a park id (e.g. "yose", "banff") or name.
| Name | Type | Req | Description |
|---|---|---|---|
| include_campgrounds | boolean | – | List each campground; set false for just the count |
| park | string | yes | Park code (e.g. "yose") or name (e.g. "Yosemite") |
No output schema declared.
No examples provided.
nationalparks_search_parks Search national parks ~117
Find the national parks this server covers: US National Park Service units (national parks, plus monuments, seashores and recreation areas with campgrounds) and Canada's national parks (Parks Canada). Search by name, park id (e.g. "yose", "banff"), US state, Canadian province, or "canada". Returns ids for nationalparks_get_park_status.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | – | Name, park code, state code or state name, case-insensitive |
No output schema declared.
No examples provided.
How do I install the status.live national parks MCP server?
status.live national parks is a hosted endpoint at https://status.live/nationalparks/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 · status.live
claude mcp add --transport http live-status-nationalparks 'https://status.live/nationalparks/mcp'
What is the status.live national parks MCP server?
status.live national parks is an MCP server listed in the public MCP registry as live.status/nationalparks. US and Canadian national park alerts, closures, road events, campgrounds open today and conditions. This page covers its hosted endpoint (https://status.live/nationalparks/mcp).
Is the status.live national parks MCP server safe to use?
status.live national parks scores 70 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 status.live national parks MCP server expose?
status.live national parks exposes 3 tools: nationalparks_search_parks, nationalparks_get_park_status, nationalparks_find_campgrounds. Their descriptions and schemas cost roughly 416 tokens of context every time the server is loaded.
Does the status.live national parks MCP server require authentication?
No. We connected to status.live national parks without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the status.live national parks MCP server still maintained?
status.live national parks is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.