# status.live ski (remote · status.live)

Live ski lift status for 260+ resorts from their own lift boards, with snow, weather and webcams.

- Trust score: 72/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `status.live`: 72/100 (this document), [markdown](https://verifymcp.io/servers/live-status-ski/ski-mcp.md), [page](https://verifymcp.io/servers/live-status-ski/ski-mcp)

## Channel facts

- Endpoint: `https://status.live/ski/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 717 tokens (~102/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 62% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http live-status-ski 'https://status.live/ski/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "live-status-ski": {
      "url": "https://status.live/ski/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "live-status-ski": {
      "type": "http",
      "url": "https://status.live/ski/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.live-status-ski]
url = "https://status.live/ski/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "live-status-ski": {
      "type": "remote",
      "url": "https://status.live/ski/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add live-status-ski --url 'https://status.live/ski/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  live-status-ski:
    url: "https://status.live/ski/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "live-status-ski": {
      "Transport": "http",
      "Url": "https://status.live/ski/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add live-status-ski -t streamable-http -u 'https://status.live/ski/mcp'
```

### Other

```json
{
  "mcpServers": {
    "live-status-ski": {
      "type": "http",
      "url": "https://status.live/ski/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 72, +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.

### 2026-10-15 (score 71, +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.

### 2026-10-13 (score 70, +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.

### 2026-10-12 (score 69, +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.

### 2026-10-09 (score 68, +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.

### 2026-10-07 (score 67)

First indexed and scored.

## MCP tools (7)

### `ski_search_resorts` (~93 tokens)

Search ski resorts

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.

Input parameters:

- `limit` (integer)
- `query` (string): Name, id, or region, case-insensitive

### `ski_list_regions` (~28 tokens)

List regions

List the region tags resorts are grouped by (states, countries, ranges), with resort counts.

### `ski_get_resort_status` (~221 tokens)

Get resort status

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.

Input parameters:

- `include_lifts` (boolean): List every lift by name; set false for just the counts
- `resort` (string, required): Resort id (e.g. "palisades") or name (e.g. "Palisades Tahoe")

### `ski_compare_resorts` (~63 tokens)

Compare resorts

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.

Input parameters:

- `resorts` (array, required): Resort ids or names

### `ski_find_nearby_resorts` (~89 tokens)

Find nearby resorts

Resorts closest to a point, by straight-line distance. Optionally fetches live open-lift counts for each.

Input parameters:

- `include_status` (boolean): Also fetch live lift counts (one request per resort)
- `latitude` (number, required)
- `limit` (integer)
- `longitude` (number, required)
- `max_km` (number): Ignore resorts farther than this

### `ski_get_region_summary` (~74 tokens)

Region summary

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.

Input parameters:

- `region` (string, required): Region tag, case-insensitive

### `ski_open_now` (~149 tokens)

Resorts open right now

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.

Input parameters:

- `limit` (integer)
- `region` (string): Country, state or region tag, case-insensitive

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/live-status-ski/ski-mcp#diagnostics

## Score history

- 2026-10-18: 72
- 2026-10-17: 72
- 2026-10-16: 71
- 2026-10-15: 71
- 2026-10-14: 70
- 2026-10-13: 70
- 2026-10-12: 69
- 2026-10-10: 68
- 2026-10-09: 68
- 2026-10-07: 67

## Common questions

### 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.

## Links

- Remote endpoint: https://status.live/ski/mcp
- Website: https://status.live/ski
- Changelog RSS feed: https://verifymcp.io/servers/live-status-ski/ski-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/live-status-ski/ski-mcp.json
- HTML version of this page: https://verifymcp.io/servers/live-status-ski/ski-mcp