Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Query the WPC WSSI MapServer at mapservices.weather.noaa.gov/vector/rest/services/outlooks/wpc_wssi/MapServer using the standard ArcGIS REST API (f=json for metadata, /query for features).
Select the specific WSSI element you need (overall index, snow-amount component, ice-amount component, population-impact, or travel-impact) — WSSI overlays NDFD forecast data with non-meteorological/climatological impact data.
Note the product updates roughly every 2 hours and covers Day 1-3 (24-hour periods) plus a 72-hour outlook.
For a quick visual check without building GIS query logic, use the WPC web display directly (wpc.ncep.noaa.gov/wwd/wssi/wssi.php?id=<office>) with a specific NWS office ID.
If you need it in an ArcGIS Online/Hub context rather than raw REST, the same layer is republished on NOAA's CloudGIS (noaa.hub.arcgis.com).
Known gotchas
This is a distinct product from generic NWS point/grid forecast APIs (api.weather.gov) — don't conflate WSSI with standard forecast endpoints.
The MapServer is not time-enabled in the ArcGIS sense — re-query on each update cycle rather than requesting a time-slider range.
WSSI is impact-based guidance layered on forecast data, not a raw obs feed — pair it with station/radar data, don't replace them.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?