Remote MCP · Endpoint

io.github.cyanheads/national-parks-mcp-server MCP server

No. io.github.cyanheads/national-parks-mcp-server answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://national-parks.caseyjhand.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.cyanheads/national-parks-mcp-server
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
286 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Plan US National Park Service trips — parks, alerts, campgrounds, things to do, events.
Listing
From the official MCP registry (active).
Recent checks of io.github.cyanheads/national-parks-mcp-server
CheckedResultHandshake
1 hour agoHandshake completed286 ms
1 day agoHandshake completed267 ms
3 days agoHandshake completed251 ms
3 days agoHandshake completed298 ms
4 days agoHandshake completed423 ms
5 days agoHandshake completed282 ms
7 days agoHandshake completed278 ms
10 days agoHandshake completed248 ms
12 days agoHandshake completed278 ms
15 days agoHandshake completed257 ms
17 days agoHandshake completed293 ms
19 days agoHandshake completed166 ms
21 days agoHandshake completed142 ms
23 days agoHandshake completed159 ms
25 days agoHandshake completed116 ms
26 days agoHandshake completed60 ms
28 days agoHandshake completed127 ms
29 days agoHandshake completed115 ms

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

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 io.github.cyanheads/national-parks-mcp-server and makes no claim about it beyond what these checks measured.