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.

io.github.cyanheads/fema-mcp-server

REMOTE · FEMA.CASEYJHAND.COM · 2 COMPONENTS

Query FEMA disaster declarations, public assistance grants, housing aid, and NFIP claims.

0 this week 89 Trust /100

Last scanned (1 hour ago)

Scores higher than 97% of remote servers

Reachable. Last reached 5 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 Security83
Transport & Reachability100
Schema Quality & AI Usability75
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3258 tokens (~362/item across 9 items; 8 tools + 1 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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
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.

  • 5 Nov 26 +1
    • Stability: 0.97 → pass security
  • 4 Nov 26 −1
    • Tool “fema_search_disasters” rewrote its description, which is the text the model reads security
    • Stability: pass → 0.97 functional
    • Server version: 0.5.0 → 0.5.1 functional
    • “fema_search_disasters” added an optional parameter “title” cosmetic
    • “fema_search_disasters” reworded the description of “county” cosmetic
    • “fema_get_public_assistance” reworded the description of “county” cosmetic
    • “fema_get_housing_assistance” reworded the description of “county” cosmetic
  • 29 Oct 26 +2
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “fema_search_nfip” rewrote its description, which is the text the model reads security
    • Schema quality: unverified → 100 ▲ functional
    • New resource “fema-guide” functional
    • Server version: 0.4.1 → 0.5.0 functional
  • 19 Oct 26 0
    • Tool “fema_get_disaster” rewrote its description, which is the text the model reads security
    • Server version: 0.4.0 → 0.4.1 functional
  • 17 Oct 26 +63
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • HSTS header: fail → pass ▲ security
    • Transport: fail → pass ▲ security
    • Tool “fema_search_disasters” rewrote its description, which is the text the model reads security
    • Tool “fema_search_nfip” rewrote its description, which is the text the model reads security
    • Tool “fema_dataframe_query” rewrote its description, which is the text the model reads security
    • Tool “fema_get_housing_assistance” rewrote its description, which is the text the model reads security
    • Tool “fema_get_public_assistance” rewrote its description, which is the text the model reads security
    • Tool “fema_query_dataset” rewrote its description, which is the text the model reads security
    • Schema quality: 281 → 380 ▼ functional
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Server version: 0.3.2 → 0.4.0 functional
    • “fema_get_housing_assistance” added an optional parameter “county” cosmetic
    • “fema_get_housing_assistance” added an optional parameter “zip_code” cosmetic
    • “fema_query_dataset” reworded the description of “filter” cosmetic
    • “fema_query_dataset” reworded the description of “limit” cosmetic
    • “fema_query_dataset” reworded the description of “offset” cosmetic
    • “fema_search_disasters” reworded the description of “county” cosmetic
    • “fema_search_nfip” reworded the description of “year_to” cosmetic
    • “fema_search_nfip” reworded the description of “year_from” cosmetic
    • “fema_search_nfip” reworded the description of “offset” cosmetic
    • “fema_search_nfip” reworded the description of “limit” cosmetic
    • “fema_search_nfip” reworded the description of “county_code” cosmetic
    • “fema_search_disasters” reworded the description of “offset” cosmetic
    • “fema_search_disasters” reworded the description of “limit” cosmetic
    • “fema_search_disasters” reworded the description of “incident_type” cosmetic
    • “fema_search_disasters” reworded the description of “date_to” cosmetic
    • “fema_search_disasters” reworded the description of “date_from” cosmetic
    • “fema_dataframe_query” reworded the description of “query” cosmetic
    • “fema_get_housing_assistance” reworded the description of “limit” cosmetic
    • “fema_get_housing_assistance” reworded the description of “offset” cosmetic
    • “fema_get_public_assistance” reworded the description of “county” cosmetic
    • “fema_get_public_assistance” reworded the description of “limit” cosmetic
    • “fema_get_public_assistance” reworded the description of “offset” cosmetic
  • 16 Oct 26 −63
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • HSTS header: pass → fail ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 4 Oct 26 0
    • Server version: 0.3.1 → 0.3.2 functional
  • 28 Sept 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 5 Nov 2026 · Probed https://fema.caseyjhand.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=caseyjhand.com CN=WE1,O=Google Trust Services,C=US 2 Nov 2026 31 Jan 2027 ECDSA 256 ECDSA-SHA256 995a30681ab772540e934241ca1d576c
SANs: caseyjhand.com, *.caseyjhand.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of fema.caseyjhand.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
caseyjhand.com. present 2371 13 Verified
fema.caseyjhand.com. Verified address RRset verified with the apex keys
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
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://fema.caseyjhand.com/mcp Verified 200
http (plaintext) http://fema.caseyjhand.com/mcp HTTPS enforced 301 https://fema.caseyjhand.com/mcp
MCP tools · 8 exposed · ~3,060 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
fema_dataframe_describe ~103

List tables and column schemas on a DataCanvas staged by fema_search_nfip. Call this before fema_dataframe_query to discover the exact table name, column names, and DuckDB data types needed to write valid SQL. Row count reflects what was actually staged — check truncated in the fema_search_nfip response to know whether the canvas holds the full matching set.

NameTypeReqDescription
canvas_idstringyesCanvas ID from the fema_search_nfip response.
NameTypeReqDescription
canvas_idstring–Canvas ID that was described — pass to fema_dataframe_query.
errorobject–Present when the call failed. Absent on success.
tablesarray–All tables and views available on this canvas.

No examples provided.

fema_dataframe_query ~286

Run a read-only SQL SELECT against a DataCanvas table staged by fema_search_nfip. Enables aggregation, GROUP BY, SUM/COUNT, time-series, and filtered analysis over the full NFIP claims result without re-fetching from the API. Call fema_dataframe_describe first to get the exact table name and column names needed for valid SQL. Only SELECT statements are allowed — DDL, DML, COPY, and file-reading functions are blocked. A response holds at most 100,000 characters of rows; when it holds fewer rows than the query returned, truncated and shown are set and the notice says how to page with OFFSET.

NameTypeReqDescription
canvas_idstringyesCanvas ID from the fema_search_nfip response (the canvas_id field).
querystringyesSQL SELECT statement to run against the staged table. Use the table name from fema_dataframe_describe. Results are capped at the canvas row limit and at 100,000 characters of rows; append LIMIT/OFFSE…
NameTypeReqDescription
canvas_idstring–Canvas ID that was queried — reuse for follow-up queries.
capnumber–The canvas row limit, present only when it capped the result. Absent when only the response budget cut it.
errorobject–Present when the call failed. Absent on success.
noticestring–Continuation guidance when truncated — how far to advance OFFSET, and lower any LIMIT, under an ORDER BY, to page the remainder.
row_countnumber–Number of rows in this response — fewer than the query returned when truncated is set.
rowsarray–Result rows from the query, bounded by the canvas row limit and by 100,000 characters of rows — when the truncated enrichment field is set, page the remainder with OFFSET (see the notice guidance).
shownnumber–Number of rows in this truncated response — the amount to advance OFFSET by, and to lower any LIMIT by, for the next page.
truncatedboolean–True when more rows match than this response holds: the result was capped at the canvas row limit, or cut at the 100,000-character response budget.

No examples provided.

fema_get_disaster ~126

Fetch up to 1,000 designated-area rows for a specific FEMA disaster by disaster number (e.g., 4781). Discloses partial area and program coverage when more rows exist. Returns counties/municipalities along with programs observed, incident period, and state info. Use fema_search_disasters to find disaster numbers. The returned disaster_number chains to fema_get_public_assistance and fema_get_housing_assistance.

NameTypeReqDescription
disaster_numberintegeryesFEMA disaster number (e.g., 4781). Obtain from fema_search_disasters.
NameTypeReqDescription
areas_truncatedboolean–True when designated-area rows remain unfetched; program flags cover only fetched rows.
declaration_datestring–ISO 8601 date the declaration was signed.
declaration_typestring–Declaration type: DR (major disaster), EM (emergency), or FM (fire management).
designated_area_countnumber–Number of designated-area rows fetched for this declaration.
designated_areasarray–Fetched counties/municipalities designated for assistance, up to 1,000 rows.
disaster_numbernumber–FEMA disaster number — use as the chain key for PA and housing assistance tools.
errorobject–Present when the call failed. Absent on success.
hm_declaredboolean–True when HM was declared in a fetched row. When areas_truncated is true, false does not exclude HM in unfetched rows.
ia_declaredboolean–True when legacy IA or IHP was declared in a fetched row. Does not guarantee housing records. When areas_truncated is true, false does not exclude IA in unfetched rows.
incident_begin_datestring–ISO 8601 start date of the incident. Absent when not recorded.
incident_end_datestring–ISO 8601 end date of the incident. Absent for ongoing or unrecorded incidents.
incident_typestring–Type of incident (e.g., Flood, Hurricane, Severe Storm).
noticestring–Returned/total area counts and partial program evidence, with the dataset tool for full rows.
pa_declaredboolean–True when PA was declared in a fetched row. When areas_truncated is true, false does not exclude PA in unfetched rows.
statestring–Two-letter state/territory code.
titlestring–Official declaration title (e.g., "SEVERE STORMS AND FLOODING").
total_designated_area_countnumber–Upstream total designated-area rows, present when areas_truncated is true.

No examples provided.

fema_get_housing_assistance ~442

Retrieve Individual Assistance (IA) housing data for a disaster by disaster number. Returns owner and/or renter records aggregated by county, city, and ZIP code — valid registrations, total approved IHP amounts, repair/rental/other-needs amounts, and inspection counts (owners also carry inspected damage in USD). Narrow with state, county, or zip_code; owners_count, renters_count, and offset then count the filtered records. Use type to select owners, renters, or both (default). A page holds at most 100,000 characters of records, owners and renters cut at the same row count so one offset continues both; when records remain past it, next_offset is the offset to continue from. Use disaster_number from fema_search_disasters.

NameTypeReqDescription
countystring–Filter by county name (e.g., Harris, Harris County, Harris (County)). Case-insensitive substring match: bare harris also matches Harrison. Recognized terminal County, Parish, Borough, and Census Area…
disaster_numberintegeryesFEMA disaster number. Obtain from fema_search_disasters. Numbers above 32767 match no declaration.
limitinteger–Maximum records per dataset to return (1–10000, default 100). A page also stops at 100,000 characters of owner and renter records together, cutting both datasets at the same row count; when either bo…
offsetinteger–Pagination offset into each queried dataset (default 0). Pass the previous page’s next_offset to continue both.
statestring–Two-letter state code to narrow results when a disaster spans multiple states.
typestring–Which housing assistance dataset to query: owners, renters, or both (default).
zip_code––Filter by 5-digit ZIP code, as a string with leading zeros kept (e.g., 77084, 00609). ZIP+4 is not accepted. One ZIP can return several records, one per county and city spelling.
NameTypeReqDescription
county_filterstring–The county name both datasets were filtered by, trimmed, matched as a case-insensitive substring. Absent when county was not set.
errorobject–Present when the call failed. Absent on success.
next_offsetnumber–Offset of the next page, for both datasets: offset plus the larger of the owner and renter record counts returned. Present only while records remain in a queried dataset; pass it as offset to continu…
noticestring–Zero-match guidance for supplied filters and declared programs, or paging guidance: the continuation offset and whether limit or the response budget ended the page, and each queried nonzero dataset’s…
ownersarray–Homeowner (HousingAssistanceOwners) records. Empty when type is "renters" or no owner data exists.
owners_countnumber–Total owner records matching the disaster and any state, county, or zip_code filter, before the per-dataset limit.
rentersarray–Renter (HousingAssistanceRenters) records. Empty when type is "owners" or no renter data exists.
renters_countnumber–Total renter records matching the disaster and any state, county, or zip_code filter, before the per-dataset limit.
totalCountnumber–Total owner + renter records available before the per-dataset limit — exceeds the returned count when either dataset was capped.
zip_code_filterstring–The 5-digit ZIP code both datasets were filtered by. Absent when zip_code was not set.

No examples provided.

fema_get_public_assistance ~330

Retrieve Public Assistance (PA) funded project records for a disaster or state — shows where federal recovery money was obligated. Returns applicant, damage category, project size and status, federal share obligated, and total obligated amounts. Either disaster_number or state must be provided. Use disaster_number (from fema_search_disasters) to scope to a single declaration, or state to browse all PA projects for a state. PA projects are created only when the PA program is declared (pa_declared: true on the disaster). A page holds at most 100,000 characters of projects; when projects remain past it, next_offset is the offset to continue from.

NameTypeReqDescription
countystring–Filter by county name (e.g., Harris, dekalb). Case-insensitive substring match: harris also matches Harrison. Recognized terminal County, Parish, Borough, and Census Area names accept plain or parent…
disaster_numberinteger–FEMA disaster number to scope results to a single declaration. Numbers above 32767 match no declaration.
limitinteger–Maximum number of projects to return (1–10000, default 100). A page also stops at 100,000 characters of projects (roughly 220 projects); when either bound leaves matching projects out, next_offset na…
offsetinteger–Pagination offset (default 0). Pass the previous page’s next_offset to continue.
statestring–Two-letter state code to browse all PA projects for a state.
NameTypeReqDescription
errorobject–Present when the call failed. Absent on success.
next_offsetnumber–Offset of the next page: offset plus returned_count. Present only while matching projects remain past this page; pass it as offset to continue.
noticestring–Zero-match guidance for supplied filters and declared programs, or paging guidance: the continuation offset and whether limit or the response budget ended the page, or the last valid offset for a non…
projectsarray–Public assistance funded project records from offset onward, bounded by limit and by 100,000 characters of projects.
returned_countnumber–Number of projects in this response.
totalCountnumber–Total matching projects before pagination — exceeds returned_count when results were capped at the limit.
total_countnumber–Total matching projects before pagination.

No examples provided.

fema_query_dataset ~459

Generic OData query against any dataset in the OpenFEMA dataset catalog — the escape hatch for datasets the convenience tools do not cover (e.g., NfipPolicies, IndividualAssistanceHousingRegistrantsLargeDisasters, FemaWebDeclarationAreas, PublicAssistanceApplicants). Accepts raw OData filter, select, orderby, and pagination parameters. For NfipPolicies, use propertyState (not state) for the state and reportedZipCode for the ZIP code — it has no countyCode; always include a ZIP filter to avoid timeout. The dataset name must match the exact OpenFEMA entity name (case-sensitive, e.g., NfipClaims). Names missing from the catalog return an unknown_dataset error; a listed dataset OpenFEMA does not serve through the API, or a retired version, returns dataset_not_served. A page holds at most 100,000 characters of records; when records remain past it, next_offset is the offset to continue from.

NameTypeReqDescription
datasetstringyesOpenFEMA dataset entity name (case-sensitive, e.g., NfipPolicies, FemaWebDeclarationAreas, PublicAssistanceApplicants).
filterstring–OData $filter expression (e.g., "state eq 'TX' and declarationDate ge '2024-01-01T00:00:00.000Z'"). String values in single quotes. For a list of values use field in ('a','b'): OpenFEMA rejects filte…
limitinteger–Maximum records to return (1–10000, default 100). A page also stops at 100,000 characters of records; when either bound leaves matching records out, next_offset names the offset to continue from.
offsetinteger–Pagination offset (default 0). Pass the previous page’s next_offset to continue.
orderbystring–OData $orderby expression (e.g., "declarationDate desc").
selectstring–Comma-separated field names to return (e.g., "disasterNumber,state,declarationDate").
NameTypeReqDescription
datasetstring–The dataset that was queried.
errorobject–Present when the call failed. Absent on success.
next_offsetnumber–Offset of the next page: offset plus returned_count. Present only while matching records remain past this page; pass it as offset to continue.
noticestring–Paging guidance — the offset to continue from and whether limit or the response budget ended the page, filter advice when nothing matches, or the total and last valid offset when offset is at or past…
returned_countnumber–Number of records in this response.
rowsarray–Records from offset onward, bounded by limit and by 100,000 characters of records. Field names depend on the queried dataset.
totalCountnumber–Total matching records before pagination — exceeds returned_count when results were capped at the limit.
total_countnumber–Total matching records before pagination.

No examples provided.

fema_search_disasters ~654

Search federal disaster declarations by title, state, incident type, declaration type, date range, and county. Returns deduplicated declaration-level summaries — each disaster number appears once with a designated_area_count showing how many counties/municipalities were designated. The disaster number is the chain key for fema_get_disaster, fema_get_public_assistance, and fema_get_housing_assistance. Use declaration_type to filter: DR (major disaster, most common), EM (emergency), FM (fire management). Date filters apply to the declaration date. Use fema_get_disaster to retrieve all designated-area rows for a specific declaration. county selects the declarations that designated a matching area; their area counts and program flags still describe the whole declaration, and matched_areas lists the matching areas with their own program flags. A search reads the most recent 10,000 designated-area rows; when more match, it returns the declarations dated after the day that window ends, sets truncated, and its notice names the date_to that continues with older declarations. A page holds at most 100,000 characters of declarations; when declarations remain past it, next_offset is the offset to continue from.

NameTypeReqDescription
countystring–Filter by designated area / county name (e.g., Harris, Harris County, Harris (County)). Case-insensitive substring match: bare harris also matches Harrison. Recognized terminal County, Parish, Boroug…
date_from––Start of the declaration date range as a calendar date in YYYY-MM-DD format (e.g., 2024-01-01). Inclusive; not after date_to.
date_to––End of the declaration date range as a calendar date in YYYY-MM-DD format (e.g., 2024-12-31). Inclusive; equal to date_from for a single day.
declaration_typestring–Declaration type: DR (major disaster declaration), EM (emergency declaration), FM (fire management assistance declaration).
incident_typestring–Incident type filter (e.g., Flood, Hurricane, Tornado, Fire, Earthquake, Severe Storm). Case-insensitive substring match: storm also matches Snowstorm and Winter Storm.
limitinteger–Maximum number of unique disaster declarations to return (1–1000, default 50). A page also stops at 100,000 characters of declarations (roughly 290 declarations, about 190 with county); when either b…
offsetinteger–Pagination offset in declarations (default 0). Pass the previous page’s next_offset to continue.
statestring–Two-letter US state/territory code (e.g., TX, CA, FL, PR). Filters by state.
titlestring–Case-insensitive substring of the declaration title (e.g., harvey). A substring can also match unrelated names such as HARVEYTOWN FIRE; it does not identify a unique storm.
NameTypeReqDescription
area_totals_unavailableboolean–True when county is set and reading the returned declarations’ full designated-area rows failed: designated_area_count and the ia/pa/hm flags then count only the areas county matched, and the notice…
declarationsarray–Disaster declarations matching the search from offset onward, one entry per unique disaster number, bounded by limit and by 100,000 characters of declarations.
errorobject–Present when the call failed. Absent on success.
next_offsetnumber–Offset of the next page: offset plus returned_count. Present only while matching declarations remain past this page — when truncated is true, only within the declarations dated after the day the wind…
noticestring–Zero-match guidance for supplied filters; paging guidance with continuation or the last valid offset for nonzero totals; when truncated is true, lower-bound totals and the date_to (YYYY-MM-DD) to sea…
returned_countnumber–Number of unique deduplicated declarations in this response.
totalCountnumber–Unique disaster declarations matching the query — the unit declaration-level pagination pages over. Exceeds returned_count when the matches span more than one page. A lower bound when truncated is tr…
total_area_rowsnumber–Total matching designated-area rows from the API (raw row count, not declaration count) — with county set, the rows of the matching areas only. DisasterDeclarationsSummaries returns one row per desig…
total_declarationsnumber–Unique disaster declarations matching the query, before offset/limit paging — the bound for declaration-level pagination (limit/offset apply to declarations, not area rows). A lower bound when trunca…
truncatedboolean–True when more than 10,000 designated-area rows match: the search covers only the declarations dated after the day its 10,000-row window ends. Each returned declaration is complete, the totals are lo…

No examples provided.

fema_search_nfip ~660

Search National Flood Insurance Program (NFIP) claims data by state, county, ZIP code, and year range. Returns the matching claim count and claim records — amounts paid on building and contents, damage estimates, flood zones, cause and occupancy codes, and loss dates — newest loss first. state is required — the full NFIP dataset is 2.7 million rows; unfiltered access is prohibited. Page the inline claims with limit and offset; a page holds at most 100,000 characters of claims, and while claims remain past it, next_offset is the offset to continue from. When DataCanvas is enabled and the match exceeds that inline budget, a call at offset 0 stages the match (up to 50,000 claims) on a canvas: inspect the staged table with fema_dataframe_describe, then aggregate it with SQL via fema_dataframe_query.

NameTypeReqDescription
canvas_idstring–Optional canvas ID from a prior call, to stage this match as another table on that canvas. Used only when the match is staged; omit it to stage on a fresh canvas. Pass the returned canvas_id to fema_…
county_codestring–County FIPS code to narrow results within the state: the full 5-digit state+county code (e.g., 48201 for Harris County TX), or the 3-digit county part (e.g., 201), to which the server prepends the st…
limitinteger–Maximum claims to return inline (1–10000, default 1000). A page also stops at 100,000 characters of claims (roughly 330 claims); when either bound leaves matching claims out, next_offset names the of…
offsetinteger–Pagination offset into the matching claims, ordered newest date of loss first (default 0). Pass the previous page’s next_offset to continue. Only a call at offset 0 stages a match on a canvas; a late…
statestringyesTwo-letter US state code (required). NFIP dataset is 2.7M rows — state filter is mandatory.
year_frominteger–Start year of loss, inclusive (e.g., 2020). Not after year_to.
year_tointeger–End year of loss, inclusive (e.g., 2023). Equal to year_from for a single year.
zip_codestring–ZIP code to narrow results to a specific area (5-digit, e.g., 77002).
NameTypeReqDescription
canvas_idstring–Canvas ID for the staged match. Pass to fema_dataframe_describe and fema_dataframe_query. Present only when spilled=true.
canvas_tablestring–DuckDB table on the canvas holding the staged claims. List its columns with fema_dataframe_describe, then reference it in fema_dataframe_query FROM clauses. Present only when spilled=true.
claimsarray–Claims from offset onward, newest date of loss first, bounded by limit and 100,000 characters of claims. When spilled=true, canvas_table holds the staged match.
errorobject–Present when the call failed. Absent on success.
next_offsetnumber–Offset of the next inline page: offset plus returned_count. Present only while matching claims remain past this page, after a spill too; pass it as offset to continue.
noticestring–Zero-match, paging, and canvas guidance, composed with county-coverage disclosure: a state/year count of claims without county codes when already available, or an unchecked-coverage notice; this coun…
returned_countnumber–Number of claim records in claims.
spilledboolean–True when the match exceeded the inline budget and was staged on DataCanvas: call fema_dataframe_describe, then fema_dataframe_query, with canvas_id. False when nothing was staged.
staged_countnumber–Claims staged on canvas_table: the whole match, or its first 50,000 when truncated=true. Present only when spilled=true.
total_countnumber–Claims matching the filters, as counted by OpenFEMA — before offset, limit, and the canvas row cap.
truncatedboolean–True when the 50,000-row canvas cap was reached: canvas_table holds staged_count of the total_count matching claims. Apply tighter filters (county_code, zip_code, year range) to stage the complete se…

No examples provided.

Install

How do I install the io.github.cyanheads/fema-mcp-server server?

io.github.cyanheads/fema-mcp-server is a hosted endpoint at https://fema.caseyjhand.com/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 · fema.caseyjhand.com

# add to Claude Code
claude mcp add --transport http cyanheads-fema-mcp-server 'https://fema.caseyjhand.com/mcp'
Common questions

What is the io.github.cyanheads/fema-mcp-server server?

io.github.cyanheads/fema-mcp-server is listed in the public MCP registry as io.github.cyanheads/fema-mcp-server. Query FEMA disaster declarations, public assistance grants, housing aid, and NFIP claims. This page covers its hosted endpoint (https://fema.caseyjhand.com/mcp).

Is the io.github.cyanheads/fema-mcp-server server safe to use?

io.github.cyanheads/fema-mcp-server scores 89 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 io.github.cyanheads/fema-mcp-server server expose?

io.github.cyanheads/fema-mcp-server exposes 8 tools: fema_search_disasters, fema_get_disaster, fema_get_public_assistance, fema_get_housing_assistance, fema_search_nfip, and 3 more. Their descriptions and schemas cost roughly 3,060 tokens of context every time the server is loaded.

Does the io.github.cyanheads/fema-mcp-server server require authentication?

No. We connected to io.github.cyanheads/fema-mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.cyanheads/fema-mcp-server server still maintained?

io.github.cyanheads/fema-mcp-server is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.