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