Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.

Is skinow free to use?

Yes — the hub reached it with no key and no payment.

What tools does skinow have?

27 tools: resort_writeup, getting_there, booking_options, plan_trip, tell_skym, trip_status, open_outlook, season_history, ….

Is skinow 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.

_ registry / mcp streamable-http · checked 3h ago

skinow

https://skimetric.eu

Registry code: cb6ba56bf8eaad38

api record

Snow forecasts, resort conditions, season history, costs, travel routing and full AI trip planning for ski resorts across Europe and the Americas. Free to use at https://skinow.co. Resolve resort names with find_resorts and shortlist with where_to_ski. RESORT VIEW: compare_resorts (up to six resorts) and get_resort_details (one resort: weather, lifts, maps, history, notes) return a comparison_id; show_resort_comparison displays it as an interactive view where the client renders MCP Apps, and returns the same facts as data everywhere else. TRIPS: plan_trip creates one saved Skym conversation…

endpoint: https://skinow.co/mcp
protocol: streamable-http ·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 skinow live?: Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is skinow free to use?: Yes — the hub reached it with no key and no payment.
What tools does skinow have?: 27 tools: resort_writeup, getting_there, booking_options, plan_trip, tell_skym, trip_status, open_outlook, season_history, ….
Is skinow 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

99.6%

90 days 99.5%· all time 99.5%

latency

117ms

last good check

priced tools

of 27 tools

_ answered our checks, 90 days 397 checks · signed record

2026-10-21 00:02 degraded → live
2026-10-20 22:52 live → degraded· timeout after 20000ms
2026-10-12 10:40 degraded → live
2026-09-28 19:06 degraded → live
2026-09-28 16:57 live → degraded· timeout after 20000ms

_ what it is for

topic: maps travel & places travel & transport
used for: get ski resort snow forecast
check live resort conditions
plan a ski trip
find booking options for a resort
set a powder alert
takes → gives: text → data, images
tools: 19 reads3 changes data2 sends messages

_ 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

through this hub

calls served

successful

paid through this hub

0 USDC

what callers paid

_ what it can do 27 tools

3 open 24 never probed 3 of 27 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.

daily_snow reads open 15h ago

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.

mcp-tool

{
  "type": "object",
  "title": "daily_snowArguments",
  "properties": {
    "lang": {
      "type": "string",
      "title": "Lang",
      "default": "en"
    },
    "region": {
      "type": "string",
      "title": "Region",
      "default": ""
    },
    "country": {
      "type": "string",
      "title": "Country",
      "default": ""
    }
  }
}

arguments 21 lines

find_resorts reads open 15h ago

Find ski resorts in Europe and the Americas 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.

mcp-tool

{
  "type": "object",
  "title": "find_resortsArguments",
  "properties": {
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 10
    },
    "query": {
      "type": "string",
      "title": "Query",
      "default": ""
    },
    "country": {
      "type": "string",
      "title": "Country",
      "default": ""
    }
  }
}

arguments 21 lines

where_to_ski reads open 15h ago
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.

mcp-tool
{ "type": "object", "title": "where_to_skiArguments", "properties": { "lens": { "type": "string", "title": "Lens", "default": "powder3d" }, "limit": { "type": "integer", "title": "Limit", "default": 10 }, "preset": { "type": "string", "title": "Preset", "default": "" }, "country": { "type": "string", "title": "Country", "default": "" }, "glacier": { "type": "boolean", "title": "Glacier", "default": false }, "min_lifts": { "type": "integer", "title": "Min Lifts", "default": 0 }, "min_summit": { "type": "integer", "title": "Min Summit", "default": 0 } } }
arguments 41 lines
resort_writeup reads unknown never probed
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".

mcp-tool
{ "type": "object", "title": "resort_writeupArguments", "required": [ "resort" ], "properties": { "lang": { "type": "string", "title": "Lang", "default": "en" }, "resort": { "type": "string", "title": "Resort" } } }
arguments 18 lines
getting_there reads unknown never probed
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.

mcp-tool
{ "type": "object", "title": "getting_thereArguments", "required": [ "resort" ], "properties": { "mode": { "type": "string", "title": "Mode", "default": "drive" }, "origin": { "type": "string", "title": "Origin", "default": "" }, "resort": { "type": "string", "title": "Resort" } } }
arguments 23 lines

booking_options reads unknown never probed

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.

mcp-tool

{
  "type": "object",
  "title": "booking_optionsArguments",
  "required": [
    "resort"
  ],
  "properties": {
    "end": {
      "type": "string",
      "title": "End",
      "default": ""
    },
    "start": {
      "type": "string",
      "title": "Start",
      "default": ""
    },
    "adults": {
      "type": "integer",
      "title": "Adults",
      "default": 2
    },
    "origin": {
      "type": "string",
      "title": "Origin",
      "default": ""
    },
    "resort": {
      "type": "string",
      "title": "Resort"
    },
    "children": {
      "type": "integer",
      "title": "Children",
      "default": 0
    }
  }
}

arguments 38 lines

plan_trip changes data unknown never probed
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.

mcp-tool
{ "type": "object", "title": "plan_tripArguments", "required": [ "brief" ], "properties": { "lang": { "type": "string", "title": "Lang", "default": "en" }, "brief": { "type": "string", "title": "Brief" }, "origin": { "type": "string", "title": "Origin", "default": "" } } }
arguments 23 lines
tell_skym changes data unknown never probed
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.

mcp-tool
{ "type": "object", "title": "tell_skymArguments", "required": [ "trip_id", "grant", "message" ], "properties": { "lang": { "type": "string", "title": "Lang", "default": "en" }, "grant": { "type": "string", "title": "Grant" }, "message": { "type": "string", "title": "Message" }, "trip_id": { "type": "integer", "title": "Trip Id" } } }
arguments 28 lines
trip_status reads unknown never probed
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.

mcp-tool
{ "type": "object", "title": "trip_statusArguments", "required": [ "trip_id", "grant" ], "properties": { "grant": { "type": "string", "title": "Grant" }, "trip_id": { "type": "integer", "title": "Trip Id" } } }
arguments 18 lines
open_outlook reads unknown 11h ago
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.

mcp-tool
{ "type": "object", "title": "open_outlookArguments", "required": [ "resort" ], "properties": { "end": { "type": "string", "title": "End", "default": "" }, "start": { "type": "string", "title": "Start", "default": "" }, "resort": { "type": "string", "title": "Resort" } } }
arguments 23 lines
season_history reads unknown 3h ago
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.

mcp-tool
{ "type": "object", "title": "season_historyArguments", "required": [ "resort" ], "properties": { "month": { "type": "integer", "title": "Month", "default": 0 }, "resort": { "type": "string", "title": "Resort" } } }
arguments 18 lines
show_resort_comparison unknown 30h ago
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. If the snapshot expired, call compare_resorts again. Also returns the complete facts for clients that cannot render UI.

mcp-tool
{ "type": "object", "title": "show_resort_comparisonArguments", "required": [ "comparison_id" ], "properties": { "comparison_id": { "type": "string", "title": "Comparison Id" } } }
arguments 13 lines
watch_resort reads unknown never probed
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.

mcp-tool
{ "type": "object", "title": "watch_resortArguments", "required": [ "resort" ], "properties": { "cm": { "type": "integer", "title": "Cm", "default": 0 }, "lang": { "type": "string", "title": "Lang", "default": "en" }, "resort": { "type": "string", "title": "Resort" } } }
arguments 23 lines
open_booking changes data unknown never probed
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.

mcp-tool
{ "type": "object", "title": "open_bookingArguments", "required": [ "entry_url" ], "properties": { "entry_url": { "type": "string", "title": "Entry Url" } } }
arguments 13 lines
start_powder_alert sends messages unknown never probed
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.

mcp-tool
{ "type": "object", "title": "start_powder_alertArguments", "required": [ "resort", "email" ], "properties": { "cm": { "type": "integer", "title": "Cm", "default": 0 }, "lang": { "type": "string", "title": "Lang", "default": "en" }, "email": { "type": "string", "title": "Email" }, "resort": { "type": "string", "title": "Resort" } } }
arguments 28 lines
watch_country reads unknown never probed
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.

mcp-tool
{ "type": "object", "title": "watch_countryArguments", "required": [ "country" ], "properties": { "lang": { "type": "string", "title": "Lang", "default": "en" }, "country": { "type": "string", "title": "Country" } } }
arguments 18 lines
season_fortnights reads unknown 3h ago
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.

mcp-tool
{ "type": "object", "title": "season_fortnightsArguments", "required": [ "resort" ], "properties": { "band": { "type": "string", "title": "Band", "default": "" }, "resort": { "type": "string", "title": "Resort" } } }
arguments 18 lines
resort_media reads unknown 11h ago
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.

mcp-tool
{ "type": "object", "title": "resort_mediaArguments", "required": [ "resort" ], "properties": { "resort": { "type": "string", "title": "Resort" } } }
arguments 13 lines
get_resort_details unknown 8h ago
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. Uses public resort data. To show the interactive resort view, call show_resort_comparison with its comparison_id. Language applies to the editorial text; UI labels are English.

mcp-tool
{ "type": "object", "title": "get_resort_detailsArguments", "required": [ "resort" ], "properties": { "end": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "title": "End", "default": null }, "lang": { "type": "string", "title": "Lang", "default": "en" }, "start": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "title": "Start", "default": null }, "resort": { "type": "string", "title": "Resort" } } }
arguments 42 lines
start_country_alert sends messages unknown never probed
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.

mcp-tool
{ "type": "object", "title": "start_country_alertArguments", "required": [ "country", "email" ], "properties": { "cm": { "type": "integer", "title": "Cm", "default": 0 }, "lang": { "type": "string", "title": "Lang", "default": "en" }, "email": { "type": "string", "title": "Email" }, "country": { "type": "string", "title": "Country" } } }
arguments 28 lines
conditions reads unknown 27h ago
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.

mcp-tool
{ "type": "object", "title": "conditionsArguments", "required": [ "resort" ], "properties": { "resort": { "type": "string", "title": "Resort" } } }
arguments 13 lines
snow_forecast reads unknown 11h ago
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.

mcp-tool
{ "type": "object", "title": "snow_forecastArguments", "required": [ "resort" ], "properties": { "resort": { "type": "string", "title": "Resort" } } }
arguments 13 lines
compare_resorts unknown 8h ago
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. Data stays useful without UI. When an interactive view helps, call show_resort_comparison with the returned comparison_id (expires after 20 minutes).

mcp-tool
{ "type": "object", "title": "compare_resortsArguments", "required": [ "resorts" ], "properties": { "days": { "enum": [ 3, 7 ], "type": "integer", "title": "Days", "default": 3 }, "nights": { "type": "integer", "title": "Nights", "default": 6, "maximum": 14, "minimum": 1 }, "resorts": { "type": "array", "items": { "type": "string" }, "title": "Resorts", "maxItems": 6, "minItems": 1 } } }
arguments 34 lines
webcams reads unknown 3h ago
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.

mcp-tool
{ "type": "object", "title": "webcamsArguments", "required": [ "resort" ], "properties": { "resort": { "type": "string", "title": "Resort" } } }
arguments 13 lines
mountain_facts reads unknown 27h ago
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.

mcp-tool
{ "type": "object", "title": "mountain_factsArguments", "required": [ "resort" ], "properties": { "resort": { "type": "string", "title": "Resort" } } }
arguments 13 lines
skier_notes reads unknown 27h ago
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.

mcp-tool
{ "type": "object", "title": "skier_notesArguments", "required": [ "resort" ], "properties": { "limit": { "type": "integer", "title": "Limit", "default": 8 }, "resort": { "type": "string", "title": "Resort" } } }
arguments 18 lines
trip_costs reads unknown 8h ago
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.

mcp-tool
{ "type": "object", "title": "trip_costsArguments", "required": [ "country" ], "properties": { "country": { "type": "string", "title": "Country" } } }
arguments 13 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.

Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
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.
Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id cb6ba56bf8eaad38.

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

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/cb6ba56bf8eaad38/badge.svg)](https://brick.blue/agent/cb6ba56bf8eaad38?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

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.