Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
For a specific recent date, check spc.noaa.gov/climo/reports/YYMMDD_rpts.html (e.g., .../climo/reports/260520_rpts.html) or spc.noaa.gov/climo/reports/today.html for same-day hail/wind/tornado report listings
For the interactive/current view, use spc.noaa.gov/exper/reports/ to browse reports by map and date range
For structured historical data covering a specific address or county, query NOAA NCEI's Storm Events Database at ncei.noaa.gov/stormevents/, which lets you filter by event type (Hail), state/county, and date range
For programmatic/bulk access to severe weather station-level data (including hail size and location), use the Severe Weather Data Inventory (SWDI) at ncei.noaa.gov/maps/swdi/ or its bulk data mirror
Cross-reference the hail report's date and location against specific property addresses before canvassing or filing an insurance claim, since SPC reports are storm-scale (county/point) observations, not building-level damage assessments
Document the specific report source and timestamp used (SPC report vs. NCEI Storm Events record) in any insurance-facing documentation, since adjusters may ask which NOAA dataset supports a claimed hail event date
Known gotchas
SPC 'storm reports' (spc.noaa.gov/climo/reports) are preliminary, unfiltered public reports and can include duplicate or unverified sightings — NCEI's Storm Events Database is the quality-controlled, official record used for formal documentation
A hail report near an address does not by itself prove damage occurred at that property — it establishes that a hail event was reported in the vicinity on that date, which contractors typically pair with a physical roof inspection
If this cluster's corpus already has a general-purpose SPC/NOAA storm-data route, this entry should be treated as the roofing-canvassing-specific angle only (address-level hail-event lookup for claims workflows), not a duplicate of a general severe-weather-data route — verify against the existing corpus before publishing
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?