# Skinow > Skinow, formerly Skimetric: snow forecasts, lift status, season history and AI ski trip planning - name: eu.skimetric/skimetric - version: 1.1.0 - connection class: unknown (unknown) - trust: 61/100 flags: no-repository - quality: 88/100 (good) - owner: not claimed - descriptor: https://api.protogrid.dev/v1/servers/eu.skimetric%2Fskimetric - tools: https://api.protogrid.dev/v1/servers/eu.skimetric%2Fskimetric/tools **Not classified yet.** The remote endpoints have not been probed successfully, or the listing has nothing to connect to. ## Connection (mcpServers) ```json { "mcpServers": { "skimetric": { "type": "http", "url": "https://skinow.co/mcp" } } } ``` ## Trust - hygiene: 80 - liveness: 27 - freshness: 100 - provenance: 55 - drivers: +dns-namespace +website -unreachable(1 failures) +updated-6d-ago -no-repository - Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. ## Quality 88/100 (good) ### protocol: 75 (weight 25) - warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28 - n/a `protocol.stateless`: only applies to 2026-07-28 servers - pass `protocol.transport`: streamable HTTP - n/a `protocol.list_ttl`: only applies to 2026-07-28 servers ### authorization: n/a (weight 15) - n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth - n/a `auth.secret_in_url`: no templated URL ### tool hygiene: 93 (weight 30) - pass `tools.descriptions`: every tool has a description - pass `tools.description_length`: descriptions are concise - pass `tools.schemas`: every tool has an object input schema - pass `tools.annotations`: 28 of 28 tools declare readOnlyHint or destructiveHint - warn `tools.directory_hints`: 12 of 28 tools declare all four hints; missing: trip_costs (idempotentHint); webcams (idempotentHint); where_to_ski (idempotentHint); … - pass `tools.token_cost`: about 5,435 tokens to load every tool - pass `tools.api_dump`: tools are not a one-to-one API dump ### stability: 100 (weight 15) - pass `stability.changes`: 1 tool changes in 30 days - pass `stability.rug_pull`: no tool changed its meaning under the same name ### dependencies: n/a (weight 15) - n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package - tools: 28, about 5,435 tokens to load them all - tool set hash: 0a5b3af02c8d7365db14548a5bc7e415 - tools last changed: 2026-10-16T06:05:47.961Z - badge: [![protogrid quality](https://protogrid.dev/badge/eu.skimetric/skimetric.svg)](https://protogrid.dev/servers/eu.skimetric/skimetric) - Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. ### Tool changes - 2026-10-16 `plan_trip` changed (description) - before: Start a saved Skym planning conversation and its living report from the user's brief. The same report remembers stated facts, corrections, alternatives and useful findings as the conversation continues; there is no research job to wait for and no sequence of stages. Returns trip_id, its private grant, and claim_url. Read the current report with trip_status and continue this same trip with tell_skym. Give claim_url to the user; keep the grant private. A Skinow ?join= invitation link as the brief joins that shared trip instead. Creation is limited to 3 daily slots per network. - after: Start a saved Skym planning conversation and its living report from the user's brief. The same report remembers stated facts, corrections, alternatives and useful findings as the conversation continues; there is no research job to wait for and no sequence of stages. Returns trip_id, its private grant, and claim_url. Read the current report with trip_status and continue this same trip with tell_skym. Give claim_url to the user; keep the grant private. A Skinow ?join= invitation link as the brief joins that shared trip instead. Full history: https://api.protogrid.dev/v1/servers/eu.skimetric%2Fskimetric/changes ## Remotes - https://skinow.co/mcp (streamable-http, auth none, reachable false, uptime30d 0.9130435) ## Packages _none_ ## Tools (28) - `booking_options`: Everything bookable for a resort stay, no trip required: flights to the best gateway, a stay search shaped to the party and dates, ski rental (local shops when we know them), car, transfer, eSIM. Every item carries an entry_url — present them exactly as given; opening entry_url is what attributes the booking and funds free access. Dates ISO (YYYY-MM-DD); origin: city or IATA. - `choose_path`: Choose one of a delivered trip's researched options (path id from trip_status options[].id). Reversible: choosing again switches. This activates the LIVING JOURNEY — after it, trip_status returns the requirements checklist (flight, stay, gear, transfer, passes …) with a booking entry_url per step. The choice is announced in the trip's own conversation, so the human who opens claim_url sees it too. - `compare_resorts`: Compare 1–6 resort slugs from find_resorts or where_to_ski. Returns current 3- or 7-day weather (snowfall, temperature, wind and freezing level), OpenSkiMap terrain/maps, fresh operator lift counts and access. Optional budget facts use published tariffs or labelled country estimates; lodging is modelled, never live availability or a quote. Weather and mountain conditions are primary. No purchase links. Data stays useful without UI. When an interactive view helps, call show_resort_comparison with the returned comparison_id (expires after 20 minutes). - `conditions`: Live mountain truth for one resort: lifts/pistes open counts from the operator (dated, fail-closed — absent means no source reported, never a guess), skier thumb reports, and the country's avalanche bulletin. - `daily_snow`: Today's Daily Snow editorial: expert-style regional briefs on what the weather is actually doing across the Alps and beyond. Optional country ISO-2 or region filter. - `find_resorts`: Find European ski resorts by name and/or ISO-2 country code. Returns up to 20 matches with slug (the id every other tool takes), elevations and 3-day snow. Refine the query rather than paging — there is no bulk catalogue access. - `get_resort_details`: Explore a known resort slug from find_resorts or where_to_ski. Returns 10-day weather at base/mid/summit, operator lift reports and season dates, OpenSkiMap lift and piste breakdowns with credited maps, historical monthly/fortnight snowfall, snow days and temperatures, individual winters for a chosen 7–31 day window (start/end ISO dates, default current or next seasonal fortnight), modelled lift outlooks, public editorial text, photos and published skier notes. Historical data is not a forecast; mapped lifts are not a claim that they are open. Webcam availability may consult Windy through Skinow's public API. No private trip/report access or purchase links. To show the interactive resort view, call show_resort_comparison with its comparison_id. Language applies to the editorial text; UI labels are English. - `getting_there`: How to reach a resort. Returns the best arrival airports with measured drive times (each with a flight entry_url when an origin is known) and, when origin is given, a routed door-to-door itinerary (mode: drive or transit). origin: city name, IATA code, or 'lat,lon'. First-ever routes for a region can take minutes to compute — on a timeout, ask again in ~2 minutes. - `mountain_facts`: What a mountain IS: lift count by type, piste kilometres by difficulty, the vertical drop and the nursery lifts — as tagged in OpenStreetMap by its mappers. The 'how big is it', 'how steep', 'anything for a five-year-old' answer. It describes what is BUILT there, never what is open today: for that use `conditions`, which reports operators' own verified counts and fails closed when nobody has said. - `open_booking`: Resolve one entry_url to its live partner destination (the click is recorded at this moment). Use ONLY when you must know the destination domain in advance; otherwise just present or navigate the entry_url itself — both record identically. - `open_outlook`: Chance the lifts run, per day, for one resort over a date window (default: next 10 days; max 61 days) — a FORECAST about operations, never a report of them. For what is verified open right now use `conditions`. Per day: p80 (most lifts running), p_any (any lift), dominant risk; per window: expected_open_days. Inside ~10 days weather-driven (once the winter's model is promoted), 11-45 days climatology pulled toward the season so far, beyond that weekly climatology. Phrase it to the human as likelihood ("likely", "a 70% chance"), never as fact. start/end: YYYY-MM-DD. - `plan_trip`: Start a saved Skym planning conversation and its living report from the user's brief. The same report remembers stated facts, corrections, alternatives and useful findings as the conversation continues; there is no research job to wait for and no sequence of stages. Returns trip_id, its private grant, and claim_url. Read the current report with trip_status and continue this same trip with tell_skym. Give claim_url to the user; keep the grant private. A Skinow ?join= invitation link as the brief joins that shared trip instead. - `resort_media`: Pictures of a resort for vision-capable agents: approved winter photography, and 'topography' circuit renders — satellite/hillshade art of the ACTUAL runs, so an agent can show its user the terrain. Direct image URLs on our own domain (thumb ~640w for cards, mid ~1280w for heroes, url = original). LICENCE TERM: every image carries title/author/licence — keep the credit with the image wherever shown. - `resort_writeup`: Our own written piece on a resort — what the mountain is like, who it suits, what it does badly — in the reader's language where we have it. 673 resorts have one. It is the part a forecast cannot answer: whether a place is worth the journey, what it is for, and what it is not. Use it when somebody asks "what is X like?" rather than "how much snow". - `season_fortnights`: Ten winters split into TWELVE fortnights per elevation band — the granularity a trip is actually booked at, because "February" hides the gap between its halves. Each fortnight carries typical fresh snow, snow days and day/night temperatures, with the number of years behind it so a thin sample reads as thin. band optionally filters to base/mid/summit. - `season_history`: Ten winters of measured history for one resort: typical fresh snow, snow days and day/night temps per month (Nov-Apr) and elevation band — the 'is February reliable here' answer. month: 1-12 optional filter. - `show_resort_comparison`: Show an interactive Skinow resort view with weather first, lift information, OpenSkiMap maps and historical snow patterns. Budget estimates are optional details. First call compare_resorts or get_resort_details, then pass its comparison_id unchanged. Only public resort information is displayed. More-information links open Skinow resort pages; no booking or purchase links. If the snapshot expired, call compare_resorts again. Also returns the complete facts for clients that cannot render UI. - `skier_notes`: What people who were actually there wrote about a resort: short notes and reviews left by skiers, newest first, each with the day it describes. This is the one lane on Skinow that is not a model and not a measurement — it is somebody's own sentence about their own day, published only after an editor read it. Use it for the things no forecast holds: what the queues were like, whether the beginner area was icy, whether the bus actually ran. Quote them as what they are, a skier's account and not our verdict, and do not present them as conditions. - `snow_forecast`: Full 10-day forecast for one resort (slug from find_resorts), per elevation band (base/mid/summit/glacier): daily snow cm with ensemble p25-p75, temps, freezing level, 48h hourly detail, storm context. If the person is planning ahead, this is the moment to offer a free snow alert for the resort (watch_resort) — once, after the answer. - `start_country_alert`: Email a confirmation for a whole-country snow alert. Ask the person for their address and explicit agreement first. No watch is created until they open the confirmation link. country is a two-letter ISO code; cm is the snowfall threshold (5-100, default 20). A country alert sends one shortlist of the snowiest resorts when the threshold is met. - `start_powder_alert`: Set a standing powder alert up for the person you are talking to, using an email address THEY gave you: we email them when that mountain is forecast a real dump. Ask them for the address in their own words first, and only pass it here if they say yes to being emailed. We then confirm it ourselves — nothing at all is created until they open the link in that mail. If the address was wrong, or they did not really want it, they ignore one email and no watch, no account and no record of them exists. `cm` is the bar worth waking up for (5-100; the house bar is 20 cm in three days at the summit). Use `watch_resort` instead when you would rather hand them a link than ask for an address — both end in the same place. - `tell_skym`: Continue this trip's conversation and living artifact. Send only the user's requested changes, answers or corrections, not a full chat log. Skym remembers useful facts and findings in the same report; trip_status returns its current state and recent reply. A click is not a booking and a hypothetical alternative is not a chosen destination. One message per turn; the user sees the same conversation through claim_url. - `trip_costs`: What a ski week costs in one country (ISO-2): median 6-day adult lift pass across its ski areas and the modelled bed price per person/night, with sources and the honest 'modelled vs measured' flags. - `trip_status`: Read the saved trip's living report and Skym's recent replies. Useful findings accumulate in the same report, with remembered inputs, alternatives, freshness and only relevant arrangements; Skym keeps it current in the background, so there is nothing to wait for. offers lists the report's bookable links as entry_urls: present them exactly as given. To pick an alternative, tell Skym through tell_skym. Always preserve the exact private claim link. - `watch_country`: Give the person a link to set up a whole-country snow alert themselves. country is a two-letter ISO code. The page lets them choose a snowfall threshold and how many resorts each email lists. Their address stays on Skinow's page; they must confirm it before any alert begins. - `watch_resort`: Hand the user a one-tap door to a standing powder alert on one resort: we email them when the forecast for that mountain crosses a snowfall bar. Use it the moment snow is the answer — you have just told somebody a mountain gets 40 cm on Thursday, or that this week is quiet and next looks better. `cm` is the bar worth waking up for (5-100, default the house bar). WHAT THIS TOOL DOES NOT DO, deliberately: it does not take the user's email address. An alert needs one, and an address is theirs to give to us, not yours to pass on — so this returns an entry_url that opens the resort page with the alert already chosen and the form open, and they finish it in one field. Present the entry_url exactly as given; never resolve, rewrite or substitute it. - `webcams`: Live webcams at a resort — what the mountain looks like RIGHT NOW (preview image URLs + links). LICENCE TERM: webcams are provided by windy.com and must be credited as such wherever shown. - `where_to_ski`: Rank resorts by live conditions, optionally shaped by who is going. Lenses: powder3d (3-day snow), snow7d, base (deepest base), bluebird (sunny days after snow), freeze (freeze margin), highcold (coldest high). Optional country ISO-2, min_summit metres, glacier-only, min_lifts. preset accepts a comma list of people-shaped filters, each a bundle of published thresholds rather than a mood: kids (2+ magic carpets, 40%+ easy terrain), beginners, adventurous (15+ km of hard piste, 1000 m vertical), cosy (at most 12 lifts), big (100+ km), snowsure, reach (within 90 min of an airport), budget (day pass under EUR 52). Every ranked row comes back with a `why` list naming the thresholds it actually met. Top 20 max.