Skip to content

TrueFixR Storm Data API MCP server

io.github.truefixr/atlascast-truefixrtruefixrstreamable-httpv1.0.1Scanned

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

7 tools: 7 only read.

Tools: 0 delete, 0 irreversible, 0 write, 7 read.
  • Reads private data · 0
  • Reads text others write · 7
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the TrueFixR Storm Data API MCP server can do

The TrueFixR Storm Data API MCP server is published by the GitHub account truefixr. It has 7 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

7 tools bring in text other people can write (get_weather_data, get_storm_history, get_risk_forecast and 4 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 20, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Only reads 7Show 7 read-only tools
  • get_address_reportONE PROPERTY, PAST 365 DAYS.Reads text others writeNo findings

    Why it is in this group

    • The name "get_address_report" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    ONE 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 secondary context. Input is an address with county and state, or lat/lon. Without a key, returns the exact price quote ($0.05) and a pay link; with a key it returns the data. 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, AtlasCast Forecast by Address). For paid single-address data, call get_weather_data with dataset=address and addresses=true ($0.05 flat per address; pay with an Atlas United API key, x402, or the card pay link).

    Annotations the server declares

    • title: Property Snapshot by Address (365-day recent storms plus county forecast label)
    • readOnlyHint: true
    • openWorldHint: true
  • get_current_weatherONE POINT, NOW AND ABOUT THE NEXT TWO DAYS.Reads text others writeNo findings

    Why it is in this group

    • The name "get_current_weather" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    ONE POINT, NOW AND ABOUT THE NEXT TWO DAYS. 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 a forecast hour. Not for storm history or storm-risk forecasts (use get_address_report, get_property_storm_history_report, get_storm_history or get_risk_forecast). Without a key, returns the exact price quote ($0.0002) and a pay link; with a key (or x402 payment) it returns the weather data, billed $0.0002 per call (not per address).

    Annotations the server declares

    • title: Weather by Address (now, and about the next two days)
    • readOnlyHint: true
    • openWorldHint: true
  • get_paid_orderAfter the user pays a card checkout link (pay_with_card), Stripe shows a receipt page whose link contains /v1/orders/ and session_id=.Reads text others writeNo findings

    Why it is in this group

    • The name "get_paid_order" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    After the user pays a card checkout link (pay_with_card), Stripe shows a receipt page whose link contains /v1/orders/ and session_id=. Pass that full link as order_url to get the paid records. Results stay available for 24 hours after payment. Leftover credit can be turned into a reusable API key via the claim_key_url in the result.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • title: Fetch a paid card order
  • get_property_storm_history_reportONE PROPERTY, 2003 TO PRESENT.Reads text others writeNo findings

    Why it is in this group

    • The name "get_property_storm_history_report" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    ONE 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, 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). Without a key, returns the exact price quote (report-line count and price) and a pay link; with a key (or x402 payment) it returns the data. Paid report: $0.05 per line; without an API key, reports start at 10 lines ($0.50). 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.

    Annotations the server declares

    • title: Storm History by Address (back to 2003)
    • readOnlyHint: true
    • openWorldHint: true
  • get_risk_forecastCOUNTY LEVEL, FUTURE (next 24 hours to 10 days).Reads text others writeNo findings

    Why it is in this group

    • The name "get_risk_forecast" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    COUNTY 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 a key it returns the data. County grade and counts by storm type are a paid County Summary (summary=true, $0.02 per county). Input is state plus county. 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 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 (pay with an Atlas United API key, x402, or the card pay link).

    Annotations the server declares

    • title: AtlasCast Forecast by Address
    • readOnlyHint: true
    • openWorldHint: true
  • get_storm_historyCOUNTY LEVEL, PAST 365 DAYS.Reads text others writeNo findings

    Why it is in this group

    • The name "get_storm_history" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    COUNTY 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 the data. County grade and counts by storm type are a paid County Summary (summary=true, $0.02 per county). 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; pay with an Atlas United API key, x402, or the card pay link).

    Annotations the server declares

    • title: Recent Storms by Address (last 365 days)
    • readOnlyHint: true
    • openWorldHint: true
  • get_weather_dataThe full API in one tool.Reads text others writeNo findings

    Why it is in this group

    • The name "get_weather_data" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    The full API in one tool. The other tools cover the common questions (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 and about the next two days). Use THIS tool for: every PAID address-level pull (set addresses=true), county coverage ($0.0002), facilities, wildfire (county-level), at_risk, daily, a counties multi-county rollup (comma-separated, max 15), hazard_score ($0.50), or any parameter the dedicated tools do not expose (radius_mi, date_of_loss, window, months, category, limit, kind, details, hours_ahead). Datasets: AtlasCast Forecast by Address (risk), Weather by Address (weather), Weather Forecast by Address (weather with hours_ahead), Storm History by Address (back to 2003) (history), Recent Storms by Address (last 365 days) (storms). Without a key, the tool returns the exact price quote (count + price) and a card pay link; with a key (new keys from $5, top-ups from $1, at https://atlasunited.io/api) or an x402 payment, it returns the data. Call with no arguments for the free full menu. License: own use only; no resale, redistribution or AI training.

    Annotations the server declares

    • title: Atlas United data, all datasets (advanced / multi-county)
    • readOnlyHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write7
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:12 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 added, 6 changed.+1 added~6 changedView diff
  2. Tools6 changed.~6 changedView diff

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http atlascast-truefixr https://mcp.atlasunited.io/mcp
claude mcp add --transport http atlascast-truefixr https://mcp.atlasunited.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__atlascast-truefixr__get_weather_data",
      "mcp__atlascast-truefixr__get_storm_history",
      "mcp__atlascast-truefixr__get_risk_forecast",
      "mcp__atlascast-truefixr__get_property_storm_history_report",
      "mcp__atlascast-truefixr__get_current_weather",
      "mcp__atlascast-truefixr__get_address_report",
      "mcp__atlascast-truefixr__get_paid_order"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as atlascast-truefixr. Review it before you use it.

Capability tags behind 7 rules
  • mcp__atlascast-truefixr__get_weather_data untrusted-input
  • mcp__atlascast-truefixr__get_storm_history untrusted-input
  • mcp__atlascast-truefixr__get_risk_forecast untrusted-input
  • mcp__atlascast-truefixr__get_property_storm_history_report untrusted-input
  • mcp__atlascast-truefixr__get_current_weather untrusted-input
  • mcp__atlascast-truefixr__get_address_report untrusted-input
  • mcp__atlascast-truefixr__get_paid_order untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.truefixr/atlascast-truefixr/verify?hash=8f6abb0672b7259e13b6d8ccfe8dfde91903ab012ae144e430608bb034df65d0" | jq -e '.changed == false'

Pinned hash 8f6abb0672b7, from Nov 20, 2026, 16:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.truefixr/atlascast-truefixr/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.truefixr/atlascast-truefixr
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.truefixr/atlascast-truefixr.svg)](https://radar.anlyon.com/servers/io.github.truefixr/atlascast-truefixr)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:50 UTC.

TrueFixR Storm Data API MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the TrueFixR Storm Data API MCP server safe?

No scan can promise that. What its definitions show: 7 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the TrueFixR Storm Data API MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the TrueFixR Storm Data API MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the TrueFixR Storm Data API MCP server have?

7 tools: 7 read. get_weather_data, get_storm_history, get_risk_forecast, get_property_storm_history_report, get_current_weather, get_address_report and get_paid_order.

Does the TrueFixR Storm Data API MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the TrueFixR Storm Data API MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the TrueFixR Storm Data API MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.