TrueFixR Storm Data API
Overview
Description from the maker (original English)
Storm history by address since 2003, recent storm leads, model-based weather and storm forecasts.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi3 of 3 passedChecked from public information; code not scanned yet
- UsageiVery new★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Marketing & social media
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 3 of 3 passed
- Runs on the maker’s server: what you ask it goes through their server.
- Can do 6 things (tools) get_weather_data, get_storm_history, get_risk_forecast, get_property_storm_history_report …
- The registry lists no key to fill in.
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
- Open Settings → Connectors
- Press Add custom connector
- Paste the address below and press Add
- If it asks you to sign in, sign in with the maker
https://mcp.atlasunited.io/mcpRun this in your terminal
claude mcp add --transport http atlascast-truefixr https://mcp.atlasunited.io/mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"atlascast-truefixr": {
"url": "https://mcp.atlasunited.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"atlascast-truefixr": {
"type": "http",
"url": "https://mcp.atlasunited.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
- Open ChatGPT on the web → Settings → Connectors (Apps)
- Press Create or Add (some plans need Developer mode under Advanced first)
- Paste the address below, give it a name and save
- If it asks you to sign in, sign in with the maker
https://mcp.atlasunited.io/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Tool names and descriptions exactly as the server reported them on Nov 8, 2026. The maker wrote them, not us; we show them as plain text.
get_weather_dataCATCH-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, 200
get_storm_historyCOUNTY LEVEL, PAST 365 DAYS. Recent Storms by Address (last 365 days). Use when the question is how much storm activity a county has had in the past year. Without a key, returns the exact price quote (address count and price at $0.05/address) and a pay link; with a key it returns
get_risk_forecastCOUNTY LEVEL, FUTURE (next 24 hours to 10 days). AtlasCast Forecast by Address. Use when the question is which storms could affect a county soon. Without a key, returns the exact price quote (count of addresses in the forecast path and price at $0.05/address) and a pay link; with
get_property_storm_history_reportONE PROPERTY, 2003 TO PRESENT. Storm History by Address (back to 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,
get_current_weatherONE POINT, NOW TO 48 HOURS. 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 Hourly Weat
get_address_reportONE PROPERTY, PAST 365 DAYS. Property Snapshot by Address: Recent Storms 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 secon
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account truefixr, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- ✓ Pass
Endpoint responds
Responded in 881 ms (HTTP 200)
- – Not applicable
Sign-in with OAuth
No sign-in needed
- ✓ Pass
No hidden instructions in tool descriptions
Read 6 tool descriptions and found no hidden instructions to the AI
Compared with others in Marketing & social mediai
- More stars than 0% of the other 3632 servers in this category
- Published to the registry more recently than 49% of the other 3632 servers in this category
- Basic checks equal to or better than 100% of the other 3632 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is TrueFixR Storm Data API safe?
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed –, and the latest version (1.0.1) reached the registry 31 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
What can I use instead?
In the same category: MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Google Analytics MCP
GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.
BibiGPT YouTube Video Summarizer
AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Atlas United storm data API: ML forecasts and storm history for every U.S. address
Atlas United builds risk models for every U.S. address (latitude/longitude), with all the information inside each location. This repository documents the API: address-level storm forecasts for the next 24 hours to 10 days, plus every reported storm at that address back to 2003. Pay per address, no contract.
AtlasCast is Atlas United's forecasting model suite: probabilistic, address-level forecasts for 10 perils, refreshed 4 times a day. TrueFixR is the storm-data side: reported and radar-detected storm history by address. Not affiliated with NOAA or the NWS.
The five products
| # | Product | dataset= | Price |
|---|---|---|---|
| 1 | ML Storm Forecast by Address | risk | $0.05 per address |
| 2 | Model-Based Weather by Address | weather | $0.0002 per call |
| 3 | Model-Based Hourly Forecast by Address | weather with hours_ahead (0 to 48) | $0.0002 per call |
| 4 | Storm History by Address: Reported and Radar-Detected Events Since 2003 | history | $0.05 per event line, no minimum |
| 5 | Past Storm Leads by Address: Reported and Radar-Detected, Last 365 Days | storms | $0.05 per address |
Products 1 to 3 are model outputs. Products 4 and 5 are recorded events matched to addresses.
1. ML Storm Forecast by Address
Probabilistic, address-level forecasts for 10 perils (tornado, hail, wind, flash flood, heavy rain, winter, ice, coastal surge, hurricane and wildfire), 24 hours to 10 days ahead, refreshed 4 times a day. AtlasCast uses a separate machine-learning model for each peril. Models are trained and validated chronologically on held-out reported events, and inputs are restricted to information available at forecast issue time.
Each address record carries the structure replacement value and the estimated people at that address, plus storm type, forecast time, a risk label and a past-hit count. Replacement value is the cost to rebuild the structure, not market value. Windows: 24h, 48h, 3d, 5d, 7d, 10d. Filter by county, peril and window. Without payment you get the address count and exact price first; county grade and per-peril totals are a County Summary ($0.02 per county). Forecasts describe what could happen, not what will happen.
2. Model-Based Weather by Address
Point weather for any U.S. coordinate: current conditions, active severe weather alerts and a short-term rain outlook. $0.0002 per call. Add details=true for the full pull of over 170 variables at $0.0002 per call.
3. Model-Based Hourly Forecast by Address
Add hours_ahead (0 to 48) to the weather dataset for forecast hours instead of current conditions. The response reports the hour actually used in forecast_hour_used. Forecast hours carry a smaller core set of fields. $0.0002 per call.
4. Storm History by Address: Reported and Radar-Detected Events Since 2003
One property's long record: every storm event reported or radar-detected within a chosen radius, 2003 to the present, across 11 categories (hail, wind, flood, lightning, tornado, hurricane, winter storm, extreme heat and cold, drought, wildfire, coastal). Each line has event date, type, magnitude where measured, distance in miles and county. Citable, with a reference_id. An optional date_of_loss mode shows whether an event was reported or radar-detected near the address on a date, and lists events before and after it. A record of reported and radar-detected events, not a damage assessment.
5. Past Storm Leads by Address: Reported and Radar-Detected, Last 365 Days
Address-level records of storm events reported or radar-detected at or near each address over the trailing 365 days, filterable by county, peril and severity. Each record has the event time (UTC), type, measured or radar-estimated severity with its unit, distance and a repeat-hit count. Without payment you get the address count and exact price first. Not a damage assessment.
Access
| Method | Best for |
|---|---|
| REST API | Prepaid API key (top up from $1), Authorization: Bearer |
| MCP server | Claude, ChatGPT and other MCP-compatible AI clients |
| x402 | Autonomous AI agents: pay per request in USDC on Base, no account |
Same prices either way. Every request without payment returns the exact price first (HTTP 402 quote with the count, the price and a card pay link). Every paid response carries a reference_id receipt, and an identical paid query within 24 hours is not billed twice.
Endpoint
GET https://data.truefixr.com/v1/dataPOST https://data.truefixr.com/v1/data (same params as a JSON body, keeps addresses out of URLs)
| Param | Description |
|---|---|
dataset | risk, weather, history, storms, plus address, hazard_score, facilities, wildfire (county-level), at_risk, daily, coverage |
state / county | 2-letter state code / county name |
peril | Narrow by peril, for example HAIL, FLASH_FLOOD, HEAVY_RAIN, TORNADO |
window | risk only: 24h, 48h, 3d, 5d, 7d, 10d |
hours_ahead | weather only: 0 to 48 |
addresses | Omit for the price quote (HTTP 402). true for the paid pull (weather uses details=true) |
limit | Max records returned (limit=10 on a $0.05 dataset is a 50 cent sample) |
format | json or csv |
Call the endpoint with no params for the live machine-readable menu. Full detail per dataset: Datasets.
Batch endpoints
| Endpoint | Max locations | Price |
|---|---|---|
POST /v1/weather/batch | 500 | $0.0002 per location |
POST /v1/portfolio/risk | 500 | $0.05 per location (county forecast status, not address-level) |
For AI agents
An agent with no API key and no human in the loop can pay per call with x402:
- Request a paid pull, for example
GET https://data.truefixr.com/v1/data?dataset=storms&county=Dallas&state=TX&addresses=true&limit=1. - Receive HTTP 402 with the exact price.
- Sign a USDC payment on Base (
eip155:8453) and retry with the payment header. - Receive the data. No signup, no key.
Manifest: /.well-known/x402.json. Agent docs: llms.txt.
Data honesty
- Forecasts describe what could happen, not what will happen.
- A storm reported or radar-detected near an address is not a property inspection, damage assessment or repair estimate.
structure_valueis replacement cost (what it costs to rebuild), not market value.- Not affiliated with NOAA or the NWS.
Who this is for
Insurers, adjusters, emergency management, property managers, restoration, solar, and data and AI-agent builders.
Documentation
- Datasets: every dataset, price and example
- Sample data: trimmed real responses
- Who this is for: use cases by audience
- What you get: the two views of every address, and data honesty
- Comparison
- Code examples: curl, Python, JavaScript, x402 and MCP
- Industry evidence
Links
- API docs and signup: https://atlasunited.io/api
- MCP server: https://mcp.atlasunited.io/mcp
- Company: https://truefixr.com