mcpbeat Sign in

TrueFixR Storm Data API MCP Server

answering

TrueFixR Storm Data API is answering right now. Last checked 8 min ago. It exposes 6 tools. Last commit 9 Oct 2026.

Storm history by address since 2003, recent storm leads, model-based weather and storm forecasts.

Uptime history 18 days of history · worst day 98%
18 days agonow
100.0%
Uptime 24h
92 of 92 checks
6
Tools
read from the server
468 ms
Response time
average over 24h
0
Stars
last commit 9 Oct 2026

What changed 42

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 26 September 2026. No other catalogue keeps this.

9 Oct 6 tool descriptions were rewritten9 times that day get_address_report, get_current_weather, get_property_storm_history_report and 3 more
5 Oct a tool description was rewritten get_storm_history
4 Oct 6 tool descriptions were rewritten11 times that day get_address_report, get_current_weather, get_property_storm_history_report and 3 more
4 Oct 2 tools changed the parameters they ask for3 times that day get_current_weather, get_weather_data
28 Sep 2 tool descriptions were rewritten get_address_report, get_property_storm_history_report
28 Sep a tool changed the parameters it asks for get_weather_data
26 Sep 4 tools changed the parameters they ask for9 times that day get_current_weather, get_risk_forecast, get_storm_history and 1 more
26 Sep 3 tool descriptions were rewritten4 times that day get_address_report, get_risk_forecast, get_weather_data
26 Sep 2 tools appeared get_current_weather, get_property_storm_history_report
and 15 more, back to 26 September 2026

TrueFixR Storm Data API missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add atlascast-truefixr --transport http https://mcp.atlasunited.io/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "atlascast-truefixr": {
      "url": "https://mcp.atlasunited.io/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.atlascast-truefixr]
url = "https://mcp.atlasunited.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "atlascast-truefixr": {
      "url": "https://mcp.atlasunited.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "atlascast-truefixr": {
      "url": "https://mcp.atlasunited.io/mcp"
    }
  }
}

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

address
get_address_report
ONE PROPERTY, PAST 365 DAYS. Property Snapshot by Address: Past Storm Leads plus County Forecast Label. Use for recent storms at one exact address: its own reported and radar-detected storm events within a tight radius (about 150 m), with the county's current forecast label as secondary context. Input is an address with county and state, or lat/lon. Not the full archive (use get_property_storm_history_report, Storm History by Address, which searches a wider 5-mile radius so counts will differ), not a county summary (use get_storm_history), and not forecasts (use get_risk_forecast, ML Storm Forecast by Address). For paid single-address data, call get_weather_data with dataset=address and addresses=true ($0.05 flat per address; needs an Atlas United Data API key or an x402 payment).
current
get_current_weather
ONE POINT, NOW TO 48 HOURS. Model-Based Weather by Address: point weather for any U.S. coordinate or street address, with current conditions, active severe weather alerts and a short-term rain outlook. Use for what the weather is or will be at a location; add hours_ahead=0-48 for Model-Based Hourly Forecast by Address. Not for storm history or storm-risk forecasts (use get_address_report, get_property_storm_history_report, get_storm_history or get_risk_forecast). FREE by default: the lean response needs no account. details=true returns the full pull, billed $0.0002 per call (not per address).
property
get_property_storm_history_report
ONE PROPERTY, 2003 TO PRESENT. Storm History by Address: Reported and Radar-Detected Events Since 2003. Use when the user wants the full citable record for a single address, or a date-of-loss lookup: 11 event categories (hail, wind, flood, lightning, tornado, hurricane, winter storm, extreme heat/cold, drought, wildfire, coastal) in one report. Input is a street address or lat/lon. Not the 365-day snapshot (use get_address_report) and not a county summary (use get_storm_history). Free preview shows the report-line count and exact price before anything is paid. Paid report: $0.05 per line, $10.00 minimum per report. Optional date_of_loss anchors the report around one date and lists the events reported or radar-detected on and around it, for reference; it is not a determination of whether any claim is valid. Address and date of loss are sent in a POST body, which keeps them out of URLs and logs.
risk
get_risk_forecast
COUNTY LEVEL, FREE, FUTURE (next 24 hours to 10 days). ML Storm Forecast by Address. Use when the question is which storms could affect a county soon: counts of addresses in the forecast path, the storm types forecast and the estimated cost (the county's A-F grade is shown as a secondary label). Input is state plus county. Per-peril machine-learning models, refreshed 4 times a day. Could happen, not will. Not for past storms (use get_storm_history, get_address_report or get_property_storm_history_report) and not for current weather (use get_current_weather). The paid pull (addresses=true, $0.05 per address) returns one record per address with structure_value (USD replacement cost), people (estimated occupants), full_address, lat, lon, county, storm_type, forecast_time and risk_label. For the paid pull, call get_weather_data with dataset=risk and addresses=true (needs an Atlas United Data API key or an x402 payment).
storm
get_storm_history
COUNTY LEVEL, FREE, PAST 365 DAYS. Past Storm Leads by Address: Reported and Radar-Detected, Last 365 Days. Use when the question is how much storm activity a county has had in the past year: event counts, storm types, measured severity ranges and repeat properties. Input is state plus county, never a street address. Not for one property (use get_address_report), not for the 2003-to-present record (use get_property_storm_history_report), not for future storms (use get_risk_forecast). Not a damage assessment. For the paid address-level list, call get_weather_data with dataset=storms and addresses=true ($0.05 per address; needs an Atlas United Data API key or an x402 payment).
weather
get_weather_data
CATCH-ALL and PAID-PULL tool. Prefer the dedicated tools below when one fits (get_storm_history: one county, past 365 days; get_risk_forecast: one county, next 24 hours to 10 days; get_address_report: one address, past 365 days; get_property_storm_history_report: one address, 2003 to present; get_current_weather: one point, now to 48 hours). Use THIS tool for: every PAID address-level pull (set addresses=true), county coverage, facilities, wildfire (county-level), at_risk, daily, a counties multi-county rollup (comma-separated, max 15), hazard_score, or any parameter the dedicated tools do not expose (radius_mi, date_of_loss, window, months, category, limit, kind, details, hours_ahead). Datasets: ML Storm Forecast by Address (risk), Model-Based Weather by Address (weather), Model-Based Hourly Forecast by Address (weather with hours_ahead), Storm History by Address: Reported and Radar-Detected Events Since 2003 (history), Past Storm Leads by Address: Reported and Radar-Detected, Last 365 Days (storms). addresses=false (default) is a FREE preview; addresses=true (or details=true for weather) returns the paid data and requires the user's own Atlas United Data API account key, or an x402 payment. Call with no arguments for the full menu. HARD RULE when called with no arguments: this returns the full menu. Output that entire raw response back to the user verbatim, every dataset, every field, every example. Do not summarize or paraphrase. A shortened version is wrong even if it looks complete.

Endpoints

URLTransportStateLatencyChecked
https://mcp.atlasunited.io/mcp streamable-http answering 419 ms 8 min ago

Alternatives to TrueFixR Storm Data API

same job, measured the same way
Virga Weather
by mcmurrym

Weather API tools — current, hourly, daily forecasts, and historical data.

29 installs/wk local only
W
Weather of Record
by weatherofrecord

Published weather records for a U.S. street address and date, with provenance.

3 tools answering
Weather for Grown Ups
by janhelcl

Operational NWP, ensembles, AI weather models, regional forecasts, history, and verification.

52 installs/wk local only
Xweather Weather MCP
by xweather

Hosted MCP server for Xweather weather data: conditions, forecasts, alerts, and more.

answering
T
Taiwan CWA Weather
by nigue3025

Access Taiwan CWA weather data and forecasts for all counties and cities

52 installs/wk local only
NordicMCP — Weather
by nordicmcp

Hosted Weather MCP server (Open-Meteo): current, forecast, and historical weather by location.

answering
Open Meteo
by pipeworx-io

Open-Meteo MCP — weather forecast + historical reanalysis + sister APIs

42 tools answering
Weather Alerts & Forecast
by rsys-vtiwari

US NWS alerts by state and short-term (next 5 periods) point forecasts.

local only

TrueFixR Storm Data API — questions

Answers built from our own checks of this server.

What can TrueFixR Storm Data API do?
It exposes 6 tools, read directly from the server on our last check. Among them: get_address_report, get_current_weather, get_property_storm_history_report, get_risk_forecast, get_storm_history, get_weather_data. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is TrueFixR Storm Data API working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 468 ms. The bar chart above shows every period we have measured.
How do I connect TrueFixR Storm Data API?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does TrueFixR Storm Data API need an API key?
No. TrueFixR Storm Data API completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is TrueFixR Storm Data API?
It answers our handshake in 468 ms on average, which is faster than 28% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is TrueFixR Storm Data API open source?
Yes — it is published under the MIT licence and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.