Stormaxis Mcp
@walker-capital
About Stormaxis Mcp
Real-time US storm intelligence for roofing and restoration contractors. Scored opportunities, property targeting, canvass routing, and FEMA claim data from live NOAA/SPC feeds.
Config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"stormaxis": {
"transport": "streamable-http",
"url": "https://stormaxis.io/api/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}Tools
21Get a real-time overview of active storm activity across the US. Returns active storm counts by type (hail, tornado, wind, flood), top affected states, and current SPC convective outlook level. Updated every 15 minutes from live NOAA/SPC feeds. No parameters required. Use this as a starting point to understand current storm conditions before drilling into specific opportunities.
Get scored forecast opportunities — storms that haven't hit yet. Analyzes today's and tomorrow's SPC convective outlooks (hail, wind, tornado probability polygons) and cross-references with property exposure data to predict WHERE the best revenue opportunities will be BEFORE storms actually hit. Returns ranked opportunities with: threat type, probability, estimated hail size/wind speed, buildings at risk, estimated revenue, and top affected cities. Use this to give contractors advance notice of where to position crews and pre-stage materials. No parameters required.
Get top-scored storm opportunities from the last 30 days. Returns storms ranked by opportunity score (0-100) with revenue estimates, affected property counts, and classification. Args: state: Filter by 2-letter state code (e.g. 'TX', 'OK'). Optional. min_score: Minimum opportunity score threshold (0-100). Default 60. limit: Maximum results. Default 10, max 50.
Get the detailed opportunity score breakdown for a specific storm. Returns the composite score (0-100) and breakdown by component: - Storm Relevance: recency, magnitude, NWS confirmation - Property Economics: avg property value, roof age, density - Replacement Probability: ML model prediction Args: storm_id: The storm noaa_event_key or episode ID.
Search the property database for targetable properties in a ZIP code. Returns property records with: owner name, property address, building sqft, roof age estimate, property value, and owner type. Args: zip_code: 5-digit US ZIP code (e.g. '76109'). owner_type: Filter by 'individual', 'joint', or 'entity'. Optional. min_roof_age: Minimum roof age in years. Optional. min_sqft: Minimum building square footage. Optional. limit: Max results. Default 50, max 100.
Get a full storm history + roof damage report for a single property address. Geocodes the address, snaps to the nearest Overture building footprint, pulls every storm polygon within 1 km whose begin_time falls inside the lookback window, joins per-storm damage signals (replacement-probability ML score), and returns an estimated repair cost band plus FEMA claim propensity for the property's ZIP. Use this when a user asks something like "has this house been hit?", "what's the damage at <address>?", or "should I door-knock this property?". For batch lookups (>5 addresses at once), recommend the /api/v1/commercial/roof-report/bulk REST endpoint instead — this tool is sized for one address at a time. Args: address: Full US street address — e.g. "123 Main St, Austin TX 78701". Ambiguous or un-geocodable addresses return an error. lookback_days: How many days back to scan storm history. Default 90. Range 1–3650 (10 years). years: Convenience alias — same as lookback_days but expressed in years. If both are provided, ``years`` wins. SA-11: previously silently ignored; now correctly mapped to lookback_days = years * 365. Returns JSON with: - coordinates: {lat, lng} from Nominatim geocode - building: nearest Overture building (class, footprint_sqft, roof_material, etc.) - storm_history: events, direct_hits count, and per-event detail - damage_assessment: replacement_probability and worst_event - estimated_repair_cost: {low_usd, expected_usd, high_usd} - claim_propensity: FEMA registrants + approved $ for the property's ZIP - audit_trail: request_id + data_sources used (replayable via /audit/{request_id})
Get pre-computed H3 canvass clusters for a storm event. Returns hexagonal grid clusters ranked by canvass priority. Pre-computed at scoring time for instant results. Each cluster: center coords, buildings, values, roof age, priority score. Args: storm_id: Storm episode ID (e.g. "1774224000870"). min_score: Minimum priority score (0-1). Default 0.3. limit: Max clusters. Default 20.
Generate neighborhood-level door-knocking targets for a storm. Returns ZIP clusters ranked by canvass priority with property details. Each cluster includes: buildings, roof ages, property values, distance from storm center, and individual property addresses with owner names. Use this to plan canvassing routes — start with the highest priority clusters (older roofs, more buildings, closer to storm center). Args: storm_id: Storm episode ID (e.g. "1774224000870") or noaa_event_key. radius_miles: Search radius from storm center. Default 15 miles. min_roof_age: Only include areas with roofs this age or older. Default 10 years. limit: Max clusters to return. Default 20.
Get insurance claim propensity data by state/region. Returns claim culture scores indicating how likely property owners in each state are to file insurance claims after storm damage. Higher scores = more claim-friendly = better for contractors. Args: state: Filter to a specific state (2-letter code). Optional.
Get historical FEMA NFIP flood insurance claims for a state. Returns aggregated claim data showing frequency and dollar amounts of flood-related insurance claims by ZIP code and year range. Args: state: 2-letter state code (required). year_start: Start year for query range. Default 2015. year_end: End year for query range. Default 2026.
Check the health and status of the StormAxis data pipeline. Returns: last ingestion timestamps for each data source, record counts, data freshness indicators, and any active pipeline alerts. Use this to verify data recency before making decisions based on storm data.
Get active water damage events in a contractor's territory, scored by urgency for restoration response prioritization. Returns events ranked by urgency score with estimated revenue, hours since onset, and damage category (pipe_burst, flood, storm_drain_backup, sewer_backup, appliance_failure, roof_leak). Args: org_id: Organization ID of the requesting contractor. min_tier: Minimum urgency tier to return. One of "critical", "high", "moderate", "low". Default "moderate". limit: Maximum number of events to return. Default 20, max 100.
Get the current water damage urgency score for a ZIP code, including factor breakdown and revenue estimate. Scores are computed from 6 weighted factors: - hours_since_onset (time decay — urgency peaks 0–6 h, drops after 72 h) - nfip_density (flood insurance policy concentration) - building_age_risk (pre-1960 structures heavily weighted) - nws_event_severity (NWS watch/warning/advisory classification) - soil_saturation_index (antecedent moisture from USDA/SNODAS) - prior_claim_rate (ZIP-level historical NFIP claim frequency) Args: zip_code: 5-digit ZIP code to score. event_id: Specific water event ID to score against. If omitted, scores against the highest-urgency active event in the ZIP.
Get a prioritized property list for water restoration dispatch after a water event. Properties are ranked by urgency score, damage category, NFIP coverage likelihood, and prior claim history. Use this to build the dispatch call list and load into your CRM immediately after an event triggers. First mover advantage is critical — the window for emergency restoration work closes fast. Args: event_id: Water event ID to dispatch against. org_id: Organization ID of the dispatching contractor. limit: Maximum properties to return. Default 100, max 500. min_urgency: Minimum property-level urgency score (0.0–1.0). Default 0.0.
Get a customized door-knock script for water restoration canvassing based on event type and property profile. Scripts are tailored to NWS event type (flood vs. freeze vs. storm drain) and include insurance-specific language when NFIP density is high in the ZIP. Args: event_type: NWS event type string, e.g. "Flash Flood Warning", "Hard Freeze Warning", "Areal Flood Advisory". zip_code: 5-digit ZIP code for property-specific customization. Optional. contractor_name: Contractor company name for script personalization. Optional.
Get active mold risk alerts for open water restoration jobs. Alerts fire when elapsed time combined with humidity forecast indicates mold onset is imminent (typically 24–48 h after water intrusion at >60% RH). Use this to prioritize follow-up calls on open jobs and upsell mold remediation before it becomes visible. Args: org_id: Organization ID of the contractor. min_risk_score: Minimum mold risk score (0.0–1.0) to return. Default 0.6.
Get real-time USGS stream gauge readings near a location. Indicates active riverine flooding risk with 6–24 hour lead time before water reaches downstream properties. Gauges above "action stage" signal imminent flood dispatch opportunities. Gauges at "flood stage" or above indicate active inundation in progress. Args: zip_code: 5-digit ZIP code to find nearby gauges. Use this OR lat/lon. lat: Latitude decimal degrees (WGS84). Use with lon instead of zip_code. lon: Longitude decimal degrees (WGS84). Use with lat instead of zip_code. radius_km: Search radius in kilometers. Default 75.
Get water restoration dashboard KPIs for a contractor organization. Returns a snapshot suitable for rendering the water restoration dashboard widget: active event count, total revenue opportunity, mold alerts, jobs created in the last 30 days, and top urgency ZIP codes. Args: org_id: Organization ID of the contractor.
Get a water damage risk profile for a contractor's service territory. Identifies highest-risk ZIP codes by building age, NFIP policy density, CSO (combined sewer overflow) community exposure, and soil saturation. Use this to prioritize marketing spend and pre-position crews. Args: org_id: Organization ID of the contractor. include_zips: If True, include per-ZIP risk breakdown in the response. Default False (summary only).
Get NFIP flood insurance policy density for a ZIP code. High NFIP density indicates a strong flood claim filing culture and higher probability of insurance-paid restoration jobs. Density above ~20 policies per 100 housing units is considered high signal territory. Policy data sourced from FEMA NFIP policy-in-force dataset, refreshed monthly. Args: zip_code: 5-digit ZIP code to look up.
Get building age cohort data for a ZIP code. Building age is the #1 predictor of pipe burst and water intrusion risk. Pre-1960 structures have galvanized supply pipes and no vapor barriers. 1960–1980 structures have polybutylene pipe (recalled, failure-prone). Post-2000 structures have modern PEX but may have improper grading. Age cohort percentages are derived from Census ACS 5-year estimates and county assessor parcel data. Args: zip_code: 5-digit ZIP code to profile.
Overview
What is Stormaxis Mcp?
Stormaxis Mcp gives AI agents real-time US storm intelligence. It connects MCP-compatible agents (Claude, GPT, etc.) to live NOAA storm data, scored contractor opportunities, property targeting lists, and canvass route optimization. It is purpose-built for roofing and restoration contractors.
How to use Stormaxis Mcp?
Sign up at stormaxis.io/partner for a Partner API key (requires Growth tier $199/mo or above). Then add the server to Claude Code using claude mcp add stormaxis --transport sse --url https://stormaxis.io/api/mcp/sse --header "X-API-Key: YOUR_API_KEY". Alternative setups include using mcp-remote with Claude Desktop or installing the stormaxis-mcp npm package as a stdio server.
Key features of Stormaxis Mcp
- Real-time US storm tracking from NOAA/NWS data
- Automatic storm opportunity scoring (0–100) based on severity, property values, roof age, and claim history
- Property targeting lists and H3-optimized canvass clusters
- Insurance claim propensity analytics by state
- Pre-built prompt templates:
storm_assessmentandproperty_search - Webhook subscriptions (Enterprise tier) for real-time alerts
Use cases of Stormaxis Mcp
- Daily sales briefing – get ranked storm opportunities and insurance propensity
- Field operations planning – identify top storms and generate optimized canvass zones and door-knock lists
- New market assessment – evaluate claim friendliness and historical flood risk before committing resources
FAQ from Stormaxis Mcp
What API key is required?
A Partner API key from stormaxis.io/partner. MCP access requires the Growth tier ($199/mo) or above.
What tools are available and what can they do?
Eight MCP tools: get_storm_overview, get_top_opportunities, get_storm_score, search_properties, get_canvass_clusters, get_insurance_propensity, get_fema_claims, and get_pipeline_status. Each returns specific storm, property, or analytics data. The Growth tier gives access to 5 of these; Professional unlocks all 8.
Where does the data come from and how often is it refreshed?
Data sources include NOAA/NWS Storm Data (continuous), SPC Convective Outlooks (every 15 minutes), MRMS (every 6 hours), US County Assessor Records (monthly), and FEMA NFIP claims (annual). Storm opportunity scores are recomputed every 6 hours.
What errors can I expect?
Common errors include missing or invalid API key, expired key, Sandbox tier restriction, daily call limit reached, invalid storm ID, and transient database unavailability (retry with exponential backoff).
How much does it cost?
Four tiers: Sandbox (free, 100 calls/day, no MCP), Growth ($199/mo, 5,000 calls/day, MCP access), Professional ($499/mo, 25,000 calls/day, all tools), Enterprise ($1,499+/mo, 100,000 calls/day, plus webhooks). Overage fees apply ($0.05–$0.08 per 1,000 calls).
Frequently asked questions
What API key is required?
A Partner API key from stormaxis.io/partner. MCP access requires the **Growth tier ($199/mo) or above**.
What tools are available and what can they do?
Eight MCP tools: `get_storm_overview`, `get_top_opportunities`, `get_storm_score`, `search_properties`, `get_canvass_clusters`, `get_insurance_propensity`, `get_fema_claims`, and `get_pipeline_status`. Each returns specific storm, property, or analytics data. The Growth tier gives access to 5 of these; Professional unlocks all 8.
Where does the data come from and how often is it refreshed?
Data sources include NOAA/NWS Storm Data (continuous), SPC Convective Outlooks (every 15 minutes), MRMS (every 6 hours), US County Assessor Records (monthly), and FEMA NFIP claims (annual). Storm opportunity scores are recomputed every 6 hours.
What errors can I expect?
Common errors include missing or invalid API key, expired key, Sandbox tier restriction, daily call limit reached, invalid storm ID, and transient database unavailability (retry with exponential backoff).
How much does it cost?
Four tiers: Sandbox (free, 100 calls/day, no MCP), Growth ($199/mo, 5,000 calls/day, MCP access), Professional ($499/mo, 25,000 calls/day, all tools), Enterprise ($1,499+/mo, 100,000 calls/day, plus webhooks). Overage fees apply ($0.05–$0.08 per 1,000 calls).
Basic information
More Other MCP servers
Inbox Zero AI
elie222The world's best AI personal assistant for email. Open source app to help you reach inbox zero fast.
MCP Toolbox for Databases
googleapisMCP Toolbox for Databases is an open source MCP server for databases.
Nginx UI
0xJackyYet another WebUI for Nginx

DeepMark
DeepMark helps teachers deliver rapid, consistent marking with meaningful feedback for every student — in a fraction of the time. What once took a week, now takes one free period.
Codelf
unbugA search tool helps dev to solve the naming things problem.
Comments