Back to Browse

Atlascast Truefixr MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

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

About

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

Remote endpoints: streamable-http: https://mcp.atlasunited.io/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

6 tools verified · Open access · No issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "io-github-truefixr-atlascast-truefixr": {
      "url": "https://mcp.atlasunited.io/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

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

#Productdataset=Price
1ML Storm Forecast by Addressrisk$0.05 per address
2Model-Based Weather by Addressweather$0.0002 per call
3Model-Based Hourly Forecast by Addressweather with hours_ahead (0 to 48)$0.0002 per call
4Storm History by Address: Reported and Radar-Detected Events Since 2003history$0.05 per event line, no minimum
5Past Storm Leads by Address: Reported and Radar-Detected, Last 365 Daysstorms$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

MethodBest for
REST APIPrepaid API key (top up from $1), Authorization: Bearer <key>
MCP serverClaude, ChatGPT and other MCP-compatible AI clients
x402Autonomous 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/data
POST https://data.truefixr.com/v1/data   (same params as a JSON body, keeps addresses out of URLs)
ParamDescription
datasetrisk, weather, history, storms, plus address, hazard_score, facilities, wildfire (county-level), at_risk, daily, coverage
state / county2-letter state code / county name
perilNarrow by peril, for example HAIL, FLASH_FLOOD, HEAVY_RAIN, TORNADO
windowrisk only: 24h, 48h, 3d, 5d, 7d, 10d
hours_aheadweather only: 0 to 48
addressesOmit for the price quote (HTTP 402). true for the paid pull (weather uses details=true)
limitMax records returned (limit=10 on a $0.05 dataset is a 50 cent sample)
formatjson or csv

Call the endpoint with no params for the live machine-readable menu. Full detail per dataset: Datasets.

Batch endpoints

EndpointMax locationsPrice
POST /v1/weather/batch500$0.0002 per location
POST /v1/portfolio/risk500$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:

  1. Request a paid pull, for example GET https://data.truefixr.com/v1/data?dataset=storms&county=Dallas&state=TX&addresses=true&limit=1.
  2. Receive HTTP 402 with the exact price.
  3. Sign a USDC payment on Base (eip155:8453) and retry with the payment header.
  4. 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_value is 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

Links

Reviews

No reviews yet

Be the first to review this server!