topo^alpin
REMOTE · API.TOPOALPIN.APP
Avalanche bulletins, mountain weather, stations, huts, ski and snowshoe tours in the Alps.
Available components
Last scanned (20 hours ago)
Scores higher than 67% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability56
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3430 tokens (~381/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 98% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
- Tool “avalanche_bulletin” rewrote its description, which is the text the model reads security
- Tool “avalanche_overview” rewrote its description, which is the text the model reads security
- Server version: 3.2.1 → 3.3.0 functional
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 0
- Tool “mountain_forecast” rewrote its description, which is the text the model reads security
- Server version: 3.2.0 → 3.2.1 functional
- Server version: 3.1.0 → 3.2.0 functional
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “avalanche_overview” rewrote its description, which is the text the model reads security
- Tool “avalanche_bulletin” rewrote its description, which is the text the model reads security
- Tool “mountain_forecast” rewrote its description, which is the text the model reads security
- Tool “mountain_huts” rewrote its description, which is the text the model reads security
- Tool “station_observations” rewrote its description, which is the text the model reads security
- Tool “tour_terrain” rewrote its description, which is the text the model reads security
- Tool “winter_tours” rewrote its description, which is the text the model reads security
- Server version: 3.0.1 → 3.1.0 functional
- Server version: 2.1.1 → 3.0.1 functional
- Server version: 2.1.0 → 2.1.1 functional
- “avalanche_overview” added an optional parameter “limit” cosmetic
- “avalanche_overview” added an optional parameter “offset” cosmetic
- “avalanche_bulletin” reworded the description of “lat” cosmetic
- “avalanche_overview” reworded the description of “lat” cosmetic
- “mountain_forecast” reworded the description of “lat” cosmetic
- “mountain_huts” reworded the description of “lat” cosmetic
- “station_observations” reworded the description of “lat” cosmetic
- “tour_terrain” reworded the description of “lang” cosmetic
- “winter_tours” reworded the description of “lat” cosmetic
- “winter_tours” reworded the description of “radiusKm” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://api.topoalpin.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.topoalpin.app | CN=YE2,O=Let's Encrypt,C=US | 14 Nov 2026 | 12 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 5715452b109dbd7a62a1ae5d95573e80887 |
| SANs: api.topoalpin.app | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.topoalpin.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| topoalpin.app. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.topoalpin.app/mcp | Verified | 200 | |
| http (plaintext) | http://api.topoalpin.app/mcp | HTTPS enforced | 301 | https://api.topoalpin.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
avalanche_bulletin Avalanche danger level at a place ~579
The danger level where someone is going in the Alps, from the official avalanche bulletin: give a place name or the name of a warning region, or lat and lon, or a region id. The elevation of a named place or point is looked up unless you give elevationM. atPlace holds the level for that elevation and time of day and the avalanche problems there; reports hold who issued the bulletin, when, until when and when the next is due, all its ratings and problems, and its texts: main message, danger description, snowpack, weather and tendency. Set when=next for the following bulletin once it is out. Say the level from atPlace.levels with its elevation and time of day, the warning service, when it was issued and until when it applies. If problemsInTextOnly is true, the service names its avalanche problems in its texts only: read them from texts. If nearbyRegions is not empty, the place lies within 2 km of another region: name it with its own level, or that it has no report, since a tour may cross into it. If outsideDescribedElevation is true, the report describes this level at describedElevation only: say so, and do not apply the level to the place or call it lower there. If atPlace.regionsWithoutLevel is not empty, the place also lies in regions without a report: say that no level is available for them, and ask the user which side the tour is on if that matters. If a report has machineTranslatedFrom, say that topo^alpin machine-translated its texts from that language and give website for the original.
| Name | Type | Req | Description |
|---|---|---|---|
| aspect | string | – | Slope aspect: narrows the avalanche problems in atPlace. |
| detail | string | – | summary: ratings, problems and main message. full (default): all texts as plain text. original: also the bulletin as published. |
| elevationM | number | – | The elevation that matters, if not the one of the place itself. |
| lang | string | – | Language for region names and, if the service publishes in it, report texts. Default en. |
| lat | number | – | Latitude, WGS 84. topo^alpin covers the Alps only. |
| lon | number | – | Longitude, WGS 84. |
| placeId | string | – | When query matched several places, the placeId of the one the user means, from that list. Give it together with the same query. |
| query | string | – | Name of a summit, hut, pass or town, or of an area such as Valais or Tyrol for all its warning regions, or of a warning region. |
| regionId | string | – | EAWS micro-region id, from avalanche_region or avalanche_coverage. |
| when | string | – | Default current. |
| Name | Type | Req | Description |
|---|---|---|---|
| appUrl | string | yes | Opens this in the topo^alpin app. Share it with the user. |
| atPlace | – | yes | – |
| dataStale | boolean|null | yes | True: the data is older than its source is refreshed, or the source reports a fault. Say that it may be outdated. null: unknown, not fresh. |
| dataUpdatedAt | string|null | yes | When the data behind this answer was produced (ISO 8601, UTC; a date for a fixed release). With several sources, the oldest. null: unknown. |
| disclaimer | string | yes | Pass this on with every danger level: errors in processing are possible. |
| missing | string | – | Present where a report is missing. Pass it on. |
| nearbyRegions | array | yes | Other warning regions within 2 km of the place. A tour may cross into them: name them, with their own report or that they have none. atPlace does not include them. |
| next | string | – | Present when the next report is not out yet: the current one still applies. |
| notice | string | – | Pass this on with the danger level. |
| place | – | yes | – |
| references | object | yes | – |
| regions | array | yes | – |
| regionsWithoutReport | array | yes | – |
| reports | array | yes | – |
| sources | array | yes | Name these when using the data. |
| status | string | yes | Is there a report for this place at all? next: the following report, asked with when=next. |
No examples provided.
avalanche_coverage Where avalanche reports exist ~100
Is there an avalanche report at all right now, and in which regions? Lists every warning region in the Alps with a current report, grouped by warning service, with validity. Off season most regions have none. Contains no danger levels: use avalanche_bulletin for those.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language for region names and, if the service publishes in it, report texts. Default en. |
| service | string | – | Only this warning service. |
| Name | Type | Req | Description |
|---|---|---|---|
| anyCurrentReport | boolean | yes | Does any region in the Alps have a current report? |
| appUrl | string | yes | Opens this in the topo^alpin app. Share it with the user. |
| dataStale | boolean|null | yes | True: the data is older than its source is refreshed, or the source reports a fault. Say that it may be outdated. null: unknown, not fresh. |
| dataUpdatedAt | string|null | yes | When the data behind this answer was produced (ISO 8601, UTC; a date for a fixed release). With several sources, the oldest. null: unknown. |
| disclaimer | string | yes | Pass this on with every danger level: errors in processing are possible. |
| missing | string | – | Present where a report is missing. Pass it on. |
| regionsTotal | number | yes | – |
| regionsWithReport | number | yes | – |
| services | array | yes | – |
| sources | array | yes | Name these when using the data. |
No examples provided.
avalanche_overview Avalanche situation in an area ~372
How is the avalanche situation in a wider area of the Alps, such as Tyrol or the Valais? Give the name of a place or warning region, or lat and lon, with an optional radius, or a warning service. Returns the reports for the area with their danger levels per elevation, avalanche problems and main message, at most limit of them; offset gives the next ones. If regionsNotShown is present, the regions there have a report that is not listed: say so, never that they have none. For one destination use avalanche_bulletin. If a report has machineTranslatedFrom, say that topo^alpin machine-translated its texts from that language and give website for the original.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | Default summary: ratings, problems and main message. |
| lang | string | – | Language for region names and, if the service publishes in it, report texts. Default en. |
| lat | number | – | Latitude, WGS 84. topo^alpin covers the Alps only. |
| limit | integer | – | How many reports, default 10. |
| lon | number | – | Longitude, WGS 84. |
| offset | integer | – | How many reports to skip, default 0: for the ones after an answer with more. |
| placeId | string | – | When query matched several places, the placeId of the one the user means, from that list. Give it together with the same query. |
| query | string | – | Name of a summit, hut, pass or town, or of an area such as Valais or Tyrol for all its warning regions, or of a warning region. |
| radiusKm | number | – | Around a place or point, default 25. |
| service | string | – | All regions of this warning service. |
| Name | Type | Req | Description |
|---|---|---|---|
| appUrl | string | yes | Opens this in the topo^alpin app. Share it with the user. |
| area | object | yes | The area used. Check that it is the right one. |
| dataStale | boolean|null | yes | True: the data is older than its source is refreshed, or the source reports a fault. Say that it may be outdated. null: unknown, not fresh. |
| dataUpdatedAt | string|null | yes | When the data behind this answer was produced (ISO 8601, UTC; a date for a fixed release). With several sources, the oldest. null: unknown. |
| disclaimer | string | yes | Pass this on with every danger level: errors in processing are possible. |
| missing | string | – | Present where a report is missing. Pass it on. |
| more | string | – | Present where limit cut the list: there are more. Say so, or call again. |
| notice | string | – | Pass this on with the danger levels. |
| references | object | yes | – |
| regionsAsked | number | yes | How many warning regions lie in the area. |
| regionsNotShown | array | – | Present where limit cut the reports: the regions whose report is not in this answer. They have one: it is only not listed here. |
| regionsWithoutReport | array | yes | – |
| reports | array | yes | The reports for the area, in the order of the regions, at most limit of them. |
| sources | array | yes | Name these when using the data. |
| status | string | yes | Is there a report for this area at all? |
No examples provided.
avalanche_region Warning region of a place ~144
Does a summit, destination or point lie in an avalanche warning region of the Alps, in which one, and does it have a current report? Takes the name of a place or of a region, or up to 20 points such as start and summit of a tour. Also names other regions within 2 km.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language for region names and, if the service publishes in it, report texts. Default en. |
| points | array | – | – |
| query | string | – | Name of a summit, hut, pass or town, or of an area such as Valais or Tyrol for all its warning regions, or of a warning region. |
| Name | Type | Req | Description |
|---|---|---|---|
| appUrl | string | yes | Opens this in the topo^alpin app. Share it with the user. |
| dataStale | boolean|null | yes | True: the data is older than its source is refreshed, or the source reports a fault. Say that it may be outdated. null: unknown, not fresh. |
| dataUpdatedAt | string|null | yes | When the data behind this answer was produced (ISO 8601, UTC; a date for a fixed release). With several sources, the oldest. null: unknown. |
| disclaimer | string | yes | Pass this on with every danger level: errors in processing are possible. |
| missing | string | – | Present where a report is missing. Pass it on. |
| namedRegions | array | yes | Regions whose own name matches the query. |
| placeSearchFailed | boolean | yes | – |
| places | array | yes | – |
| sources | array | yes | Name these when using the data. |
No examples provided.
mountain_forecast Mountain weather forecast at a place ~374
The weather forecast at a place in the Alps, for its elevation: weather, precipitation, fresh snow, freezing level, temperature, wind and gusts, sunshine and thunderstorm risk, in six-hour periods of local time for up to ten days. Computed from several weather models like the forecast in the topo^alpin app. Say the elevation elevationM and the period, and the weather, precipitation, fresh snow, freezing level, wind with gusts and thunderstorm risk where they matter. temperatureC is the spread of the models, from the coldest to the warmest: give it as a range. Where freezingLevelSource is estimate, the freezing level is carried from the temperature at the place: call it estimated. Where precipitationMm is above 0 and rainMm and fresh snow are 0, only a trace falls: say so, not that it stays dry. A period marked past has ended: do not give it as forecast, and say that the day totals include it.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | One day, YYYY-MM-DD in local time. Without it, from today. |
| days | integer | – | Days from today, if no date is given. Default 3. |
| elevationM | number | – | The elevation that matters, if not the one of the place itself. |
| lang | string | – | Language for place names. Default en. |
| lat | number | – | Latitude, WGS 84. topo^alpin covers the Alps only. |
| lon | number | – | Longitude, WGS 84. |
| placeId | string | – | When query matched several places, the placeId of the one the user means, from that list. Give it together with the same query. |
| query | string | – | Name of a summit, hut, pass or town. |
| Name | Type | Req | Description |
|---|---|---|---|
| appUrl | string | yes | Opens this place and its forecast in the topo^alpin app. |
| availableDates | array | yes | Days with a forecast, from today. |
| dataStale | boolean|null | yes | True: the data is older than its source is refreshed, or the source reports a fault. Say that it may be outdated. null: unknown, not fresh. |
| dataUpdatedAt | string|null | yes | When the data behind this answer was produced (ISO 8601, UTC; a date for a fixed release). With several sources, the oldest. null: unknown. |
| days | array | yes | – |
| disclaimer | string | yes | Pass this on with every forecast. |
| elevationM | number|null | yes | The elevation the values apply to. |
| elevationSource | – | yes | model-grid: no elevation known, the values apply to the model terrain. |
| missing | string | – | Present where there is no forecast. Pass it on. |
| modelRuns | – | – | The run behind each model. null: the state of the weather server is unknown. |
| models | array | yes | The weather models combined. |
| notice | string | – | Pass it on. |
| place | object | yes | – |
| sources | array | yes | Name these when using the data. |
No examples provided.
mountain_huts Mountain huts near a place ~273
The mountain huts nearest to a place in the Alps, or to where the user stands: name, distance and direction in a straight line, elevation and the difference to the place, mountain hut or self-catering, operator, beds and contact, as far as OpenStreetMap has them. Not opening times, free places or prices. Say how far, in which direction and how much higher or lower each hut lies, in a straight line, and pass on the field notice: whether a hut is staffed, opening times, free places and prices are not in the data.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language for names. Default en. |
| lat | number | – | Latitude, WGS 84. topo^alpin covers the Alps only. |
| limit | integer | – | How many huts. Default 5. |
| lon | number | – | Longitude, WGS 84. |
| placeId | string | – | When query matched several places, the placeId of the one the user means, from that list. Give it together with the same query. |
| query | string | – | Name of a summit, hut, pass or town. |
| radiusKm | number | – | Search radius. Default 10. |
| selfCatering | boolean | – | Only bivouacs and self-catering huts. Default false. |
| Name | Type | Req | Description |
|---|---|---|---|
| appUrl | string | yes | Opens this place in the topo^alpin app. |
| dataStale | boolean|null | yes | True: the data is older than its source is refreshed, or the source reports a fault. Say that it may be outdated. null: unknown, not fresh. |
| dataUpdatedAt | string|null | yes | When the data behind this answer was produced (ISO 8601, UTC; a date for a fixed release). With several sources, the oldest. null: unknown. |
| disclaimer | string | yes | Automatic and possibly outdated. Pass it on. |
| elevationM | number|null | yes | The elevation differences refer to this. |
| elevationSource | – | yes | Where elevationM comes from: input (given), place (of the place found) or terrain (our terrain model at the point). null: no elevation known. |
| huts | array | yes | Nearest first. |
| missing | string | – | Present where there is no hut. Pass it on. |
| more | string | – | Present where limit cut the list: there are more. Say so, or call again. |
| notice | string | yes | Pass this on with the huts. |
| place | object | yes | – |
| radiusKm | number | yes | – |
| sources | array | yes | Name these when using the data. |
No examples provided.
station_observations What weather stations measure near a place ~296
What the weather stations near a place in the Alps measure now: temperature, snow depth, fresh snow, wind and gusts, each with the time of the measurement, and optionally the last days. Measured, not forecast, at the place and elevation of the station. Stations are chosen by distance and elevation difference, like in the topo^alpin app. Say which station, its elevation, how far away it is and when it measured: a station measures at its own place and elevation, not at the destination. A value of null means nothing current, never zero.
| Name | Type | Req | Description |
|---|---|---|---|
| elevationM | number | – | The elevation that matters, if not the one of the place itself. |
| history | boolean | – | Also the last days per station, one line per day. Default false. |
| lang | string | – | Language for names. Default en. |
| lat | number | – | Latitude, WGS 84. topo^alpin covers the Alps only. |
| limit | integer | – | How many stations. Default 3. |
| lon | number | – | Longitude, WGS 84. |
| placeId | string | – | When query matched several places, the placeId of the one the user means, from that list. Give it together with the same query. |
| query | string | – | Name of a summit, hut, pass or town. |
| radiusKm | number | – | Search radius. Default 25. |
| Name | Type | Req | Description |
|---|---|---|---|
| appUrl | string | yes | Opens this place in the topo^alpin app. |
| dataStale | boolean|null | yes | True: the data is older than its source is refreshed, or the source reports a fault. Say that it may be outdated. null: unknown, not fresh. |
| dataUpdatedAt | string|null | yes | When the data behind this answer was produced (ISO 8601, UTC; a date for a fixed release). With several sources, the oldest. null: unknown. |
| disclaimer | string | yes | Pass this on with every measurement. |
| elevationM | number|null | yes | The elevation stations were chosen for. |
| elevationNotice | string | – | Present where a station measures far above or below the elevation asked. Pass it on. |
| elevationSource | – | yes | Where elevationM comes from: input (given), place (of the place found) or terrain (our terrain model at the point). null: no elevation known. |
| missing | string | – | Present where there is no station. Pass it on. |
| more | string | – | Present where limit cut the list: there are more. Say so, or call again. |
| place | object | yes | – |
| radiusKm | number | yes | – |
| sources | array | yes | Name these when using the data. |
| stations | array | yes | Best match first, by distance and elevation difference. |
No examples provided.
tour_terrain Terrain of a ski or snowshoe tour ~225
The terrain of one ski or snowshoe tour in the Alps, by the id from winter_tours: how steep it is and for how long, the aspects of the steep slopes, how much lies in avalanche terrain (ATES and ATM), stretch by stretch, and the grade explained with the words of the SAC scale and who gave it. Terrain only, computed from terrain models; not snow or avalanche conditions. Name ATES and ATM with what terrainExplained says they are, and compare aspectsSteep and the elevations with the avalanche bulletin, without turning them into a go/no-go. Where atm lists runout, avalanches from slopes above can reach the line, also below 30° and with ates 0: say so. Pass on gradeSources with the grades, and name terrain.onFoot, the part on foot above the ski depot, with the grade: it is often the steepest.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The id of a tour from winter_tours. |
| lang | string | – | Language for the grade scale and titles. Default en. |
| Name | Type | Req | Description |
|---|---|---|---|
| appUrl | string | yes | Opens this tour in the topo^alpin app, on the map. Give it to the user. |
| dataStale | boolean|null | yes | True: the data is older than its source is refreshed, or the source reports a fault. Say that it may be outdated. null: unknown, not fresh. |
| dataUpdatedAt | string|null | yes | When the data behind this answer was produced (ISO 8601, UTC; a date for a fixed release). With several sources, the oldest. null: unknown. |
| disclaimer | string | yes | Automatic and possibly outdated. Pass it on. |
| gradeSources | object | yes | Each gradeSource in this answer, once: who gives the grade. Pass it on with the grades. |
| missing | string | – | Present where there is no terrain data. Pass it on. |
| notice | string | yes | Terrain, not conditions. Pass it on. |
| scale | – | yes | The grade on the SAC scale in the language asked for: name, steepness and the criteria of the SAC. null without a grade. |
| sources | array | yes | Name these when using the data. |
| terrain | – | yes | null where there is no terrain data: unknown, not flat. |
| terrainExplained | object | yes | What the terrain values mean, once per answer. Explain them when you name them. |
| tour | object | yes | – |
No examples provided.
winter_tours Ski and snowshoe tours at a place ~406
Ski and snowshoe tours in the Alps at a place: the routes up to a summit, hut or pass, and the routes that start in a valley or at a hut. Each with title, grade in the scale of the language, elevation gain, length, and the start seen from the place. From the guidebook and portal data shown in the topo^alpin app; not current conditions. Say the grade, the elevation gain, where the route starts and who gave the grade: gradeSource on each tour, explained once in gradeSources; a grade with ~ is estimated by topo^alpin. Give each tour with its appUrl, which opens it in the topo^alpin app. Say where each route in startingHere starts: it can lie in another valley, across a pass. Where target.endBelowM is above 30, the line ends at a ski depot that far below the summit and the rest is not in the route: say so. Pass on the field notice, check avalanche_bulletin for the tour, and use tour_terrain for how steep it is and how much lies in avalanche terrain.
| Name | Type | Req | Description |
|---|---|---|---|
| discipline | string | – | Only ski or only snowshoe tours. Default both. |
| lang | string | – | Language for titles and grades. Default en. |
| lat | number | – | Latitude, WGS 84. topo^alpin covers the Alps only. |
| limit | integer | – | How many tours per list. Default 10. |
| lon | number | – | Longitude, WGS 84. |
| placeId | string | – | When query matched several places, the placeId of the one the user means, from that list. Give it together with the same query. |
| query | string | – | Name of a summit, hut, pass or town. |
| radiusKm | number | – | How far a start in startingHere may lie from the place; routes up to it count wherever they start. Default 5. |
| Name | Type | Req | Description |
|---|---|---|---|
| appUrl | string | yes | Opens this place in the topo^alpin app. |
| dataStale | boolean|null | yes | True: the data is older than its source is refreshed, or the source reports a fault. Say that it may be outdated. null: unknown, not fresh. |
| dataUpdatedAt | string|null | yes | When the data behind this answer was produced (ISO 8601, UTC; a date for a fixed release). With several sources, the oldest. null: unknown. |
| disclaimer | string | yes | Automatic and possibly outdated. Pass it on. |
| elevationM | number|null | yes | – |
| elevationSource | – | yes | Where elevationM comes from: input (given), place (of the place found) or terrain (our terrain model at the point). null: no elevation known. |
| gradeSources | object | yes | Each gradeSource in this answer, once: who gives the grade. Pass it on with the grades. |
| missing | string | – | Present where there is no tour. Pass it on. |
| more | string | – | Present where limit cut the list: there are more. Say so, or call again. |
| notice | string | yes | Pass this on with the tours. |
| place | object | yes | – |
| radiusKm | number | yes | How far a start in startingHere may lie from the place. |
| sources | array | yes | Name these when using the data. |
| startingHere | array | yes | Routes that start within radiusKm of the place in a straight line, nearest first; a start can lie in another valley, across a pass. Say where it starts. Empty at a summit. |
| terrainExplained | object | yes | What the terrain values mean, once per answer. Explain them when you name them. |
| toSummit | array | yes | Routes up to the place, ascents first, then descents from it: they end within 1 km of it, wherever they start. radiusKm does not apply to them. |
No examples provided.
How do I install the topo^alpin MCP server?
topo^alpin is a hosted endpoint at https://api.topoalpin.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.topoalpin.app
claude mcp add --transport http app-topoalpin-mcp 'https://api.topoalpin.app/mcp'
What is the topo^alpin MCP server?
topo^alpin is an MCP server listed in the public MCP registry as app.topoalpin/mcp. Avalanche bulletins, mountain weather, stations, huts, ski and snowshoe tours in the Alps. This page covers its hosted endpoint (https://api.topoalpin.app/mcp).
Is the topo^alpin MCP server safe to use?
topo^alpin scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the topo^alpin MCP server expose?
topo^alpin exposes 9 tools: avalanche_coverage, avalanche_region, avalanche_overview, avalanche_bulletin, mountain_forecast, and 4 more. Their descriptions and schemas cost roughly 2,769 tokens of context every time the server is loaded.
Does the topo^alpin MCP server require authentication?
No. We connected to topo^alpin without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the topo^alpin MCP server still maintained?
topo^alpin is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the topo^alpin MCP server?
VerifyMCP ran 13 checks on topo^alpin, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.