原型 · 预览版：收录官方注册中心里的全部服务器，每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚
新手模式 开
配色跟随系统浅色深色
语言ไทยEnglish中文日本語한국어EspañolDeutsch
☰ 菜单设置
新手模式 开
配色跟随系统浅色深色
语言ไทยEnglish中文日本語한국어EspañolDeutsch

TrueFixR Storm Data API

作者：truefixr版本 1.0.1i★ –i在云端运行
注册名称io.github.truefixr/atlascast-truefixr

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在云端运行
  • 传输方式: Streamable HTTP
  • 分类: 营销与社交媒体

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

你需要

你用的是哪个应用？

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

适用于网页版、桌面版和手机版 Claude：

  1. 打开 Settings → Connectors
  2. 点击 Add custom connector
  3. 粘贴下面的地址，然后点击 Add
  4. 如果要求登录，请登录作者的服务
SettingsConnectors1+ Add2https://…3
https://mcp.atlasunited.io/mcp

在终端中运行这条命令

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

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "atlascast-truefixr": {
      "type": "http",
      "url": "https://mcp.atlasunited.io/mcp"
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

ChatGPT 只能连接互联网上的服务器：

  1. 打开网页版 ChatGPT → Settings → Connectors (Apps)
  2. 点击 Create 或 Add（部分套餐需要先在 Advanced 中开启 Developer mode）
  3. 粘贴下面的地址，起个名字，然后保存
  4. 如果要求登录，请登录作者的服务
SettingsConnectors1+ Create2https://…3
https://mcp.atlasunited.io/mcp

菜单名称可能因套餐和版本不同而略有差异。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月8日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

  • get_weather_data

    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, 200

  • get_storm_history

    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

  • get_risk_forecast

    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

  • get_property_storm_history_report

    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,

  • get_current_weather

    ONE 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_report

    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 secon

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月9日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 truefixr 验证，该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • ✓ 通过

    端点有响应

    在 881 毫秒内响应（HTTP 200）

  • – 不适用

    使用 OAuth 登录

    无需登录

  • ✓ 通过

    工具描述中没有隐藏指令

    已读取 6 个工具描述，未发现针对 AI 的隐藏指令

与“营销与社交媒体”中的其他服务器比较i

  • 星标数多于此分类中其他 3639 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 3639 个服务器的 48% 更新
  • 基础检查结果等于或优于此分类中其他 3639 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

TrueFixR Storm Data API 安全吗？

它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在作者的云端运行。通过互联网连接，无需安装，但你发送的内容会经过作者的服务器。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（1.0.1）于32天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。

有什么可以替代它？

同一分类中有：MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

MCP YouTube Transcript

An MCP server retrieving transcripts of YouTube videos

作者：jkawamoto正在增长★ 49512天前更新

在你的电脑上运行
安装

Google Analytics MCP

GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.

作者：surendranb正在增长↓ 1088/周★ 24412天前更新

在你的电脑上运行
安装

BibiGPT YouTube Video Summarizer

AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.

作者：JimmyLv正在增长★ 13712天前更新

在云端运行✓ bibigpt.co
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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

  • 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
问 PopNx