protogrid

Search / io.github.truefixr/atlascast-truefixr

TrueFixR Storm Data API

R0· no sign-in

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

v1.0.1 · active · repository · website · descriptor JSON · versions

An agent can connect right now, no human step.Remote endpoint, no authentication, reachable on the last probe.
Quality75good
Trust97of 100
Uptime, 30 days100%
Latency p50315 ms

Connect

8 clients · secrets stay placeholders
{
  "mcpServers": {
    "atlascast-truefixr": {
      "type": "http",
      "url": "https://mcp.atlasunited.io/mcp"
    }
  }
}
claude mcp add --transport http atlascast-truefixr https://mcp.atlasunited.io/mcp
[mcp_servers.atlascast-truefixr]
url = "https://mcp.atlasunited.io/mcp"
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "atlascast-truefixr": {
      "type": "remote",
      "url": "https://mcp.atlasunited.io/mcp",
      "enabled": true
    }
  }
}
{
  "mcpServers": {
    "atlascast-truefixr": {
      "type": "http",
      "url": "https://mcp.atlasunited.io/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=atlascast-truefixr&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vbWNwLmF0bGFzdW5pdGVkLmlvL21jcCJ9"
}
{
  "servers": {
    "atlascast-truefixr": {
      "type": "http",
      "url": "https://mcp.atlasunited.io/mcp"
    }
  }
}
{
  "mcpServers": {
    "atlascast-truefixr": {
      "httpUrl": "https://mcp.atlasunited.io/mcp"
    }
  }
}
extensions:
  "atlascast-truefixr":
    enabled: true
    name: "atlascast-truefixr"
    type: streamable_http
    uri: "https://mcp.atlasunited.io/mcp"
    timeout: 300

Quality 75 / 100good

protocol100 · weight 25
  • pass
    protocol.modernsupports 2026-07-28 (server/discover)
  • pass
    protocol.statelessanswers without a session
  • pass
    protocol.transportstreamable HTTP
  • pass
    protocol.list_ttltool list is cacheable (ttlMs 3600000)
authorizationn/a · weight 15
  • n/a
    auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
  • n/a
    auth.secret_in_urlno templated URL
tool hygiene79 · weight 30
  • pass
    tools.descriptionsevery tool has a description
  • warn
    tools.description_length1 tools have descriptions over 1,024 characters, which crowds the context
  • pass
    tools.schemasevery tool has an object input schema
  • pass
    tools.annotations6 of 6 tools declare readOnlyHint or destructiveHint
  • fail
    tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: get_weather_data (destructiveHint, idempotentHint); get_storm_history (destructiveHint, idempotentHint); get_property_storm_history_report (destructiveHint, idempotentHint); …
  • pass
    tools.token_costabout 3,376 tokens to load every tool
  • pass
    tools.api_dumptools are not a one-to-one API dump
stability25 · weight 15
  • warn
    stability.changes42 tool changes in 30 days
  • fail
    stability.rug_pull4 tools kept their name but changed most of their description in 30 days; review before trusting them
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

6 tools, about 3,376 tokens to load them all · tool set 9f4495266a70 · tools last changed 2026-10-09 · checked 2026-10-20 22:23 UTC

Tool changes

  • get_address_reportchangeddescription
    before

    Property Snapshot by Address: Past Storm Leads plus County Forecast Label. ONE property, 365-day snapshot within a tight radius (about 150 m) of the exact address: its own reported and radar-detected storm events (not the full archive), with the county's current forecast label as secondary context. Give an address with county+state, or lat/lon. For the full 2003-present record use get_property_storm_history_report (Storm History by Address); it searches a wider 5-mile radius by default, so counts will differ. For address-level 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).

    after · 82% of words in common

    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).

  • get_current_weatherchangeddescription
    before

    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. FREE by default: the lean response needs no account. details=true returns the full pull, billed $0.0002 per call (not per address). Add hours_ahead=0-48 for Model-Based Hourly Forecast by Address.

    after · 75% of words in common

    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).

  • get_property_storm_history_reportchangeddescription
    before

    Storm History by Address: Reported and Radar-Detected Events Since 2003. One property, 11 event categories (hail, wind, flood, lightning, tornado, hurricane, winter storm, extreme heat/cold, drought, wildfire, coastal), 2003 to present, in one citable report. Not the 365-day snapshot (use get_address_report for that). 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.

    after · 86% of words in common

    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.

  • get_risk_forecastchangeddescription
    before

    ML Storm Forecast by Address. FREE preview: counts of addresses in the forecast path of storms that could happen over the next 24 hours to 10 days, the storm types forecast and the estimated cost (the county's A-F grade is shown as a secondary label). 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. Per-peril machine-learning models, refreshed 4 times a day. Could happen, not will. 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).

    after · 81% of words in common

    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).

  • get_storm_historychangeddescription
    before

    Past Storm Leads by Address: Reported and Radar-Detected, Last 365 Days. FREE preview of storms already reported or radar-detected near addresses in a county over the last 365 days: event counts, storm types, measured severity ranges and repeat properties. Not a damage assessment. For the paid address-level pull, 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).

    after · 61% of words in common

    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).

  • get_weather_datachangeddescription
    before

    General-purpose query across every dataset: 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), plus address, hazard_score, facilities, wildfire (county-level), at_risk, daily, coverage. Free preview by default; address-level pulls need an account key or an x402 payment. Call with no arguments for the full menu. Dedicated tools: get_storm_history, get_risk_forecast, get_address_report, get_property_storm_history_report, get_current_weather. Use THIS tool for coverage, facilities, wildfire (county-level), at_risk, daily, a counties multi-county rollup (comma-separated, max 15), hazard_score, or any parameter combination the dedicated tools do not expose (radius_mi, date_of_loss, window, months, category, limit, kind, details, hours_ahead). 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. 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.

    after · 84% of words in common

    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.

  • get_address_reportchangeddescription
    before

    Property Snapshot by Address: Past Storm Leads plus County Forecast Label. ONE property, 365-day snapshot within a tight radius (about 150 m) of the exact address: its own reported and radar-detected storm events (not the full archive), with the county's current forecast label as secondary context. Give an address with county+state, or lat/lon. For the full 2003-present record use get_property_storm_history_report (Storm History by Address); it searches a wider 5-mile radius by default, so counts will differ. For address-level forecasts use get_risk_forecast (ML Storm Forecast by Address).

    after · 78% of words in common

    Property Snapshot by Address: Past Storm Leads plus County Forecast Label. ONE property, 365-day snapshot within a tight radius (about 150 m) of the exact address: its own reported and radar-detected storm events (not the full archive), with the county's current forecast label as secondary context. Give an address with county+state, or lat/lon. For the full 2003-present record use get_property_storm_history_report (Storm History by Address); it searches a wider 5-mile radius by default, so counts will differ. For address-level 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).

  • get_risk_forecastchangeddescription
    before

    ML Storm Forecast by Address. FREE preview: counts of addresses in the forecast path of storms that could happen over the next 24 hours to 10 days, the storm types forecast and the estimated cost (the county's A-F grade is shown as a secondary label). 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. Per-peril machine-learning models, refreshed 4 times a day. Could happen, not will.

    after · 82% of words in common

    ML Storm Forecast by Address. FREE preview: counts of addresses in the forecast path of storms that could happen over the next 24 hours to 10 days, the storm types forecast and the estimated cost (the county's A-F grade is shown as a secondary label). 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. Per-peril machine-learning models, refreshed 4 times a day. Could happen, not will. 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).

  • get_storm_historychangeddescription
    before

    Past Storm Leads by Address: Reported and Radar-Detected, Last 365 Days. FREE preview of storms already reported or radar-detected near addresses in a county over the last 365 days: event counts, storm types, measured severity ranges and repeat properties. Not a damage assessment.

    after · 62% of words in common

    Past Storm Leads by Address: Reported and Radar-Detected, Last 365 Days. FREE preview of storms already reported or radar-detected near addresses in a county over the last 365 days: event counts, storm types, measured severity ranges and repeat properties. Not a damage assessment. For the paid address-level pull, 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).

  • get_storm_historychangeddescription
    before

    Past Storm Leads by Address: Reported and Radar-Detected, Last 365 Days. FREE preview of storms already reported or radar-detected near addresses in a county over the last 365 days: event counts, storm types, measured severity ranges and repeat-hit properties. Not a damage assessment.

    after · 97% of words in common

    Past Storm Leads by Address: Reported and Radar-Detected, Last 365 Days. FREE preview of storms already reported or radar-detected near addresses in a county over the last 365 days: event counts, storm types, measured severity ranges and repeat properties. Not a damage assessment.

Showing the latest 10. Full history: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 97 / 100

provenance90
liveness100
freshness100
hygiene100

+repository +namespace-matches-repo +website +reachable +uptime-100% +updated-12d-ago

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://mcp.atlasunited.io/mcp streamable-httpnoneyes100%315 ms2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-052026-10-20

Tools (6)

get_address_reportread-onlyONE 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).
get_current_weatherread-onlyONE 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).
get_property_storm_history_reportread-onlyONE 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.
get_risk_forecastread-onlyCOUNTY 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).
get_storm_historyread-onlyCOUNTY 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).
get_weather_dataread-onlyCATCH-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.

Schemas: list_tools.

Similar MCP servers

Official server.json
{
  "name": "io.github.truefixr/atlascast-truefixr",
  "title": "TrueFixR Storm Data API",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://mcp.atlasunited.io/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "1.0.1",
  "repository": {
    "url": "https://github.com/truefixr/atlascast-truefixr",
    "source": "github"
  },
  "websiteUrl": "https://truefixr.com/api",
  "description": "Storm history by address since 2003, recent storm leads, model-based weather and storm forecasts."
}