status.live ski
REMOTE · STATUS.LIVE
Live ski lift status for 260+ resorts from their own lift boards, with snow, weather and webcams.
Available components
Last scanned (9 hours ago)
Scores higher than 63% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 717 tokens (~102/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 62% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 20. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 10. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 67
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Probed https://status.live/ski/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=status.live | CN=WE1,O=Google Trust Services,C=US | 8 Oct 2026 | 6 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 92ea705d3a84484a13943f2e810d4260 |
| SANs: status.live, api.status.live, *.api.status.live | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of status.live. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| live. | present | 36322 | 8 | Verified |
| status.live. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://status.live/ski/mcp | Verified | 200 | |
| http (plaintext) | http://status.live/ski/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ski_compare_resorts Compare resorts ~63
Side-by-side open-lift counts for up to 10 resorts, sorted by share of lifts open. Operator-reported; a resort without a count says whether it listed no lifts or could not be read.
| Name | Type | Req | Description |
|---|---|---|---|
| resorts | array | yes | Resort ids or names |
No output schema declared.
No examples provided.
ski_find_nearby_resorts Find nearby resorts ~89
Resorts closest to a point, by straight-line distance. Optionally fetches live open-lift counts for each.
| Name | Type | Req | Description |
|---|---|---|---|
| include_status | boolean | – | Also fetch live lift counts (one request per resort) |
| latitude | number | yes | – |
| limit | integer | – | – |
| longitude | number | yes | – |
| max_km | number | – | Ignore resorts farther than this |
No output schema declared.
No examples provided.
ski_get_region_summary Region summary ~74
Open-lift totals for a whole region (a tag from ski_list_regions, e.g. "Utah", "Dolomiti"), with each resort's count. Fetches every resort in the region, so it is limited to 40 resorts.
| Name | Type | Req | Description |
|---|---|---|---|
| region | string | yes | Region tag, case-insensitive |
No output schema declared.
No examples provided.
ski_get_resort_status Get resort status ~221
Everything known about one resort: live lift status (each lift open, on hold, scheduled, or closed, read from the resort's own site), opening date if the season has not started, a model weather forecast, model snow estimates (depth and snowfall over the last 7/30 and next 7 days at the lower and upper lift elevations), official road conditions on the access routes where a source exists (California chain controls, the road to Farellones), and webcams. Lift data is operator-reported and comes with an as-of time and a state: reported (the board listed lifts), none_listed (it listed none, usually off-season; not the same as closed) or source_error (it could not be read; unknown). Accepts an id or a resort name.
| Name | Type | Req | Description |
|---|---|---|---|
| include_lifts | boolean | – | List every lift by name; set false for just the counts |
| resort | string | yes | Resort id (e.g. "palisades") or name (e.g. "Palisades Tahoe") |
No output schema declared.
No examples provided.
ski_list_regions List regions ~28
List the region tags resorts are grouped by (states, countries, ranges), with resort counts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ski_open_now Resorts open right now ~149
Ski resorts whose own lift board lists running lifts right now, most open lifts first, optionally within a region (a country such as "Chile", a state such as "Colorado", a season pass such as "Ikon Pass" or "Epic Pass", or any tag from ski_list_regions). Uses the latest check of every resort, made about every 90 minutes, so it answers "where can I ski today?" across all resorts at once; each line gives its as-of time. Use ski_get_resort_status for a live, per-lift answer about one resort.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| region | string | – | Country, state or region tag, case-insensitive |
No output schema declared.
No examples provided.
ski_search_resorts Search ski resorts ~93
Find the ski resorts this server covers, by name, id, region tag (e.g. "Colorado", "Alps", "Lake Tahoe") or season pass ("Ikon Pass", "Epic Pass"). Returns resort ids to pass to the other tools. Leave query empty to list everything.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | – | Name, id, or region, case-insensitive |
No output schema declared.
No examples provided.
How do I install the status.live ski MCP server?
status.live ski is a hosted endpoint at https://status.live/ski/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · status.live
claude mcp add --transport http live-status-ski 'https://status.live/ski/mcp'
What is the status.live ski MCP server?
status.live ski is an MCP server listed in the public MCP registry as live.status/ski. Live ski lift status for 260+ resorts from their own lift boards, with snow, weather and webcams. This page covers its hosted endpoint (https://status.live/ski/mcp).
Is the status.live ski MCP server safe to use?
status.live ski scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the status.live ski MCP server expose?
status.live ski exposes 7 tools: ski_search_resorts, ski_list_regions, ski_get_resort_status, ski_compare_resorts, ski_find_nearby_resorts, and 2 more. Their descriptions and schemas cost roughly 717 tokens of context every time the server is loaded.
Does the status.live ski MCP server require authentication?
No. We connected to status.live ski without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the status.live ski MCP server still maintained?
status.live ski is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.