# SnowSure — Snow & Ski (remote · www.snowsure.ai)

Live ski snow, multi-model forecasts, powder rankings & a grounded Answer Engine for 500+ resorts.

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

## Components

- remote · `www.snowsure.ai`: 72/100 (this document), [markdown](https://verifymcp.io/servers/ai-snowsure-snow/www.md), [page](https://verifymcp.io/servers/ai-snowsure-snow/www)
- npm · `snowsure-mcp-server`: 35/100, [markdown](https://verifymcp.io/servers/ai-snowsure-snow/snowsure-mcp-server.md), [page](https://verifymcp.io/servers/ai-snowsure-snow/snowsure-mcp-server)

## Channel facts

- Endpoint: `https://www.snowsure.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.4`

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

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (remove_saved_resort).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 88/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 5538 tokens (~102/item across 54 items; 42 tools + 12 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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).
  - 99% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### Claude

```bash
claude mcp add --transport http ai-snowsure-snow https://www.snowsure.ai/mcp
```

### Codex

```toml
[mcp_servers.ai-snowsure-snow]
url = "https://www.snowsure.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-snowsure-snow": {
      "type": "remote",
      "url": "https://www.snowsure.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-snowsure-snow --url https://www.snowsure.ai/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-snowsure-snow:
    url: "https://www.snowsure.ai/mcp"
```

### Other

```json
{
  "mcpServers": {
    "ai-snowsure-snow": {
      "type": "http",
      "url": "https://www.snowsure.ai/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-08-03 (score 72, +1)

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

### 2026-08-01 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 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-07-31 (score 70, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 70, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 70, +2)

- [functional regression] Schema quality: pass → fail
- [functional] New tool “get_monthly_snow”

### 2026-07-27 (score 68, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

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

First indexed and scored.

## MCP tools (42)

### `ask_snowdata` (~267 tokens)

Ask SnowSure

Text-only Q&A grounded in SnowSure data (~1s). Use for open-ended questions, terrain %, expert-run counts, advice, AND specifically: head-to-head resort comparisons (annual snowfall, vertical drop, base/summit elevation, skiable area — "which has more snowfall, Niseko or Whistler"), season-opening norms ("which resort typically opens earliest", "usually open by Thanksgiving"), glacier / year-round skiing, and factual resort & geography trivia (what country/state/island a resort is in, named runs like Corbet's Couloir, records like the highest chairlift). NEVER use for photo/gallery/picture requests (→ get_resort_photos) or resort guide cards (→ get_resort_info). Does NOT render UI cards.

Input parameters:

- `format` (string): Response shape: markdown (default) or json
- `hemisphere` (string): Optional hemisphere hint when not resort-scoped
- `locale` (string): Response language (default: en)
- `partnerId` (string): Client hint for tailored guidance: claude, chatgpt, cursor, perplexity
- `question` (string, required): Natural-language question about snow or a resort
- `resortSlug` (string): Optional resort slug to scope the answer (e.g. jackson-hole)

Output parameters:

- `answer` (string)
- `answerSource` (string)
- `confidence` (string)
- `evidence` (array)
- `generatedAt` (string)
- `intent` (string)
- `markdown` (string): Human-readable markdown summary (required for ChatGPT Instant mode).
- `queryId` (string)
- `sourceLabel` (string)

### `get_snow_report` (~122 tokens)

Global snow report

Get the global snow report with top-ranked resorts by snow conditions. Returns resorts sorted by SnowSure score, forecast, or recent snowfall. Use this for "where has the best snow?" or "top ski resorts right now" queries.

Input parameters:

- `limit` (number): Number of resorts to return (default: 10, max: 50)
- `region` (string): Filter by region
- `sort` (string): Sort order: snowsure (AI rating), forecast (14-day snow), recent (24h snowfall), depth (current base)

Output parameters:

- `markdown` (string): Human-readable markdown summary (required for ChatGPT Instant mode).
- `resorts` (array)
- `subtitle` (string)
- `title` (string)
- `updatedAt` (string)

### `get_powder_reels` (~147 tokens)

Powder Reels storm timelapses

Powder Reels — SnowSure archived storm timelapses with verified accumulation data burned into the frames ("Proof of Powder"). Use for "how much did it snow at X last night", "show me the storm at Alta", "biggest powder days this season", or any request for storm footage / timelapse / receipts. Returns reels newest-first with watch links.

Input parameters:

- `date` (string): Optional storm date (YYYY-MM-DD) — requires resort
- `limit` (number): Number of reels to return (default: 5, max: 20)
- `resort` (string): Optional resort slug to filter (e.g. "alta", "portillo")

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `get_resort_info` (~161 tokens)

Resort guide card

INTERACTIVE RESORT GUIDE CARD (Resort Info sidebar UI) — elevation, vertical, lifts, runs, skiable acres, average snowfall, season dates, ski passes, editorial description, hero/gallery carousel. REQUIRED when the user asks for: resort guide, mountain profile, resort info, lifts/runs/vertical/skiable area, season dates, ski passes, or "tell me about the mountain" (non-weather). Examples: "Aspen Mountain resort guide", "how many lifts at Jackson Hole". Do NOT use get_resort (that shows the snow conditions card).

Input parameters:

- `slug` (string, required): Resort slug identifier (e.g., "aspen-mountain", "niseko-hanazono-resort", "jackson-hole")

Output parameters:

- `markdown` (string): Human-readable markdown summary (required for ChatGPT Instant mode).
- `resort` (object): Structured resort payload for inline widget rendering.

### `get_resort_photos` (~120 tokens)

Resort photo gallery

INTERACTIVE PHOTO GALLERY CAROUSEL — official SnowSure resort photos (hero + Sanity gallery). REQUIRED for: photos, pictures, images, gallery, "show me photos of Vail/Aspen". Never use web search or inline images — call this tool. Do NOT use get_destination, get_resort_info, or ask_snowdata for photo requests.

Input parameters:

- `slug` (string, required): Resort slug identifier (e.g., "aspen-mountain", "jackson-hole", "niseko-hanazono-resort")

Output parameters:

- `markdown` (string): Human-readable markdown summary (required for ChatGPT Instant mode).
- `resort` (object): Structured resort payload for inline widget rendering.

### `get_resort` (~212 tokens)

Live snow & forecast

Single-resort data with a REQUIRED card parameter that picks the interactive UI. card=guide → resort info card (elevation, lifts, season dates). card=photos → photo gallery carousel. card=snow → snow conditions card (score, base depth, forecast). card=full → detailed markdown only, no card. "Resort guide" → card=guide. "Photos/gallery" → card=photos. "Conditions/forecast" / "is it open right now, base depth, lifts open of total" → card=snow (open status, base depth, and lifts open of total). Prefer get_resort_info / get_resort_photos when available (same cards).

Input parameters:

- `card` (string, required): UI card type: guide (resort info), photos (gallery carousel), snow (conditions), full (text only)
- `slug` (string, required): Resort slug identifier (e.g., "aspen-mountain", "niseko-hanazono-resort", "jackson-hole")

Output parameters:

- `markdown` (string): Human-readable markdown summary (required for ChatGPT Instant mode).
- `resort` (object): Structured resort payload for inline widget rendering.

### `search_resorts` (~107 tokens)

Search resorts

Search for ski resorts by name, country, or region. Returns matching resorts with basic conditions. Use for "find resorts in [location]" or "search [name]" queries.

Input parameters:

- `country` (string): Filter by exact country name (e.g., "Japan", "Switzerland", "United States")
- `limit` (number): Maximum results to return (default: 20)
- `query` (string): Search query - can be resort name, country, or partial match

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `find_best_powder` (~93 tokens)

Find fresh powder

Find resorts with the freshest powder snow right now. Returns resorts sorted by 24-hour snowfall. Use for "where is it snowing?" or "fresh powder" queries.

Input parameters:

- `limit` (number): Number of results (default: 10)
- `minSnowfall` (number): Minimum 24h snowfall in cm to include (default: 5)
- `region` (string): Filter by region

Output parameters:

- `markdown` (string): Human-readable markdown summary (required for ChatGPT Instant mode).
- `resorts` (array)
- `subtitle` (string)
- `title` (string)
- `updatedAt` (string)

### `find_powder_trips` (~172 tokens)

Find bookable powder trips

Powder trips you can BOOK: ranks resorts by their 14-day forecast (best chance of fresh snow in the bookable window) and returns handpicked luxury ski hotels at each — "where to go AND where to stay". Use for "where should I book for powder", "best powder trip this month", "book a ski trip with good snow coming". Optional vibe filter (lux | hip | family | budget) shows only hotels handpicked into that tier. Each hotel carries an attribution-tagged booking link; booking completes on LUXSKI.

Input parameters:

- `limit` (number): Number of destinations (default: 5)
- `region` (string): Filter destinations by region
- `vibe` (string): Only show handpicked hotels in this tier: lux, hip, family, or budget

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `compare_forecasts` (~72 tokens)

Compare forecast models

Compare 14-day snow forecasts across 7 weather models (ECMWF, GFS, GEM, JMA, ICON, Météo-France, Met Norway) for a resort. Shows model agreement and uncertainty. Use for forecast reliability queries.

Input parameters:

- `slug` (string, required): Resort slug to compare forecasts for

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `get_weather_forecast` (~69 tokens)

Resort weather forecast

Get detailed day-by-day weather forecast for a resort including temperature, snowfall, wind, and conditions for each of the next 14 days.

Input parameters:

- `days` (number): Number of days to forecast (default: 7, max: 14)
- `slug` (string, required): Resort slug

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `find_resorts_by_criteria` (~129 tokens)

Filter resorts by criteria

Find resorts matching specific criteria like minimum snow depth, elevation range, number of runs, or SnowSure rating. Advanced filtering for trip planning.

Input parameters:

- `country` (string): Filter by country
- `limit` (number): Max results (default: 20)
- `minDepth` (number): Minimum snow depth in cm
- `minElevation` (number): Minimum summit elevation in meters
- `minRuns` (number): Minimum number of ski runs
- `minScore` (number): Minimum SnowSure score (0-100)
- `region` (string): Filter by region

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `get_southern_hemisphere_report` (~173 tokens)

Southern Hemisphere report

Get snow conditions for Southern Hemisphere ski resorts (Australia, New Zealand, Argentina, Chile) currently in season. Answers "is Perisher / Portillo / Valle Nevado open right now and what are the current conditions", "is the Australian ski season underway", and "which Southern Hemisphere region — the Andes, Australia, or NZ — has the best snow right now". Use for June–October SH ski queries. Prefers operator-verified data when available. Do NOT use for a specific opening DATE — use get_season_openings instead.

Input parameters:

- `country` (string): Optional country filter
- `limit` (number): Max resorts (default: 10)
- `sort` (string): Sort: snowsure (AI score), recent (24h snow), depth (base depth)

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `get_season_openings` (~181 tokens)

Season opening calendar

Resorts whose season OPENING DATE is a specific day — answers "what opens today?", "opening this week", or "which resorts start their season on June 27?". Returns only resorts scheduled or confirmed to open on that date, NOT all currently-open resorts. Prefer over get_southern_hemisphere_report for opening-day questions. For historical-norm questions ("which resort typically opens earliest each season", "is X usually open by Thanksgiving / mid-December"), use ask_snowdata instead — those are about typical timing, not a specific calendar date.

Input parameters:

- `country` (string): Filter by country, e.g. Chile or New Zealand
- `date` (string): Opening date YYYY-MM-DD. Defaults to today (UTC).
- `hemisphere` (string): Northern or Southern Hemisphere filter
- `region` (string): Filter by region

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `get_snow_history` (~47 tokens)

Resort snow history

Get historical snowfall data for a resort including season totals, comparison to 5-year and 30-year averages, and best months to visit.

Input parameters:

- `slug` (string, required): Resort slug

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `get_monthly_snow` (~148 tokens)

Typical snow by month

Typical snow for a resort MONTH BY MONTH, from ~30 years of ERA5 reanalysis — average snowfall, snow days, base and peak depth, and biggest storm, plus per-season totals. Use for date-choosing questions: 'what is February usually like at Vail', 'when should I go', 'is January or March better'. This is HISTORY, not a forecast and not a prediction — for the next 14 days use get_weather_forecast, and for right now use get_resort. Months with too little history are withheld rather than shown thin; every month returned carries yearsTracked so you can cite the evidence.

Input parameters:

- `slug` (string, required): Resort slug

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `plan_ski_trip` (~119 tokens)

Plan a ski trip

Get ski trip recommendations based on dates, preferences, and conditions. Suggests best resorts for a given time period.

Input parameters:

- `dates` (string): When you plan to travel — month name or date range, e.g. "February" or "Jan 15-22".
- `level` (string): Skier or snowboarder ability level.
- `priority` (string): Optional main trip priority (single value). Omit for best overall SnowSure score ranking.
- `region` (string): Preferred ski region. Defaults to worldwide (any).

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `get_webcam_status` (~64 tokens)

Resort webcams

Get live webcam links and status for a resort to see current on-mountain conditions visually — answers "show me the webcam / live cam at <resort>", "current conditions on camera", and named-cam lookups.

Input parameters:

- `slug` (string, required): Resort slug

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `get_regional_summary` (~73 tokens)

Regional snow summary

Get a summary of snow conditions across an entire region or country with statistics and top resorts.

Input parameters:

- `country` (string): Exact country name when region is too broad, e.g. "Switzerland" or "Japan".
- `region` (string): Geographic region to summarize, e.g. alps or japan.

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `list_insight_categories` (~61 tokens)

List insight categories

List SnowSure insight categories (live conditions, current season, last season, forecast trust, patterns, SnowSure index, ground truth). Use before get_insights to choose a category filter. Lighter than raw leaderboards — retrospective and verification-backed cards.

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `get_insights` (~143 tokens)

SnowSure insights

Get categorized SnowSure intelligence insights (not just snow totals). Answers questions like season vs 5yr norm, last season powder leaders, model accuracy by region, longest dry spell, trend pulse. Filter by category or insightType=intelligence to skip simple leaderboards.

Input parameters:

- `category` (string): Single insight category id from list_insight_categories. Omit to return all categories.
- `hemisphere` (string): Northern (nh) or southern (sh) hemisphere. Defaults to nh.
- `insightType` (string): data = leaderboards only; intelligence = analysis cards (recommended).
- `scope` (string): snapshot = one hemisphere; global = both hemispheres.

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `get_ml_trends` (~344 tokens)

ML/AI trends

Fetch SnowSure-unique ML/AI trend datasets from the public REST API. Use for powder-day leaders, bluebird-day leaders, bluebird predictions, improving/stable/declining score pulse, per-model accuracy weights, daily SnowSure score component history, ML extended outlook (days 8–14), global forecast trust, and powder/bluebird event logs. Start with dataset=catalog. Prefer get_insights for narrative intelligence cards; use this for raw rankings and time series.

Input parameters:

- `dataset` (string, required): Trend dataset to fetch. catalog lists all endpoints; powder_days / bluebird_days = season leaderboards; score_components needs slug.
- `days` (number): Lookback days for score_components (default 30, max 365).
- `eventType` (string): Filter snow_events by event type.
- `limit` (number): Max rows for leaderboards or snow_events (default 25, max 100).
- `minCm` (number): Minimum ML days 8–14 snow (cm) when dataset=extended_outlook leaderboard (default 0).
- `minSpread` (number): Minimum 14d model spread (cm) when dataset=forecast_disagreement (default 5).
- `openOnly` (boolean): When dataset=extended_outlook, filter to open resorts only (default true).
- `resort` (string): Resort slug filter when dataset=snow_events.
- `slug` (string): Resort slug — required for score_components, vs_last_year, and season_stats; optional for extended_outlook (per-resort).
- `stats` (boolean): When dataset=snow_events, return season aggregates instead of events.

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `get_destination` (~127 tokens)

Destination hub

Multi-mountain destination hub (Niseko, Chamonix, Aspen Snowmass umbrella) with a table of member ski areas. Use ONLY when the user names the hub itself — NOT for photo gallery (→ get_resort_photos on a specific mountain slug) and NOT for resort guide cards (→ get_resort_info).

Input parameters:

- `limit` (number): Max member resorts to return (default 12)
- `slug` (string, required): Destination slug (e.g. niseko, chamonix, hakuba, aspen-snowmass) or alias like "hakuba valley"

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `list_saved_resorts` (~43 tokens)

List saved resorts

List the signed-in user's saved resorts. Requires a SnowSure user access token (OAuth); without one it returns an authorization-required error telling the agent how to connect.

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `save_resort` (~56 tokens)

Save a resort

Save a resort to the signed-in user's favorites. Requires a SnowSure user access token (OAuth). The slug must be a real SnowSure resort.

Input parameters:

- `slug` (string, required): Resort slug to save, e.g. jackson-hole

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `remove_saved_resort` (~42 tokens)

Remove a saved resort

Remove a resort from the signed-in user's saved list. Requires a SnowSure user access token (OAuth).

Input parameters:

- `slug` (string, required): Resort slug to remove

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `subscribe_alerts` (~205 tokens)

Subscribe to snow alerts

Subscribe the signed-in user to snow alerts. Requires a SnowSure user access token (OAuth). type: 'powder' (OBSERVED fresh snow >= thresholdCm in 24h), 'forecast' (the 14-day FORECAST clears thresholdCm within windowDays — the proactive 'tell me when a powder trip is forming' watcher), 'opening' (resort opens for the season), or 'bluebird' (powder day then clear skies).

Input parameters:

- `channel` (string): Delivery channel (default email)
- `scope` (string): Resort slug, or 'any' for all resorts (default 'any')
- `thresholdCm` (number): Snow threshold in cm — fresh-snow for powder (default 15), 14-day forecast total for forecast (default 30)
- `type` (string, required): Alert type
- `windowDays` (number): forecast alerts only: scan the next N days of forecast (1–14, default 14)

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `list_alerts` (~27 tokens)

List alert subscriptions

List the signed-in user's alert subscriptions. Requires a SnowSure user access token (OAuth).

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `unsubscribe_alerts` (~47 tokens)

Unsubscribe from alerts

Remove one of the signed-in user's alert subscriptions by id (from list_alerts). Requires a SnowSure user access token (OAuth).

Input parameters:

- `id` (string, required): Subscription id to remove

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `book_lodging` (~210 tokens)

Find lodging & booking link

Lodging near a resort via LUXSKI for the signed-in user. With a specific `hotelName` + checkIn + checkOut it PREBOOKS a live rate and returns a LUXSKI checkout URL to complete payment (we hold the rate + attribute the booking; we never charge). Without those it returns availability + a booking link. Requires a SnowSure user access token (OAuth). Payment always completes on LUXSKI.

Input parameters:

- `checkIn` (string): Check-in date (YYYY-MM-DD)
- `checkOut` (string): Check-out date (YYYY-MM-DD)
- `guests` (number): Number of adults, optional
- `hotelName` (string): Specific hotel to prebook (from find_powder_trips / search). With dates → returns a checkout URL.
- `powderEventId` (string): Optional powder-event id to attribute the booking to
- `slug` (string, required): Resort slug to find lodging near, e.g. verbier

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `get_pass` (~67 tokens)

Ski pass details

Details for a multi-resort ski pass (Epic, Ikon, Mountain Collective, …): operator, season pricing tiers, destination count, regions, and the buy link.

Input parameters:

- `passId` (string, required): Pass id, e.g. epic-pass, ikon-pass, mountain-collective

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `find_pass_resorts` (~95 tokens)

Resorts on a ski pass

List the resorts on a ski pass, optionally filtered to a region — answers "is <resort> on the Ikon Pass" and "what resorts does the Epic Pass include". Returns names + SnowSure slugs you can pass to get_resort.

Input parameters:

- `passId` (string, required): Pass id, e.g. ikon-pass
- `region` (string): Optional region filter (matches the pass’s region labels)

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `compare_passes` (~162 tokens)

Compare ski passes

Compare ski passes on price, resort coverage, and value — the tool for "which season pass includes <resort> — Epic or Ikon?" (pass resortSlugs=[<resort>]). Optionally pass resortSlugs you plan to ski and tripDays to see which pass covers them and whether it beats buying window lift tickets.

Input parameters:

- `dailyTicketUsd` (number): Override the assumed window ticket rate (default $185)
- `passIds` (array): Passes to compare (default: all). e.g. ["epic-pass","ikon-pass"]
- `resortSlugs` (array): Resorts you plan to ski — used for coverage scoring
- `tripDays` (number): Total days you plan to ski (for the value calc)

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `compare_resorts` (~112 tokens)

Compare resorts

Compare 2–4 resorts side by side across snow, terrain, and live conditions — every value comes from the SnowSure conditions resolver/contract. Optionally restrict to specific dimensions.

Input parameters:

- `dimensions` (array): Optional subset of: score, status, depth, snowfall24h, forecast14d, lifts, runs, snowQuality, summit, vertical, longestRun
- `slugs` (array, required): 2–4 resort slugs to compare, e.g. ["verbier","val-disere"]

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `get_my_snow_report` (~50 tokens)

My personalized snow report

Personalized snow report for the signed-in user's saved resorts — live conditions for each, ranked best-first (open resorts with the freshest snow on top). Requires a SnowSure user access token (OAuth).

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `get_avalanche` (~87 tokens)

Avalanche bulletin

Current avalanche danger bulletin for a resort's forecast zone (US, Canada, Switzerland in v1), relayed from the official warning service with the issuer + link. Returns 'no bulletin' when there's no forecast service for the area or it's off-season. NOT a substitute for the official bulletin or avalanche training.

Input parameters:

- `slug` (string, required): Resort slug, e.g. jackson-hole

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `get_operating_risk` (~80 tokens)

Lift-operation risk

Will the lifts run? A 48-hour operating-risk estimate from the Open-Meteo forecast — wind-hold (gusts), visibility, cold (wind-chill), and heavy-snow control delays. Modeled guidance, NOT the resort's own operating decision — always check live lift status.

Input parameters:

- `slug` (string, required): Resort slug

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `get_road_access` (~111 tokens)

Road & chain control

Driving access for a resort — answers "do I need chains to get to <resort>" and "is the road to <resort> open": chain-control / mountain-pass / road-surface conditions on nearby highways (California via Caltrans, Washington via WSDOT, Colorado via CDOT, Utah via UDOT). Returns 'no road data' outside the covered area. Links to the official DOT map; the resort's road status is authoritative.

Input parameters:

- `slug` (string, required): Resort slug

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `get_road_cameras` (~86 tokens)

Road cameras

Live roadside DOT/CCTV camera stills on the highways near a resort — shows what the drive actually looks like right now (California via Caltrans, Washington via WSDOT, Utah via UDOT). Distinct from resort webcams. Returns 'no road cameras' outside the covered area; each camera includes a live image URL.

Input parameters:

- `slug` (string, required): Resort slug

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `get_road_weather` (~89 tokens)

Roadside weather

Measured roadside weather (RWIS) on the highways near a resort — surface + air temperature, visibility, wind, precipitation (Colorado via CDOT, Washington via WSDOT, Utah via UDOT). Sensor data on the actual road, distinct from the modeled get_operating_risk. Returns 'no road weather' outside the covered area.

Input parameters:

- `slug` (string, required): Resort slug

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `plan_ski_road_trip` (~138 tokens)

Plan a ski road trip

Plan a multi-stop ski road trip: picks the top-scoring resorts in a region, orders them into a drivable route (nearest-neighbour, minimal backtracking), allocates your days across stops, estimates each driving leg, and folds in live conditions plus chain-control where covered. Args: region (required), days, optional pass.

Input parameters:

- `days` (integer)
- `pass` (string): Optional ski pass to limit stops (e.g. epic, ikon)
- `region` (string, required): europe | north-america | asia | oceania | south-america | alps | rockies | japan | any

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

### `find_flights_to_powder` (~164 tokens)

Flights to the powder

Complete the trip: from a resort, find the nearest gateway airport(s) and get flight-search links from your home airport. The "get there" leg of the funnel — pair with find_best_powder / find_powder_trips (find fresh snow) → this → book_lodging (stay). Args: resort (slug, required — use search_resorts to resolve a name), optional origin (your home-airport IATA like DEN, or a city name).

Input parameters:

- `origin` (string): Your departure airport IATA (e.g. DEN, LHR) or a city name. Optional — omit for an origin-less flight search.
- `resort` (string, required): Resort slug (use search_resorts first if you only have a name).

Output parameters:

- `markdown` (string): Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-snowsure-snow/www#diagnostics

## Score history

- 2026-08-03: 72
- 2026-08-02: 71
- 2026-08-01: 71
- 2026-07-31: 70
- 2026-07-30: 70
- 2026-07-29: 70
- 2026-07-28: 68
- 2026-07-27: 68
- 2026-07-26: 67

## Links

- Remote endpoint: https://www.snowsure.ai/mcp
- Website: https://www.snowsure.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-snowsure-snow/www/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-snowsure-snow/www/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ai-snowsure-snow/www