Remote MCP · Endpoint

status.live MCP server

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

UpLast checked 1 hour ago

Server URL

https://status.live/mcp

The last check completed an MCP handshake.

Registry name
live.status/status-live
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
114 ms
Tools exposed
17 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Live status of the physical world: ski lifts, theme park rides, national parks, campgrounds, surf.
Website
https://status.live/
Listing
From the official MCP registry (active).
Recent checks of status.live
CheckedResultHandshake
1 hour agoHandshake completed114 ms
2 days agoHandshake completed659 ms
5 days agoHandshake completed91 ms
7 days agoHandshake completed425 ms
9 days agoHandshake completed322 ms
11 days agoHandshake completed519 ms
13 days agoHandshake completed507 ms
16 days agoHandshake completed350 ms
18 days agoHandshake completed295 ms
19 days agoHandshake completed543 ms
21 days agoHandshake completed443 ms
22 days agoHandshake completed106 ms
23 days agoHandshake completed25 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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