Skip to content

FEMA Disasters MCP server

com.olyport/femaolyport.comstreamable-httpv1.1.0Scanned

Federal disaster declarations, emergencies, and assistance data

5 tools: 5 only read.

Tools: 0 delete, 0 irreversible, 0 write, 5 read.
  • Reads private data · 0
  • Reads text others write · 0
  • 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 FEMA Disasters MCP server can do

The FEMA Disasters MCP server is published by olyport.com, a domain the MCP Registry verified. It has 5 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

None of its tools reads private data, brings in text other people write, or sends data out.

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 17, 2026, version 1.1.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

Only reads 5Show 5 read-only tools
  • get_disaster_declarationsGet FEMA disaster declarations filtered by state, year, or type.No findings

    Why it is in this group

    • The name "get_disaster_declarations" says "get": a word for reading.
    Description, as the server wrote it
    Get FEMA disaster declarations filtered by state, year, or type. Returns federal disaster declarations including major disasters, emergencies, and fire management assistance. Each record includes the disaster number, title, declaration date, and affected area. Args: state: Two-letter US state abbreviation (e.g. 'CA', 'TX', 'FL'). year: Filter by fiscal year of the declaration (e.g. 2023). disaster_type: Declaration type code: 'DR' (major disaster), 'EM' (emergency), or 'FM' (fire management assistance). limit: Maximum number of records to return (default 25, max 1000).
  • get_disaster_detailGet detailed information about a specific FEMA disaster declaration.No findings

    Why it is in this group

    • The name "get_disaster_detail" says "get": a word for reading.
    Description, as the server wrote it
    Get detailed information about a specific FEMA disaster declaration. Returns comprehensive data for a single disaster including all declared programs, incident dates, and affected areas. Use disaster numbers from get_disaster_declarations results. Args: disaster_number: The FEMA disaster number (e.g. 4737, 3604).
  • get_hazard_mitigation_grantsGet FEMA Hazard Mitigation Grant Program (HMGP) data.No findings

    Why it is in this group

    • The name "get_hazard_mitigation_grants" says "get": a word for reading.
    Description, as the server wrote it
    Get FEMA Hazard Mitigation Grant Program (HMGP) data. Returns data on grants awarded to reduce future disaster losses through mitigation projects such as property acquisition, elevation, and infrastructure improvements. Args: state: Two-letter US state abbreviation (e.g. 'CA', 'TX'). limit: Maximum number of records to return (default 25, max 1000).
  • get_individual_assistanceGet FEMA Individual and Households Program (IHP) assistance data.No findings

    Why it is in this group

    • The name "get_individual_assistance" says "get": a word for reading.
    Description, as the server wrote it
    Get FEMA Individual and Households Program (IHP) assistance data. Returns aggregated data on individual assistance provided to disaster survivors including housing assistance and other needs assistance. Data is aggregated at the county level per disaster. Args: disaster_number: FEMA disaster number to filter by (e.g. 4737). state: Two-letter US state abbreviation (e.g. 'CA', 'TX'). limit: Maximum number of records to return (default 25, max 1000).
  • get_public_assistanceGet FEMA Public Assistance (PA) grant data for disaster recovery.No findings

    Why it is in this group

    • The name "get_public_assistance" says "get": a word for reading.
    Description, as the server wrote it
    Get FEMA Public Assistance (PA) grant data for disaster recovery. Returns PA grant obligations that fund debris removal, emergency protective measures, and permanent restoration of infrastructure. Filter by disaster number or state. Args: disaster_number: FEMA disaster number to filter by (e.g. 4737). state: Two-letter US state abbreviation (e.g. 'CA', 'TX'). limit: Maximum number of records to return (default 25, max 1000).

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 untrusted-input or outbound.

Reads private data0
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, 19:29 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.

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.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http fema https://mcp.olyport.com/fema/mcp
claude mcp add --transport http fema https://mcp.olyport.com/fema/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__get_disaster_declarations",
      "mcp__fema__get_disaster_detail",
      "mcp__fema__get_public_assistance",
      "mcp__fema__get_individual_assistance",
      "mcp__fema__get_hazard_mitigation_grants"
    ],
    "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 fema. Review it before you use it.

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.olyport/fema/verify?hash=e3887b1cd72a2eaef82f1f86f691ea5dfad3bfb848d05122aa59b8ca611fd804" | jq -e '.changed == false'

Pinned hash e3887b1cd72a, from Nov 17, 2026, 22:17 UTC.

Watch

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

https://radar.anlyon.com/servers/com.olyport/fema/changes.xml

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

Badge

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

Source: MCP Registry. Synced Oct 21, 2026, 17:59 UTC.

FEMA Disasters MCP server: questions and answers

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

Is the FEMA Disasters MCP server safe?

No scan can promise that. What its definitions show: 5 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 FEMA Disasters MCP server delete data?

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

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

5 tools: 5 read. get_disaster_declarations, get_disaster_detail, get_public_assistance, get_individual_assistance and get_hazard_mitigation_grants.

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

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

Does the FEMA Disasters MCP server send data to outside services?

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

Has the FEMA Disasters MCP server changed its tools?

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