_ registry / mcp http-sse · checked 2h ago

io.peakcam/snow

https://www.peakcam.io

Registry code: d4d0d47667dbf217

api record

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.

endpoint
https://www.peakcam.io/api/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is io.peakcam/snow live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is io.peakcam/snow free to use?
Yes — the hub reached it with no key and no payment.
What tools does io.peakcam/snow have?
8 tools: get_forecast, search_resorts, get_resort_conditions, get_resort_cams, get_snow_history, compare_resorts, find_powder, get_opening_dates.
Is io.peakcam/snow safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
285ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
2 open 6 never probed 2 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • find_powder open 2h ago

    Rank resorts by new snow in the last 24 or 48 hours, optionally within one state/province and above a minimum. Pass sourceOnly="snotel" to answer "where did it snow most, measured only" with station data alone. Resorts with no report are left out; zero inches is a measurement. Sources: `snotel` = measured at a USDA NRCS SNOTEL station near the resort (station elevation, not the summit), `open_meteo` = weather-model estimate for resorts without a station.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 25,
      "minimum": 1,
      "description": "Rows to return, 1–25."
    },
    "state": {
      "type": "string",
      "maxLength": 40,
      "minLength": 2,
      "description": "US state or Canadian province code (`CO`, `UT`, `BC`), or for the Andes the country name PeakCam lists (`Chile`, `Argentina`). Case-insensitive."
    },
    "window": {
      "enum": [
        "24h",
        "48h"
      ],
      "type": "string",
      "default": "24h",
      "description": "Which window ranks first; the other breaks ties."
    },
    "minInches": {
      "type": "number",
      "maximum": 500,
      "minimum": 0,
      "description": "Keep only resorts with at least this many inches in the window."
    },
    "sourceOnly": {
      "enum": [
        "snotel"
      ],
      "type": "string",
      "description": "`snotel` keeps only station-measured reports and drops model estimates."
    }
  }
}
    arguments 41 lines
  • get_opening_dates open 2h ago

    Season opening and closing dates with status (open / closed / unknown) for every resort, or those in one state/province, soonest opening first. Confirmed dates come from the resort; projected ones are third-party estimates.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 50,
      "maximum": 150,
      "minimum": 1,
      "description": "Rows to return, 1–150."
    },
    "state": {
      "type": "string",
      "maxLength": 40,
      "minLength": 2,
      "description": "US state or Canadian province code (`CO`, `UT`, `BC`), or for the Andes the country name PeakCam lists (`Chile`, `Argentina`). Case-insensitive."
    }
  }
}
    arguments 19 lines
  • get_forecast unknown never probed

    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. NWS covers US resorts only; Canadian and Andes resorts return available=false.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "PeakCam resort slug, lowercase kebab-case, e.g. `breckenridge` or `ski-portillo`. Get it from search_resorts."
    }
  }
}
    arguments 15 lines
  • search_resorts unknown never probed

    Find PeakCam resorts by name (or part of one, or a region) and get their slugs with a one-line snow summary each. Call this first when the user names a resort; then use the slug with the other tools. Covers about 150 resorts in the US, Canada, Chile and Argentina.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 20,
      "minimum": 1,
      "description": "Rows to return, 1–20."
    },
    "query": {
      "type": "string",
      "maxLength": 80,
      "minLength": 1,
      "description": "Resort name or fragment, e.g. `vail`, `big sky`, `portillo`, `tahoe`. Also matches region names."
    },
    "state": {
      "type": "string",
      "maxLength": 40,
      "minLength": 2,
      "description": "US state or Canadian province code (`CO`, `UT`, `BC`), or for the Andes the country name PeakCam lists (`Chile`, `Argentina`). Case-insensitive."
    },
    "country": {
      "type": "string",
      "maxLength": 2,
      "minLength": 2,
      "description": "ISO 3166-1 alpha-2 country code: `US`, `CA`, `CL` or `AR`."
    }
  }
}
    arguments 34 lines
  • get_resort_conditions unknown never probed

    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. Sources: `snotel` = measured at a USDA NRCS SNOTEL station near the resort (station elevation, not the summit), `open_meteo` = weather-model estimate for resorts without a station.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "PeakCam resort slug, lowercase kebab-case, e.g. `breckenridge` or `ski-portillo`. Get it from search_resorts."
    }
  }
}
    arguments 15 lines
  • get_resort_cams unknown never probed

    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). Frames are never returned inline.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "PeakCam resort slug, lowercase kebab-case, e.g. `breckenridge` or `ski-portillo`. Get it from search_resorts."
    }
  }
}
    arguments 15 lines
  • get_snow_history unknown never probed

    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. Use it for "how has the base changed this week" questions.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "slug"
  ],
  "properties": {
    "days": {
      "type": "integer",
      "default": 14,
      "maximum": 30,
      "minimum": 1,
      "description": "Days back, 1–30."
    },
    "slug": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "PeakCam resort slug, lowercase kebab-case, e.g. `breckenridge` or `ski-portillo`. Get it from search_resorts."
    }
  }
}
    arguments 22 lines
  • compare_resorts unknown 2h ago

    Side-by-side latest snow, season status and cam counts for 2–6 resorts. Every slug must resolve; an unknown one returns suggestions.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "slugs"
  ],
  "properties": {
    "slugs": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 100,
        "minLength": 1,
        "description": "PeakCam resort slug, lowercase kebab-case, e.g. `breckenridge` or `ski-portillo`. Get it from search_resorts."
      },
      "maxItems": 6,
      "minItems": 2,
      "description": "2–6 resort slugs."
    }
  }
}
    arguments 21 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id d4d0d47667dbf217.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d4d0d47667dbf217/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/d4d0d47667dbf217/badge.svg)](https://brick.blue/agent/d4d0d47667dbf217?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.