Skip to content

RestoreWorth FEMA Data MCP server

com.restoreworth/fema-datarestoreworth.comstreamable-httpv1.0.0Scanned

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

5 tools: 4 change things and 1 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • 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 RestoreWorth FEMA Data MCP server can do

The RestoreWorth FEMA Data MCP server is published by restoreworth.com, a domain the MCP Registry verified. It has 5 tools. It can create or change data (4 tools: nfip_claims_by_state, nfip_claims_by_county, flood_damage_by_water_depth and county_profile), but cannot delete data. 1 tool only reads.

1 tool reads private data (list_sources).

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.

Last scanned Nov 14, 2026, version 1.0.0.

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.

5 tools

Changes things 4Claude Code: ask
  • county_profileFEMA 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 P…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: County FEMA profile
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true
  • flood_damage_by_water_depthMedian 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-flo…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: NFIP flood damage by interior water depth
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true
  • nfip_claims_by_countyNFIP paid building claims for one county, 2015-2024 and 2020-2024.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: NFIP paid building claims by county
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true
  • nfip_claims_by_stateNFIP 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…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: NFIP paid building claims by state
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: true
Only reads 1Show 1 read-only tool
  • list_sourcesLists every source file this server reads, with publisher, dataset page, terms, as-of and retrieval dates, and the RestoreWorth page that publishes it.Reads private dataNo findings

    Why it is in this group

    • The name "list_sources" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "file": it reads files.
    Description, as the server wrote it
    Lists every source file this server reads, with publisher, dataset page, terms, as-of and retrieval dates, and the RestoreWorth page that publishes it.

    Annotations the server declares

    • title: Sources and refresh dates
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
    • idempotentHint: 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 untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
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, 18:45 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
4
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
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://restoreworth.com/api/mcp: tools/list returned 5 tools to an anonymous client, including nfip_claims_by_state (write), nfip_claims_by_county (write), flood_damage_by_water_depth (write), county_profile (write)

    What this check looks for

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.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport http fema-data https://restoreworth.com/api/mcp
claude mcp add --transport http fema-data https://restoreworth.com/api/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__fema-data__list_sources"
    ],
    "ask": [
      "mcp__fema-data__nfip_claims_by_state",
      "mcp__fema-data__nfip_claims_by_county",
      "mcp__fema-data__flood_damage_by_water_depth",
      "mcp__fema-data__county_profile"
    ],
    "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 fema-data. Review it before you use it.

Capability tags behind 1 rule
  • mcp__fema-data__list_sources private-data

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/com.restoreworth/fema-data/verify?hash=e9ab659c4c335516e36ab67831577acf6783a082434128db1287c6bc91309feb" | jq -e '.changed == false'

Pinned hash e9ab659c4c33, from Nov 14, 2026, 05:17 UTC.

Watch

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

https://radar.anlyon.com/servers/com.restoreworth/fema-data/changes.xml

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

Badge

Anlyon Radar badge for com.restoreworth/fema-data
[![Anlyon Radar](https://radar.anlyon.com/badge/com.restoreworth/fema-data.svg)](https://radar.anlyon.com/servers/com.restoreworth/fema-data)

Source: MCP Registry. Synced Oct 21, 2026, 18:02 UTC.

RestoreWorth FEMA Data MCP server: questions and answers

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

Is the RestoreWorth FEMA Data MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the RestoreWorth FEMA Data MCP server delete data?

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

Can the RestoreWorth FEMA Data 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 RestoreWorth FEMA Data MCP server have?

5 tools: 4 write, 1 read. nfip_claims_by_state, nfip_claims_by_county, flood_damage_by_water_depth, county_profile and list_sources.

Does the RestoreWorth FEMA Data MCP server need sign-in or OAuth?

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

Does the RestoreWorth FEMA Data MCP server send data to outside services?

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

Has the RestoreWorth FEMA Data MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.