Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe
Free
Tools
ask_snowdata
Text-only Q&A grounded in SnowSure data (~1s). Use for open-ended questions, terrain %, expert-run counts, advice, AND specifically: El Niño / ENSO / 2026-27 winter outlook (or call get_elnino_signal / get_elnino_rankings), head-to-head resort comparisons (annual snowfall, vertical drop, base/summit elevation, skiable area — "which has more snowfall, Niseko or Whistler"), season-opening norms ("wh
ArgumentsA call is made on an account: it counts against an allowance and the publisher sees it, which is why this one asks who you are first.
—
p95 latency
—
call success
—
uptime 90d
0
calls last 7d
What it does
Live ski snow, multi-model forecasts, powder rankings & a grounded Answer Engine for 500+ resorts.
Quickstart
# 1 — install (mcprush login holds a key from your dashboard)
npx mcprush@latest add snowsure-snow-ski-mcp
# 2 — ask your agent something
> Live ski snow, multi-model forecasts, powder rankings & a grounded Answer Engine for 500+ resorts.
SnowSure — Snow & Ski is free: there is no plan to choose, no cap to set and nothing that can bill you.
Publishernot claimed
SNAll 1 server
snowsure.ai1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine — this server runs on the publisher’s own infrastructure behind our gateway, and what you install is the connection to it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add --transport http snowsure-snow-ski-mcp https://www.snowsure.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free to install, and it runs from its publisher’s own package: no account, no key, no card.
What it writes
One config entry pointing at the gateway. The server itself runs on the publisher’s own infrastructure, so nothing from this listing executes on your machine.
What you approve
45 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Text-only Q&A grounded in SnowSure data (~1s). Use for open-ended questions, terrain %, expert-run counts, advice, AND specifically: El Niño / ENSO / 2026-27 winter outlook (or call get_elnino_signal / get_elnino_rankings), head-to-head resort comparisons (annual snowfall, vertical drop, base/summit elevation, skiable area — "which has more snowfall, Niseko or Whistler"), season-opening norms ("wh
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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). Answers single-reso
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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,
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
Get detailed day-by-day weather forecast for a resort including temperature, snowfall, wind, and conditions for each of the next 14 days.
Takes no parameters.
Example callreturns →
Find resorts matching specific criteria like minimum snow depth, elevation range, number of runs, or SnowSure rating. Advanced filtering for trip planning.
Takes no parameters.
Example callreturns →
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. Pr
Takes no parameters.
Example callreturns →
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. This tool is date-scoped, so it is the wrong shape for two neighbouring quest
Takes no parameters.
Example callreturns →
Rank resorts by how a season actually went, scoped to a place. This is the tool for "which <place> resort had the most <metric> last season" — the single most common retrospective question agents ask. Scope by state or province (Maine, Montana, Wyoming, British Columbia, Hokkaido, Nagano, Valais, Tyrol), by country (Switzerland, Japan, Canada), or by region (north-america, europe, asia, oceania, s
Takes no parameters.
Example callreturns →
One resort's own snowfall history: season totals, comparison to its 5-year and 30-year averages, and best months to visit. Scoped to a SINGLE resort — for "which resort in <state/country/region> led <metric> last season", use get_season_leaderboard instead.
Takes no parameters.
Example callreturns →
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
Takes no parameters.
Example callreturns →
Resort-level El Niño / ENSO outlook from SnowSure's 30-year fleet dataset (152 ranked resorts). Returns rank, tier, strong/all-event signal, analog winters ('97-98, '15-16, '23-24), forecast paragraph, methodology note, and in-season scorecard when live. Use for ANY El Niño, ENSO, or 2026-27 winter-outlook question about a named resort. Tilt, not fate — n=3 disclosed; D/E tiers are timing plays.
Takes no parameters.
Example callreturns →
Ranked El Niño ski resorts from SnowSure's 30-year fleet table. Filter by region (south-america, north-america, europe, asia, oceania) or tier (A prime / B favored / C ENSO-proof / D late bloomer / E timing play). Use for 'best El Niño resorts in Europe', 'where will it snow most in 2026-27', 'is El Niño good for the Alps'.
Takes no parameters.
Example callreturns →
Get ski trip recommendations based on dates, preferences, and conditions. Suggests best resorts for a given time period.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
Get a summary of snow conditions across an entire region or country with statistics and top resorts.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
Get categorized SnowSure intelligence insights (not just snow totals). The last_season category is the one to reach for on retrospective questions — how a finished season compared to its 5yr norm, who led it, where the models were trustworthy. Also covers model accuracy by region, longest dry spell, and trend pulse. Insights are hemisphere-scoped narrative cards; when the question names a specific
Takes no parameters.
Example callreturns →
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. Its leaderboards read CURRENT-seaso
Takes no parameters.
Example callreturns →
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).
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
Remove a resort from the signed-in user's saved list. Requires a SnowSure user access token (OAuth).
Takes no parameters.
Example callreturns →
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).
Takes no parameters.
Example callreturns →
List the signed-in user's alert subscriptions. Requires a SnowSure user access token (OAuth).
Takes no parameters.
Example callreturns →
Remove one of the signed-in user's alert subscriptions by id (from list_alerts). Requires a SnowSure user access token (OAuth).
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
Details for a multi-resort ski pass (Epic, Ikon, Mountain Collective, …): operator, season pricing tiers, destination count, regions, and the buy link.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
Compare 2–4 resorts side by side across snow, terrain, and live conditions — every value comes from the SnowSure conditions resolver/contract. Use for head-to-head stat questions phrased as either/or: "which gets more average annual snowfall, X or Y", "which has the greater vertical drop / higher base or summit elevation / bigger skiable area, X or Y", "which typically opens earlier, X or Y". Opti
Takes no parameters.
Example callreturns →
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).
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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).
Takes no parameters.
Example callreturns →
Freeyour plan
$0 forever
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. SnowSure — Snow & Ski costs nothing to install and nothing to call, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is a hosted endpoint: the publisher runs it and we connect to it. The scanner reads packages and source, and neither exists to read here, so there is no grade — not a withheld one, an unmeasured one. What can be checked instead is on Installation: what it asks to reach and what it writes.
Release history
Pinned to 3.12.7 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
3.12.7
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against SnowSure — Snow & Ski in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.