avalanche_danger_rating_by_point
Get the current avalanche danger rating and forecast metadata for the avalanche zone containing a latitude/longitude point. Can fall back to the nearest zone.
LABSCO SUMMARY
Resolving a coordinate to its forecast zone is the whole value: the ratings are public, the zone boundaries are what make them answerable from a GPS point.
Avalanche forecasts are published per zone, and a zone is a polygon most people cannot name from memory. Handing the server a latitude and longitude and getting back the rating that applies there removes the step where someone guesses which forecast covers the trailhead. The historic lookup is the quieter half and is what makes this useful after the fact — reconstructing what the rating was on the day of an incident or a trip report. This reports what the forecast centers published; it is not a substitute for the forecast itself, which carries the problem types and travel advice that a rating number does not.
What it is
A client for Avalanche.org's forecast data with four tools: current and historic danger ratings resolved from a coordinate, and the raw map-layer GeoJSON for all avalanche centers or one of them.
What you get
- avalanche_danger_rating_by_point takes a latitude and longitude and returns the danger rating plus the forecast metadata for the zone that contains it — the coordinate-to-zone lookup being the part that is otherwise manual.
- historic_avalanche_danger_rating_by_point does the same for a date in the past.
- raw_map_layer returns the GeoJSON FeatureCollection for every avalanche center, and raw_map_layer_by_avalanche_center narrows it to one.
Requirements
Nothing to supply — the Avalanche.org data is public.
Setup effort
One command — npx -y avalanche-org-mcp-server
USE CASES
01
Checking the rating for a specific place
Pass the trailhead's coordinates and get the danger rating for the zone that actually contains it, without working out which forecast applies.
02
Reconstructing conditions on a past date
Look up what the rating was at that coordinate on the day in question, for a trip report or an incident review.
03
Working with the zones themselves
Pull the raw GeoJSON for all centers or one, when you need the boundaries rather than a single point's answer.
4 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
historic_avalanche_danger_rating_by_point
Get the avalanche danger rating and forecast metadata for the avalanche zone containing a latitude/longitude point on a specific historic day (YYYY-MM-DD). Can fall back to the nearest zone.
raw_map_layer
Return the raw Avalanche.org map-layer GeoJSON FeatureCollection for all avalanche centers. Supports an optional historic day (YYYY-MM-DD).
raw_map_layer_by_avalanche_center
Return the raw Avalanche.org map-layer GeoJSON FeatureCollection for a specific avalanche center ID. Supports an optional historic day (YYYY-MM-DD).
BEFORE YOU INSTALL
What to know first
Tools you get
4 tools when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 4 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"avalanche-org-mcp-server": {
"command": "npx",
"args": [
"-y",
"avalanche-org-mcp-server"
]
}
}
}npx
TERMINAL
npx -y avalanche-org-mcp-server
