Remote MCP · Endpoint

status.live campgrounds MCP server

No. status.live campgrounds answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://status.live/campgrounds/mcp

The last check completed an MCP handshake.

Registry name
live.status/campgrounds
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
935 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Which of 4,200 national park and national forest campgrounds are open today, with booking links.
Listing
From the official MCP registry (active).
Recent checks of status.live campgrounds
CheckedResultHandshake
1 hour agoHandshake completed935 ms
2 days agoHandshake completed89 ms
5 days agoHandshake completed442 ms
7 days agoHandshake completed916 ms
9 days agoHandshake completed482 ms
11 days agoHandshake completed688 ms
14 days agoHandshake completed532 ms
16 days agoHandshake completed29 ms
18 days agoHandshake completed29 ms
19 days agoHandshake completed621 ms
21 days agoHandshake completed582 ms
22 days agoHandshake completed547 ms
23 days agoHandshake completed262 ms

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

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 campgrounds and makes no claim about it beyond what these checks measured.