Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
peaks.fyi — Mountain Routes, Huts & Weather is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
European mountain routes, huts, access and forecasts with sources and explicit unknowns.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http peaks-fyi-mountain-routes-huts-weather-mcp https://peaks.fyi/mcp
# 2 — ask your agent for something these tools do
# get_route_briefs, get_capabilities, get_notices and 12 more
peaks.fyi — Mountain Routes, Huts & Weather costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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 and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http peaks-fyi-mountain-routes-huts-weather-mcp https://peaks.fyi/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
15 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.
Compare up to six known routes in one compact evidence packet: grade, timing conflicts, selected equipment, linked huts, access, notices and optional dated daylight. Preserves per-route errors and source provenance. Partial results must not be treated as complete; no booking, live transport or suitability guarantee. Use get_route for full details and get_weather for forecasts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| routes | array | yes | One to six known peak slug / route ID pairs from search_routes; not free-text names. |
| date | string | no | — |
| sections | array | no | — |
Inspect actual catalogue coverage, output JSON schemas, data version, units and unsupported operations before planning. Unknown data is not evidence of absence.
No parameter schema on file.
Read dated notices with publication validity, explicit scope uncertainty and recurrence hints. Supply slug and the trip date; omitted date means today (UTC), echoed in requestedDate. Expired notices may describe recurring regulations; expiry is not evidence that access is open. Verify current law with the linked source.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Peak slug returned by search, for example mont-blanc. |
| date | string | no | Trip date, YYYY-MM-DD. Omit to check today's UTC date, which is echoed in requestedDate. |
| routeId | string | no | — |
Resolve a canonical peak ID, external Wikidata/OSM ID, current slug or exact name to its current slug and citable URL. Example input: {"id":"Ben Nevis"}. Use canonical IDs to recover from renamed slugs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Canonical peak:id, Wikidata Q ID, OSM ID, current slug or exact translated name. |
Compare a watched set of peaks with a previous snapshot. Returns content changes, removals and an updated snapshot. No changes means no new source data, not proof that conditions are unchanged. Date-dependent notice status must still be checked.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slugs | array | yes | — |
| previous | array | no | — |
Compute sunrise, sunset and civil twilight for the exact calendar date and IANA zone. UTC instants handle daylight saving and polar days. Terrain and weather can reduce usable daylight.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Peak slug returned by search, for example mont-blanc. |
| date | string | yes | — |
| timeZone | string | no | Optional explicit IANA zone; defaults to the catalogue zone. |
Search peaks.fyi by mountain name, alternative name, country, range or climbing request. Returns citable peak IDs and URLs. Use fetch to read a result; use search_peaks for explicit filters and pagination. An empty result means no match in this catalogue, not that the mountain does not exist.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Peak name, alias, country, range, or request such as hiking in Austria in July. |
Read a peak search result by catalogue slug as a citable text document. Example input: {"id":"ben-nevis"}. This retrieves catalogue documents, not external website URLs; use your own browsing tool for publisher pages. Includes routes, season, access, hazards, huts, notices and provenance. Use get_weather for current forecasts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Peak ID (slug) from search. |
Get compact peak facts and route IDs. Example input: {"slug":"ben-nevis"}. Optionally request access, huts, seasons, hazards or provenance sections. For fact questions search may already suffice. For current weather use get_weather; for hut booking information use get_huts. Research is not live availability.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Peak slug returned by search, for example mont-blanc. |
| sections | array | no | Omit for a compact overview, route IDs, season and notices. Request only sections needed. |
Get one route by peak slug and routeId from get_peak: grade, equipment, key passages, stages, trailhead, timing, confidence and geometry QA. Failed, truncated or outline geometry must not be used for navigation. Times are estimates. No live route safety or opening guarantee.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Peak slug returned by search, for example mont-blanc. |
| routeId | string | yes | Route ID from get_peak or search_routes. |
| includeDescription | boolean | no | — |
Look up a named waypoint or difficult passage on a route. Returns source notes, known coordinates, nearby stage names, key passages and relevant equipment. Missing coordinates or conditions remain unknown; this is not live navigation guidance.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Peak slug returned by search, for example mont-blanc. |
| routeId | string | yes | — |
| query | string | yes | Name of a waypoint or key passage, e.g. Grand Couloir or halfway lochan. |
Read huts, documented seasonal operation, source years and booking/contact URLs for a peak. Beds means capacity, never vacancies. Live availability, reservations, rental inventory and current opening status are unknown. Do not infer next year's opening dates from a dated season; contact the linked provider.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Peak slug returned by search, for example mont-blanc. |
| hutId | string | no | — |
| date | string | no | Planning date; does not turn published seasons into live availability. |
Find routes satisfying all supplied constraints on the SAME route, including difficulty, glacier travel, style and computed round-trip hours. Unknown glacier status is excluded by glacier filters. Searches all candidate peaks; use nextCursor until null for complete results. Coordinates filter peak locations, not trailheads. Transport matches documented prose, not confirmed operation. Historical se
| Parameter | Type | Required | Notes |
|---|---|---|---|
| near | object | no | — |
| bbox | array | no | Exactly [west,south,east,north] in degrees; west > east crosses the antimeridian. |
| query | string | no | — |
| cursor | string | no | Opaque nextCursor from the same query. Bound to the catalogue revision and filters. |
| countries | array | no | — |
| month | integer | no | — |
| maxDifficulty | integer | no | — |
| maxRoundTripHours | number | no | — |
| glacier | string | no | — |
| styles | array | no | — |
| publicTransport | boolean | no | Require documented transport to the trailhead; schedules and operating dates still need checking. |
| limit | integer | no | — |
Get published weather for a peak and optional summit/hut/trailhead target. Set targetId and start/end for a bounded planning response; unfiltered forecasts can be large. Point samples are separate from accumulated rain/snow intervals and complete-window totals. Check target coverage and missing fields. Stale is marked; expired, missing and far-future data is unavailable. For a trip months away use
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Peak slug returned by search, for example mont-blanc. |
| view | string | no | Compact retains requested weather, intervals, uncertainty and coverage, omitting auxiliary per-point fields. Follow fullData for all fields. |
| start | string | no | Inclusive forecast interval start, ISO 8601 with time zone. |
| end | string | no | Exclusive forecast interval end, ISO 8601 with time zone. |
| targetId | string | no | Optional exact summit, hut or trailhead target ID. Omit to see all targets. |
Find and compare mountains with explicit country, elevation, season, difficulty and glacier filters. All filters are hard constraints; never silently relaxed. Returns compact peak summaries, IDs, total and nextOffset. Read get_peak and get_route before recommending a route: peak-level filters can describe different routes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Peak name, alias, country, range, or request such as hiking in Austria in July. |
| near | object | no | — |
| bbox | array | no | Exactly [west,south,east,north] in degrees; west > east crosses the antimeridian. |
| countries | array | no | — |
| month | integer | no | Month with a good historical climbing season; not a weather forecast. |
| minElevationM | number | no | — |
| maxElevationM | number | no | — |
| maxDifficulty | integer | no | 1–2 easy hike, 3 mountain hike, 4 alpine hike/F, 5 PD, 6 AD, 7 D, 8 TD, 9 ED, 10 extreme. Peak-level minimum, not a guarantee for every route. |
| glacier | string | no | — |
| limit | integer | no | Page size, at most 20. Omit for 10. Use nextOffset to request another page. |
| offset | integer | no | Start at 0; use nextOffset from the preceding response for subsequent pages. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install peaks.fyi — Mountain Routes, Huts & Weather or to call it, at any volume.
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.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_route_briefs | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_capabilities | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_notices | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| resolve_peak | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_changes | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_daylight | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| search | untrusted-input | untrusted-input: keyword "fetch", declares openWorldHint: true (interacts with entities outside the server) |
| fetch | untrusted-input | untrusted-input: keyword "fetch", declares openWorldHint: true (interacts with entities outside the server) |
| get_peak | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_route | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_route_point | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_huts | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| search_routes | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_weather | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| search_peaks | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 3.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish peaks.fyi — Mountain Routes, Huts & Weather can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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 a signed-in account that does not publish it, and nothing else.