mcpbeat Sign in

RestoreWorth FEMA Data MCP Server

by restoreworth Your server? Claim it
not responding

RestoreWorth FEMA Data is listed as active in the registry but did not answer our last check. It exposes 5 tools.

FEMA NFIP flood claims by state and county, damage by water depth, county profiles. Read-only.

Uptime history 24 days of history · worst day 0%
24 days agonow
5.5%
Uptime 24h
5 of 91 checks
5
Tools
read from the server
281 ms
Response time
average over 24h
open, no key
Access
streamable-http

RestoreWorth FEMA Data does not always answer

Over the last week it answered 8.6% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add fema-data --transport http https://restoreworth.com/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://restoreworth.com/api/mcp
~/.codex/config.toml
[mcp_servers.fema-data]
url = "https://restoreworth.com/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "fema-data": {
      "url": "https://restoreworth.com/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "fema-data": {
      "type": "http",
      "url": "https://restoreworth.com/api/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

nfip
nfip_claims_by_county
NFIP paid building claims for one county, 2015-2024 and 2020-2024. Give a 5-digit FIPS code, or a county name and its state. A county absent from the table (it keeps counties with at least 100 paid claims) gets the state row, and the answer says so. These are amounts paid by NFIP, not repair cost.
nfip_claims_by_state
NFIP paid building claims for one US state or DC, 2020-2024 (FEMA OpenFEMA, NFIP Redacted Claims v3): number of paid claims, quartiles and median of the amount paid, dominant flood event and its share. These are amounts paid by NFIP, not repair cost.
county
county_profile
FEMA open-data profile of one county by 5-digit FIPS: NFIP paid claims summary, disaster declarations since 2000, FEMA inspections of owner applicants (Individuals and Households Program), NFIP Community Status Book and CRS classes. A value the source does not give is returned as "not in source", never 0.
flood
flood_damage_by_water_depth
Median damage ratio (FEMA actual cash value of the damage / actual cash value of the building) on NFIP paid claims 2015-2024, by interior water depth band and single-family one-floor segment. With building_value_usd, returns ratio x value: the median ratio of the band, not an estimate for this home.
sources
list_sources
Lists every source file this server reads, with publisher, dataset page, terms, as-of and retrieval dates, and the RestoreWorth page that publishes it.

Endpoints

URLTransportStateLatencyChecked
https://restoreworth.com/api/mcp streamable-http answering 99 ms 13 min ago

Alternatives to RestoreWorth FEMA Data

same job, measured the same way
Claims Index
by damagerestorehq

DamageRestore HQ: the median paid water damage claim, read from NFIP claim records (2023 to...

55 installs/wk local only
KirinBoard
by kirinboard

Read-only agent claims, CI status and delivery data from a KirinBoard workspace

18 tools answering
US Disaster Declarations (FEMA) MCP
by donniertf-hub

FEMA disaster declarations by state and county.

3 tools answering
Ethos
by ethos

Ethos credibility scores and profiles for wallets and X accounts. Read-only, free, no key.

5 tools answering
KeepUp
by keepup

Net worth percentiles by country and age, and how KeepUp users compare. Read-only, no key.

5 tools answering
Instagram Data
by fastsocialco

Read-only public Instagram data: profiles, posts, reels, stories, comments, top-accounts ranking.

195 installs/wk answering
Census MCP
by mrfentmen

US Census population data by nation, state, and county. Requires a free Census API key.

203 installs/wk local only
codeDB Lens
by codedb-io

Read-only health checks and data questions for SQL Server and PostgreSQL, with your saved profiles.

local only

RestoreWorth FEMA Data — questions

Answers built from our own checks of this server.

What can RestoreWorth FEMA Data do?
It exposes 5 tools, read directly from the server on our last check. Among them: county_profile, flood_damage_by_water_depth, list_sources, nfip_claims_by_county, nfip_claims_by_state. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is RestoreWorth FEMA Data working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 5 of 91 checks got a reply (5.5%), average response time 281 ms. The bar chart above shows every period we have measured.
The registry lists RestoreWorth FEMA Data as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect RestoreWorth FEMA Data?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does RestoreWorth FEMA Data need an API key?
No. RestoreWorth FEMA Data completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is RestoreWorth FEMA Data?
It answers our handshake in 281 ms on average, which is faster than 49% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.