Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

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.

67 Trust /100

Last scanned (13 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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. 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. 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
Schema Quality & AI Usability64
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 18 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 17 Nov 26 65

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://snow-depth-snowpack-snotel-mcp.lipmichal.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=lipmichal.workers.dev CN=WE1,O=Google Trust Services,C=US 2 Oct 2026 31 Dec 2026 ECDSA 256 ECDSA-SHA256 ebf145553d5751d20e0d3cd51e3d7a94
SANs: lipmichal.workers.dev, *.lipmichal.workers.dev
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 snow-depth-snowpack-snotel-mcp.lipmichal.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. No DS 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://snow-depth-snowpack-snotel-mcp.lipmichal.workers.dev/mcp Verified 200
http (plaintext) http://snow-depth-snowpack-snotel-mcp.lipmichal.workers.dev/mcp Inconclusive 405
MCP tools · 4 exposed · ~857 tokens

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 →

Tool Tokens
snotel_stations ~219

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.

NameTypeReqDescription
countystring–County name.
latitudenumber–Latitude, with longitude, instead of location.
limitinteger–Maximum stations returned. Default 20.
locationstring–A place ("Breckenridge, CO", "Mount Hood", "Alta, UT"), a US ZIP code, or "lat, lon".
longitudenumber–Longitude, with latitude.
max_milesnumber–Radius around the place in miles. Default 50.
min_elevation_ftnumber–Only stations at or above this elevation in feet.
namestring–Part of a station name, such as "Pass" or "Summit".
statestring–State code or name.

No output schema declared.

No examples provided.

snow_depth ~246

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.

NameTypeReqDescription
countinteger–How many nearest stations. Default 3.
latitudenumber–Latitude, with longitude, instead of location.
locationstring–A place ("Breckenridge, CO", "Mount Hood", "Alta, UT"), a US ZIP code, or "lat, lon".
longitudenumber–Longitude, with latitude.
max_milesnumber–Search radius in miles. Default 60.
stationstring–A SNOTEL station name ("Berthoud Summit", "Berthoud Summit, CO"), id ("335") or triplet ("335:CO:SNTL"). Overrides location.

No output schema declared.

No examples provided.

snow_depth_history ~225

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.

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

No output schema declared.

No examples provided.

snowpack_by_state ~167

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.

NameTypeReqDescription
sortstring–Station order. Default depth (deepest first).
statestringyesState code or name: AK, AZ, CA, CO, ID, MT, NV, NM, OR, SD, UT, WA or WY.
topinteger–How many stations to name in the summary. Default 10; the structured list has every station.

No output schema declared.

No examples provided.

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.

remote · snow-depth-snowpack-snotel-mcp.lipmichal.workers.dev

# add to Claude Code
claude mcp add --transport http theluckystrike-snow-depth-snowpack-snotel-mcp 'https://snow-depth-snowpack-snotel-mcp.lipmichal.workers.dev/mcp'
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.