Remote MCP · Endpoint
SnowData — Live Snow MCP server
Yes, as of 32 days ago: the check failed for an unclassified reason.
DownLast checked 32 days ago
Server URL
https://mcp.snowdata.ai/
The last check failed: the check failed for an unclassified reason.
- Registry name
- ai.snowdata/live-snow
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- Not measured yet
- Uptime, last 30 days
- —
- Described by its publisher as
- Live verified resort snow, forecasts, powder search, trip planning & grounded Q&A for 430+ resorts.
- Website
- https://www.snowdata.ai/
- Listing
- From the official MCP registry (active).
No checks recorded yet. This endpoint was discovered in the registry and is queued for its first probe.
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 SnowData — Live Snow and makes no claim about it beyond what these checks measured.