Remote MCP · Endpoint

ClimbCast MCP server

No. ClimbCast answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://climbcast.io/mcp

The last check completed an MCP handshake.

Registry name
io.climbcast/climbcast
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
321 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Conditions, trip briefs, alerts, permits, roads, hourly, areas, accuracy for WA, OR, BC. No account.
Listing
From the official MCP registry (active).
Recent checks of ClimbCast
CheckedResultHandshake
1 day agoHandshake completed321 ms
2 days agoHandshake completed265 ms
5 days agoHandshake completed251 ms
7 days agoHandshake completed253 ms
8 days agoHandshake completed1.23 s
10 days agoHandshake completed259 ms
12 days agoHandshake completed246 ms
13 days agoHandshake completed386 ms
14 days agoHandshake completed233 ms
17 days agoHandshake completed388 ms
18 days agoHandshake completed206 ms
20 days agoHandshake completed233 ms
21 days agoHandshake completed217 ms
22 days agoHandshake completed205 ms

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

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