# Snow Depth and Snowpack (SNOTEL) MCP (remote · snow-depth-snowpack-snotel-mcp.lipmichal.workers.dev)

SNOTEL snow depth, snowpack and percent of median for western US mountain sites, from USDA NRCS.

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `snow-depth-snowpack-snotel-mcp.lipmichal.workers.dev`: 67/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-snow-depth-snowpack-snotel-mcp/snow-depth-snowpack-snotel-mcp.md), [page](https://verifymcp.io/servers/theluckystrike-snow-depth-snowpack-snotel-mcp/snow-depth-snowpack-snotel-mcp)

## Channel facts

- Endpoint: `https://snow-depth-snowpack-snotel-mcp.lipmichal.workers.dev/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-11-21.

- **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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 971 tokens (~242/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 Snow Depth and Snowpack (SNOTEL) MCP server?

Snow Depth and Snowpack (SNOTEL) MCP is a hosted endpoint at https://snow-depth-snowpack-snotel-mcp.lipmichal.workers.dev/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 theluckystrike-snow-depth-snowpack-snotel-mcp 'https://snow-depth-snowpack-snotel-mcp.lipmichal.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-snow-depth-snowpack-snotel-mcp": {
      "url": "https://snow-depth-snowpack-snotel-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-snow-depth-snowpack-snotel-mcp": {
      "type": "http",
      "url": "https://snow-depth-snowpack-snotel-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-snow-depth-snowpack-snotel-mcp]
url = "https://snow-depth-snowpack-snotel-mcp.lipmichal.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-snow-depth-snowpack-snotel-mcp": {
      "type": "remote",
      "url": "https://snow-depth-snowpack-snotel-mcp.lipmichal.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-snow-depth-snowpack-snotel-mcp --url 'https://snow-depth-snowpack-snotel-mcp.lipmichal.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-snow-depth-snowpack-snotel-mcp:
    url: "https://snow-depth-snowpack-snotel-mcp.lipmichal.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-snow-depth-snowpack-snotel-mcp": {
      "Transport": "http",
      "Url": "https://snow-depth-snowpack-snotel-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-snow-depth-snowpack-snotel-mcp -t streamable-http -u 'https://snow-depth-snowpack-snotel-mcp.lipmichal.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-snow-depth-snowpack-snotel-mcp": {
      "type": "http",
      "url": "https://snow-depth-snowpack-snotel-mcp.lipmichal.workers.dev/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-11-21 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-17 (score 65)

First indexed and scored.

## MCP tools (4)

### `snow_depth` (~246 tokens)

Snow depth near a place

Current snow depth (inches and cm), snow water equivalent, SWE as a percent of the 30-year median for the date, and the 24-hour and 7-day change in depth at the SNOTEL stations nearest a place, ZIP code or coordinates, or at a named station. Each station has its elevation and distance. SNOTEL covers the mountains of AK, AZ, CA, CO, ID, MT, NV, NM, OR, SD, UT, WA and WY.

Input parameters:

- `count` (integer): How many nearest stations. Default 3.
- `latitude` (number): Latitude, with longitude, instead of location.
- `location` (string): A place ("Breckenridge, CO", "Mount Hood", "Alta, UT"), a US ZIP code, or "lat, lon".
- `longitude` (number): Longitude, with latitude.
- `max_miles` (number): Search radius in miles. Default 60.
- `station` (string): A SNOTEL station name ("Berthoud Summit", "Berthoud Summit, CO"), id ("335") or triplet ("335:CO:SNTL"). Overrides location.

### `snowpack_by_state` (~167 tokens)

Snowpack by state

Statewide snowpack from every active SNOTEL station in one state: snow water equivalent as a percent of the 30-year median (summed over stations), the median station percent, how many stations report and have snow, the deepest site, and every station with its snow depth, SWE and percent of median, sorted by depth, SWE, percent of median, elevation or name.

Input parameters:

- `sort` (string): Station order. Default depth (deepest first).
- `state` (string, required): State code or name: AK, AZ, CA, CO, ID, MT, NV, NM, OR, SD, UT, WA or WY.
- `top` (integer): How many stations to name in the summary. Default 10; the structured list has every station.

### `snow_depth_history` (~225 tokens)

Snow depth season history

One SNOTEL station's snow season (Oct 1 to Sep 30): daily snow depth, snow water equivalent and the 30-year median SWE, weekly samples, the deepest day and peak SWE so far, first snow, melt-out, the same day last year, last season's peak, and the median onset, peak and melt-out dates. Give a station, or a place to use its nearest station.

Input parameters:

- `latitude` (number): Latitude, with longitude, instead of location.
- `location` (string): A place ("Breckenridge, CO", "Mount Hood", "Alta, UT"), a US ZIP code, or "lat, lon".
- `longitude` (number): Longitude, with latitude.
- `season` (string): Season such as "2025-26", or "current" (default) or "last".
- `station` (string): A SNOTEL station name ("Berthoud Summit", "Berthoud Summit, CO"), id ("335") or triplet ("335:CO:SNTL"). Overrides location.

### `snotel_stations` (~219 tokens)

Find SNOTEL stations

Search the active USDA NRCS SNOTEL stations by state, name, county, minimum elevation or distance from a place (nearest first). Returns name, triplet (for the other tools), state, county, elevation, coordinates and the NRCS station page.

Input parameters:

- `county` (string): County name.
- `latitude` (number): Latitude, with longitude, instead of location.
- `limit` (integer): Maximum stations returned. Default 20.
- `location` (string): A place ("Breckenridge, CO", "Mount Hood", "Alta, UT"), a US ZIP code, or "lat, lon".
- `longitude` (number): Longitude, with latitude.
- `max_miles` (number): Radius around the place in miles. Default 50.
- `min_elevation_ft` (number): Only stations at or above this elevation in feet.
- `name` (string): Part of a station name, such as "Pass" or "Summit".
- `state` (string): State code or name.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-snow-depth-snowpack-snotel-mcp/snow-depth-snowpack-snotel-mcp#diagnostics

## Score history

- 2026-11-21: 67
- 2026-11-20: 66
- 2026-11-19: 66
- 2026-11-18: 65
- 2026-11-17: 65

## Common questions

### What is the Snow Depth and Snowpack (SNOTEL) MCP server?

Snow Depth and Snowpack (SNOTEL) MCP is listed in the public MCP registry as io.github.theluckystrike/snow-depth-snowpack-snotel-mcp. SNOTEL snow depth, snowpack and percent of median for western US mountain sites, from USDA NRCS. This page covers its hosted endpoint (https://snow-depth-snowpack-snotel-mcp.lipmichal.workers.dev/mcp).

### Is the Snow Depth and Snowpack (SNOTEL) MCP server safe to use?

Snow Depth and Snowpack (SNOTEL) MCP scores 67 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 Snow Depth and Snowpack (SNOTEL) MCP server expose?

Snow Depth and Snowpack (SNOTEL) MCP exposes 4 tools: snow_depth, snowpack_by_state, snow_depth_history, snotel_stations. Their descriptions and schemas cost roughly 857 tokens of context every time the server is loaded.

### Does the Snow Depth and Snowpack (SNOTEL) MCP server require authentication?

No. We connected to Snow Depth and Snowpack (SNOTEL) MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Snow Depth and Snowpack (SNOTEL) MCP server still maintained?

Snow Depth and Snowpack (SNOTEL) MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Snow Depth and Snowpack (SNOTEL) MCP server?

VerifyMCP ran 12 checks on Snow Depth and Snowpack (SNOTEL) MCP, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Snow Depth and Snowpack (SNOTEL) MCP: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://snow-depth-snowpack-snotel-mcp.lipmichal.workers.dev/mcp
- Repository: https://github.com/theluckystrike/snow-depth-snowpack-snotel-mcp
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-snow-depth-snowpack-snotel-mcp/snow-depth-snowpack-snotel-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-snow-depth-snowpack-snotel-mcp/snow-depth-snowpack-snotel-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theluckystrike-snow-depth-snowpack-snotel-mcp/snow-depth-snowpack-snotel-mcp.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-snow-depth-snowpack-snotel-mcp/snow-depth-snowpack-snotel-mcp
