Remote MCP · Endpoint

status.live national parks MCP server

No. status.live national parks answered an MCP handshake 10 hours ago.

UpLast checked 10 hours ago

Server URL

https://status.live/nationalparks/mcp

The last check completed an MCP handshake.

Registry name
live.status/nationalparks
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
721 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
US and Canadian national park alerts, closures, road events, campgrounds open today and conditions.
Listing
From the official MCP registry (active).
Recent checks of status.live national parks
CheckedResultHandshake
10 hours agoHandshake completed721 ms
3 days agoHandshake completed1.46 s
12 days agoHandshake completed95 ms
13 days agoHandshake completed79 ms
14 days agoHandshake completed61 ms
15 days agoHandshake completed134 ms
16 days agoHandshake completed606 ms
17 days agoHandshake completed269 ms
18 days agoHandshake completed791 ms
20 days agoHandshake completed91 ms
22 days agoHandshake completed714 ms
25 days agoHandshake completed665 ms
27 days agoHandshake completed1.21 s
30 days agoHandshake completed355 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 22 responding of 22.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with status.live national parks and makes no claim about it beyond what these checks measured.