Remote MCP · Endpoint

status.live ski MCP server

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

UpLast checked 1 hour ago

Server URL

https://status.live/ski/mcp

The last check completed an MCP handshake.

Registry name
live.status/ski
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
553 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Live ski lift status for 260+ resorts from their own lift boards, with snow, weather and webcams.
Website
https://status.live/ski
Listing
From the official MCP registry (active).
Recent checks of status.live ski
CheckedResultHandshake
1 hour agoHandshake completed553 ms
2 days agoHandshake completed638 ms
5 days agoHandshake completed998 ms
7 days agoHandshake completed692 ms
9 days agoHandshake completed642 ms
11 days agoHandshake completed532 ms
13 days agoHandshake completed674 ms
15 days agoHandshake completed292 ms
18 days agoHandshake completed323 ms
19 days agoHandshake completed369 ms
20 days agoHandshake completed93 ms
22 days agoHandshake completed638 ms
23 days agoHandshake completed243 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 ski and makes no claim about it beyond what these checks measured.