peaks.fyi — Mountain Routes, Huts & Weather is answering right now. Last checked 11 min ago. It exposes 15 tools.
European mountain routes, huts, access and forecasts with sources and explicit unknowns.
The linked repository no longer exists on GitHub — it was deleted or made private.
Uptime history
40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
15
Tools
read from the server
344 ms
Response time
average over 24h
open, no key
Access
streamable-http
This one has been quiet for a while
Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.
run in your terminal
claude mcp add mountains --transport http https://peaks.fyi/mcpSettings → Connectors → Add custom connector, then paste this address
https://peaks.fyi/mcp~/.codex/config.toml
[mcp_servers.mountains]
url = "https://peaks.fyi/mcp".cursor/mcp.json
{
"mcpServers": {
"mountains": {
"url": "https://peaks.fyi/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"mountains": {
"type": "http",
"url": "https://peaks.fyi/mcp"
}
}
}Available tools 15
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
route
get_route
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.
get_route_briefs
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.
get_route_point
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.
capabilities
get_capabilities
Inspect actual catalogue coverage, output JSON schemas, data version, units and unsupported operations before planning. Unknown data is not evidence of absence.
changes
get_changes
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.
daylight
get_daylight
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.
fetch
fetch
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.
huts
get_huts
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.
notices
get_notices
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.
peak
get_peak
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.
peaks
search_peaks
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.
resolve
resolve_peak
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.
routes
search_routes
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 season and public transport descriptions are not current operating confirmations. Read route details and conflicts before recommending.
search
search
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.
weather
get_weather
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 get_peak seasons instead, never invent a forecast or a safety verdict.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://peaks.fyi/mcp | streamable-http | answering | 462 ms | 11 min ago |
Alternatives to peaks.fyi — Mountain Routes, Huts & Weather
same job, measured the same way
T
Taiwan CWA Weather
by nigue3025
Access Taiwan CWA weather data and forecasts for all counties and cities
Windshield Weather
by windshieldweather
Weather forecasts along driving routes and highways.
WillyWeather MCP by UnClick
by malamutemayhem
Australian weather, surf, and tide forecasts from WillyWeather. By UnClick.
Weather MCP Server
by jaredco-ai
Fast - accurate weather conditions and forecasts by city or coordinates.
W
Weather of Record
by weatherofrecord
Published weather records for a U.S. address and date, with provenance, and current NWS forecasts.
Bike Router
by jonasheinickebio
Plan bike routes with a self-hosted OSM service: facts only, with weather and sights.
Open Meteo MCP
by mrfentmen
Open-Meteo weather, geocoding, elevation, and UV forecasts.
Agent Weather
by agentweather
Open-source intelligence for AI agents: public readings, each with its source and timestamp.
peaks.fyi — Mountain Routes, Huts & Weather — questions
Answers built from our own checks of this server.
What can peaks.fyi — Mountain Routes, Huts & Weather do?
It exposes 15 tools, read directly from the server on our last check. Among them: fetch, get_capabilities, get_changes, get_daylight, get_huts, get_notices and 9 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is peaks.fyi — Mountain Routes, Huts & Weather working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 344 ms. The bar chart above shows every period we have measured.
Is peaks.fyi — Mountain Routes, Huts & Weather still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect peaks.fyi — Mountain Routes, Huts & Weather?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does peaks.fyi — Mountain Routes, Huts & Weather need an API key?
No. peaks.fyi — Mountain Routes, Huts & Weather completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 15 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is peaks.fyi — Mountain Routes, Huts & Weather?
It answers our handshake in 344 ms on average, which is faster than 39% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.