Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

TrueFixR Storm Data API

REMOTE · MCP.ATLASUNITED.IO

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

0 this week 82 Trust /100

Last scanned (15 hours ago)

Scores higher than 81% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability57
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 4033 tokens (~576/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_current_weather” rewrote its description, which is the text the model reads security
    • Tool “get_weather_data” rewrote its description, which is the text the model reads security
    • “get_risk_forecast” reworded the description of “peril” cosmetic
    • “get_storm_history” reworded the description of “peril” cosmetic
    • “get_weather_data” reworded the description of “hours_ahead” cosmetic
    • “get_weather_data” reworded the description of “peril” cosmetic
    • “get_weather_data” reworded the description of “window” cosmetic
    • Tool “get_current_weather” changed its title: Weather by Address (hourly forecast with hours_ahead) → Weather by Address (now, and about the next two days) cosmetic
    • Tool “get_storm_history” changed its title: Recent Storms by Address (county quote) → Recent Storms by Address (last 365 days) cosmetic
  • 14 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_property_storm_history_report” rewrote its description, which is the text the model reads security
    • Tool “get_weather_data” rewrote its description, which is the text the model reads security
    • Schema quality: 3170 → 4025 ▼ functional
    • Server version: 2.5.1 → 2.7.0 functional
    • New tool “get_paid_order” functional
    • “get_address_report” added an optional parameter “api_key” cosmetic
    • “get_address_report” added an optional parameter “sandbox” cosmetic
    • “get_address_report” added an optional parameter “x_payment” cosmetic
    • “get_current_weather” added an optional parameter “api_key” cosmetic
    • “get_current_weather” added an optional parameter “sandbox” cosmetic
    • “get_property_storm_history_report” added an optional parameter “api_key” cosmetic
    • “get_property_storm_history_report” added an optional parameter “end” cosmetic
    • “get_property_storm_history_report” added an optional parameter “sandbox” cosmetic
    • “get_property_storm_history_report” added an optional parameter “start” cosmetic
    • “get_risk_forecast” added an optional parameter “api_key” cosmetic
    • “get_risk_forecast” added an optional parameter “sandbox” cosmetic
    • “get_risk_forecast” added an optional parameter “summary” cosmetic
    • “get_risk_forecast” added an optional parameter “x_payment” cosmetic
    • “get_storm_history” added an optional parameter “api_key” cosmetic
    • “get_storm_history” added an optional parameter “sandbox” cosmetic
    • “get_storm_history” added an optional parameter “summary” cosmetic
    • “get_storm_history” added an optional parameter “x_payment” cosmetic
    • “get_weather_data” added an optional parameter “api_key” cosmetic
    • “get_weather_data” added an optional parameter “end” cosmetic
    • “get_weather_data” added an optional parameter “sandbox” cosmetic
    • “get_weather_data” added an optional parameter “start” cosmetic
    • “get_weather_data” added an optional parameter “summary” cosmetic
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
    • “get_weather_data” reworded the description of “dataset” cosmetic
  • 8 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_address_report” rewrote its description, which is the text the model reads security
    • Tool “get_current_weather” rewrote its description, which is the text the model reads security
    • Tool “get_property_storm_history_report” rewrote its description, which is the text the model reads security
    • Tool “get_risk_forecast” rewrote its description, which is the text the model reads security
    • Tool “get_storm_history” rewrote its description, which is the text the model reads security
    • Tool “get_weather_data” rewrote its description, which is the text the model reads security
    • “get_weather_data” reworded the description of “details” cosmetic
    • “get_weather_data” reworded the description of “hours_ahead” cosmetic
    • Tool “get_address_report” changed its title: Property Snapshot by Address (365-day past storm leads plus county forecast label) → Property Snapshot by Address (365-day recent storms plus county forecast label) cosmetic
    • Tool “get_current_weather” changed its title: Model-Based Weather by Address (hourly forecast with hours_ahead) → Weather by Address (hourly forecast with hours_ahead) cosmetic
    • Tool “get_property_storm_history_report” changed its title: Storm History by Address: Reported and Radar-Detected Events Since 2003 → Storm History by Address (back to 2003) cosmetic
    • Tool “get_risk_forecast” changed its title: ML Storm Forecast by Address → AtlasCast Forecast by Address cosmetic
    • Tool “get_storm_history” changed its title: Past Storm Leads by Address (county quote) → Recent Storms by Address (county quote) cosmetic
  • 7 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.atlasunited.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.atlasunited.io CN=YE1,O=Let's Encrypt,C=US 23 Sept 2026 22 Dec 2026 ECDSA 256 ECDSA-SHA384 5bd7aa7b507b74f89d945ed2850f21d0e9e
SANs: mcp.atlasunited.io
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.atlasunited.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
atlasunited.io. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.atlasunited.io/mcp Verified 200
http (plaintext) http://mcp.atlasunited.io/mcp HTTPS enforced 308 https://mcp.atlasunited.io/mcp
MCP tools · 7 exposed · ~3,740 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_address_report ~391

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

NameTypeReqDescription
addressstring–Street address.
api_keystring–Optional. The user's Atlas United API key (tfx_live_...), if they share it in chat. Otherwise leave empty.
countystring–County name without the word 'County', e.g. Dallas.
latnumber–Latitude.
lonnumber–Longitude.
sandboxboolean–true = free real data (up to 10 records) at the sandbox place only: 1100 Congress Ave, Austin, TX 78701 (lat 30.2747, lon -97.7404) or Travis County, TX. Elsewhere it has no effect.
statestring–2-letter US state code, e.g. TX.
x_paymentstring–Optional signed x402 payment payload, used instead of an API key.

No output schema declared.

No examples provided.

get_current_weather ~397

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

NameTypeReqDescription
addressstring–Street address. Server-side geocoding, no separate geocoding step needed.
api_keystring–Optional. The user's Atlas United API key (tfx_live_...), if they share it in chat. Otherwise leave empty.
detailsboolean–true = full pull ($0.0002/call). Requires an API key or x402 payment; without a key, returns a price quote and pay link.
hours_aheadinteger–Forecast 0-48h out instead of current conditions; snaps to the nearest available forecast hour, and forecast_hour_used says what you got.
latnumber–Latitude, alternative to address.
lonnumber–Longitude, alternative to address.
sandboxboolean–true = free real data (up to 10 records) at the sandbox place only: 1100 Congress Ave, Austin, TX 78701 (lat 30.2747, lon -97.7404) or Travis County, TX. Elsewhere it has no effect.
x_paymentstring–Optional signed x402 payment payload, used instead of an API key.

No output schema declared.

No examples provided.

get_paid_order ~124

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.

NameTypeReqDescription
order_urlstringyesThe receipt page link shown after paying the card checkout, e.g. https://data.truefixr.com/v1/orders/ord_.../?session_id=cs_...

No output schema declared.

No examples provided.

get_property_storm_history_report ~535

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.

NameTypeReqDescription
addressstring–Street address. Server-side geocoding, no separate geocoding step needed.
addressesboolean–false = price quote (line count + price) and pay link. true = the full report ($0.05/line, no minimum; requires an Atlas United Data API key or an x402 payment).
api_keystring–Optional. The user's Atlas United API key (tfx_live_...), if they share it in chat. Otherwise leave empty.
date_of_lossstring–Optional, YYYY-MM-DD. Anchors the report around this date.
endstring–Optional, YYYY-MM-DD. End of the date range.
latnumber–Latitude, alternative to address.
lonnumber–Longitude, alternative to address.
radius_minumber–Search radius in miles. Default 5, max 25.
sandboxboolean–true = free real data (up to 10 records) at the sandbox place only: 1100 Congress Ave, Austin, TX 78701 (lat 30.2747, lon -97.7404) or Travis County, TX. Elsewhere it has no effect.
startstring–Optional, YYYY-MM-DD. Start of the date range.
x_paymentstring–Optional signed x402 payment payload, used instead of an API key.

No output schema declared.

No examples provided.

get_risk_forecast ~458

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

NameTypeReqDescription
api_keystring–Optional. The user's Atlas United API key (tfx_live_...), if they share it in chat. Otherwise leave empty.
countystringyesCounty name without the word 'County', e.g. Dallas.
perilstring–Narrows the forecast to one storm type (e.g. HAIL, WIND, TORNADO, FLASH_FLOOD).
sandboxboolean–true = free real data (up to 10 records) at the sandbox place only: 1100 Congress Ave, Austin, TX 78701 (lat 30.2747, lon -97.7404) or Travis County, TX. Elsewhere it has no effect.
statestringyes2-letter US state code, e.g. TX.
summaryboolean–true = County Summary: county grade and counts by storm type ($0.02 per county).
windowstring–Forecast window. Default 24h.
x_paymentstring–Optional signed x402 payment payload, used instead of an API key.

No output schema declared.

No examples provided.

get_storm_history ~545

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

NameTypeReqDescription
api_keystring–Optional. The user's Atlas United API key (tfx_live_...), if they share it in chat. Otherwise leave empty.
countystringyesCounty name without the word 'County', e.g. Dallas.
daysinteger–Look-back window in days (up to 365).
min_severitynumber–Minimum severity, e.g. 1.75 for golf-ball hail.
perilstring–Storm/risk type filter. Used by dataset=storms and dataset=risk (narrows to one storm type) and by dataset=at_risk (narrows to one peril bucket). Common storms values: HAIL, THUNDERSTORM_WIND, FLASH_…
sandboxboolean–true = free real data (up to 10 records) at the sandbox place only: 1100 Congress Ave, Austin, TX 78701 (lat 30.2747, lon -97.7404) or Travis County, TX. Elsewhere it has no effect.
statestringyes2-letter US state code, e.g. TX.
summaryboolean–true = County Summary: county grade and counts by storm type ($0.02 per county).
x_paymentstring–Optional signed x402 payment payload, used instead of an API key.

No output schema declared.

No examples provided.

get_weather_data ~1,290

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.

NameTypeReqDescription
addressstring–Street address, for dataset=address.
addressesboolean–Without a key, returns the exact price quote (count and price) and a pay link. With a key or x402 payment, true = address-level records ($0.05/record).
api_keystring–Optional. The user's Atlas United API key (tfx_live_...), if they share it in chat. Otherwise leave empty.
categorystring–dataset=facilities only. Facility category filter.
countiesstring–Comma-separated county names (max 15) plus state, for a multi-county rollup.
countystring–County name without the word 'County', e.g. Dallas.
datasetstring–Target dataset. Default storms. One-peril products: <peril>_forecast (county+state+window, $0.05/address), <peril>_leads (county+state, last 365 days, $0.05/address), <peril>_history (address or lat+…
date_of_lossstring–dataset=history only. YYYY-MM-DD. Anchors the report around this date, returning the weather events recorded on and immediately around that date, for reference. Not a determination of whether any cla…
daysinteger–Look-back window in days where supported.
detailsboolean–dataset=weather only (Weather by Address). Billed $0.0002/call with a key or x402 payment; without a key, returns a price quote and pay link.
endstring–dataset=history only. YYYY-MM-DD end of the date range.
formatstring–Response format. json (default) or csv.
hours_aheadinteger–dataset=weather only (a forecast hour). Forecast 0-48h out instead of current conditions; snaps to the nearest available forecast hour, and forecast_hour_used says what you got.
kindstring–dataset=at_risk only. Narrows to 'schools' or 'businesses'.
latnumber–Latitude in decimal degrees.
limitinteger–Max records on the paid pull (default 2000, per-dataset caps still apply, e.g. storms caps at 5000).
lonnumber–Longitude in decimal degrees.
max_severitynumber–Maximum measured severity.
min_severitynumber–Minimum measured severity (e.g. 1.5 = 1.5 inch hail).
monthsinteger–dataset=storms only. Returns month-bucketed history totals instead of individual leads, for the last N months.
perilstring–Storm/risk type filter. Used by dataset=storms and dataset=risk (narrows to one storm type) and by dataset=at_risk (narrows to one peril bucket). Common storms values: HAIL, THUNDERSTORM_WIND, FLASH_…
radius_minumber–dataset=history only. Search radius in miles. Default 5, max 25.
sandboxboolean–true = free real data (up to 10 records) at the sandbox place only: 1100 Congress Ave, Austin, TX 78701 (lat 30.2747, lon -97.7404) or Travis County, TX. Elsewhere it has no effect.
startstring–dataset=history only. YYYY-MM-DD start of the date range.
statestring–2-letter US state code, e.g. TX.
summaryboolean–true = County Summary: county grade and counts by storm type ($0.02 per county).
windowstring–dataset=risk and the one-peril forecasts (<peril>_forecast). Forecast window. Default 24h.
x_paymentstring–Optional. A signed x402 protocol payment payload (base64), used instead of an API key to pay per call in USDC on Base network. Without a key or x_payment, the API returns an HTTP 402 quote with payme…

No output schema declared.

No examples provided.

Install

How do I install the TrueFixR Storm Data API MCP server?

TrueFixR Storm Data API is a hosted endpoint at https://mcp.atlasunited.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.atlasunited.io

# add to Claude Code
claude mcp add --transport http truefixr-atlascast-truefixr 'https://mcp.atlasunited.io/mcp'
Common questions

What is the TrueFixR Storm Data API MCP server?

TrueFixR Storm Data API is an MCP server listed in the public MCP registry as io.github.truefixr/atlascast-truefixr. Storm history by address since 2003, recent storm leads, model-based weather and storm forecasts. This page covers its hosted endpoint (https://mcp.atlasunited.io/mcp).

Is the TrueFixR Storm Data API MCP server safe to use?

TrueFixR Storm Data API scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

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

TrueFixR Storm Data API exposes 7 tools: get_weather_data, get_storm_history, get_risk_forecast, get_property_storm_history_report, get_current_weather, and 2 more. Their descriptions and schemas cost roughly 3,740 tokens of context every time the server is loaded.

Does the TrueFixR Storm Data API MCP server require authentication?

No. We connected to TrueFixR Storm Data API without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the TrueFixR Storm Data API MCP server still maintained?

TrueFixR Storm Data API is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the TrueFixR Storm Data API MCP server?

VerifyMCP ran 13 checks on TrueFixR Storm Data API, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.