← Registry

Data Collection

peakcam.io

Provides PeakCam ski resort snow reports, webcam links, and comparison/ranking tools for resort conditions.

1 endpoint14 known toolsFirst detected October 19, 2026Last detected October 19, 2026

ENDPOINT 1

https://www.peakcam.io/api/mcp

No auth detected

MCP server metadata

Name
io.peakcam/snow
Version
0.1.0
Capabilities
tools.listChangedresources.listChangedcompletions
Server instructions

PeakCam Snow is read-only snow data for about 150 ski resorts in the US, Canada, Chile and Argentina (https://www.peakcam.io). Every snow number carries a `source`: `snotel` means measured at a USDA NRCS SNOTEL station near the resort (quality-controlled, refreshed every 6 hours, valid at the station's elevation rather than the summit); `open_meteo` means a weather-model estimate for resorts with no station; `pipeline`, `manual` and `resort` are blends or hand-entered values. Webcams are returned as links only: the resort's PeakCam page, the operator's stream URL and, when one exists, a still-image URL with its capture time. Never describe a frame you have not seen. Workflow: search_resorts turns a name into a slug; get_resort_conditions, get_resort_cams, get_forecast and get_snow_history take that slug; find_powder ranks resorts by new snow (sourceOnly="snotel" for measured-only); compare_resorts sets 2–6 resorts side by side; get_opening_dates lists season dates. When you answer, label each number with its source and time (for example "6 in in 24 h, SNOTEL-measured, 2026-12-20 12:00 UTC"), call model values estimates, and link the resort's canonicalUrl. Each resort is also readable as markdown at peakcam://resorts/{slug}.

Known tools 14

search_resorts

Find PeakCam resorts by name (or part of one, or a region) and get their slugs with a one-line snow summary each.

Inferred read-only
get_resort_conditions

The latest snow report for one resort with provenance: new snow 24 h / 48 h, base depth, snow water equivalent, percent of normal, 7-day trend, rating, season status, plus a cam summary and the canonical PeakCam URL to cite.

Inferred read-only
get_resort_cams

The resort's webcams as links: PeakCam page URL, the operator's stream or page URL, a still-image URL when one exists, and health (live / down / unchecked, from PeakCam's probe, not proof of a live broadcast).

Inferred read-only
find_powder

Rank resorts by new snow in the last 24 or 48 hours, optionally within one state/province and above a minimum.

Inferred read-only
compare_resorts

Side-by-side latest snow, season status and cam counts for 2–6 resorts.

Inferred read-only
get_forecast

Five-day National Weather Service forecast for a US resort (daily high/low, text forecast, precipitation chance, wind) with a rough snow estimate derived from the forecast wording.

Inferred read-only
get_snow_history

Daily snow depth, snow water equivalent, precipitation accumulation and temperatures for the last 1–30 days at the resort's station (SNOTEL where there is one, Open-Meteo model otherwise), newest first.

Inferred read-only
get_opening_dates

Season opening and closing dates with status (open / closed / unknown) for every resort, or those in one state/province, soonest opening first.

Inferred read-only
get_resort_profile

Who and where a resort is, without the snow numbers: location and elevations, website and social links, PeakCam's cam page, the SNOTEL station its numbers come from (if any), season status, cam counts, and every URL PeakCam publishes for it (page, JSON, markdown, Atom feed, state hub).

Inferred read-only
get_percent_of_normal

SNOTEL-fed resorts ranked by snowpack relative to normal: snow water equivalent against the station's own 1991–2020 median for today's date, deepest first, optionally within one state.

Inferred read-only
list_regions

Every state, province and country PeakCam covers, with resort, reporting, measured (SNOTEL) and cam counts and the hub page URL.

Inferred read-only
get_alert_options

How to be told when it snows, without this server writing anything: the powder-alert threshold and schedule, the e-mail, webhook (Standard Webhooks, signed), Atom and iCal channels, the per-resort public Atom feed, the webhook payload contract, and the manage page where a person registers a destination.

Inferred read-only
get_cam_timeline

Archived still frames for a resort's webcams (or one cam) over the last 1–48 hours, as links with capture times, plus the newest storm frame on tape per cam.

Inferred read-only
ask

One natural-language question in, one tool result out, deterministically: the router resolves the resort by name or nickname, picks an intent from the wording (snow, open/closed, forecast, cams, history, compare, where did it snow, percent of normal, profile, regions, alerts) and calls the matching tool.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.io-peakcam-snow]
url = "https://www.peakcam.io/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "io-peakcam-snow": {
      "type": "http",
      "url": "https://www.peakcam.io/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: io-peakcam-snow
Remote MCP URL: https://www.peakcam.io/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "io-peakcam-snow": {
      "url": "https://www.peakcam.io/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "io-peakcam-snow": {
      "type": "http",
      "url": "https://www.peakcam.io/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "io-peakcam-snow",
  "transport": "streamable-http",
  "url": "https://www.peakcam.io/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.