# io.github.cyanheads/fema-mcp-server (remote · fema.caseyjhand.com) Query FEMA disaster declarations, public assistance grants, housing aid, and NFIP claims. - Trust score: 68/100 (medium) - Change this week: +5 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-08-03 ## Components - remote · `fema.caseyjhand.com`: 68/100 (this document), [markdown](https://verifymcp.io/servers/cyanheads-fema-mcp-server/fema.md), [page](https://verifymcp.io/servers/cyanheads-fema-mcp-server/fema) - npm · `@cyanheads/fema-mcp-server`: 35/100, [markdown](https://verifymcp.io/servers/cyanheads-fema-mcp-server/cyanheads-fema-mcp-server.md), [page](https://verifymcp.io/servers/cyanheads-fema-mcp-server/cyanheads-fema-mcp-server) ## Channel facts - Endpoint: `https://fema.caseyjhand.com/mcp` - Transports: `streamable-http` - Auth: `none` - Version: `0.1.13` ## Trust breakdown 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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-08-03. - **Endpoint Security**: 66/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. - HTTPS is enforced; there's no plaintext access path. - The HSTS (Strict-Transport-Security) header is present. - DNSSEC is configured correctly; the domain's records validate against the full chain to the root. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 63/100 - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 2049 tokens (~256/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 27/100 - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - Structured output schemas are declared (100% of tools); any adoption earns full credit. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. ## Install ### Claude ```bash claude mcp add --transport http cyanheads-fema-mcp-server https://fema.caseyjhand.com/mcp ``` ### Codex ```toml [mcp_servers.cyanheads-fema-mcp-server] url = "https://fema.caseyjhand.com/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "cyanheads-fema-mcp-server": { "type": "remote", "url": "https://fema.caseyjhand.com/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add cyanheads-fema-mcp-server --url https://fema.caseyjhand.com/mcp --transport streamable-http ``` ### Hermes ```yaml mcp_servers: cyanheads-fema-mcp-server: url: "https://fema.caseyjhand.com/mcp" ``` ### Other ```json { "mcpServers": { "cyanheads-fema-mcp-server": { "type": "http", "url": "https://fema.caseyjhand.com/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-08-03 (score 68, +1) No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-07-31 (score 67, +2) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-07-30 (score 65, +1) No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-07-28 (score 64, +1) No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-07-27 (score 63, +1) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-07-26 (score 62) First indexed and scored. ## MCP tools (8) ### `fema_search_disasters` (~370 tokens) Search FEMA Disaster Declarations Search federal disaster declarations by state, incident type, declaration type, date range, and county. Returns deduplicated declaration-level summaries — each disaster number appears once with a designatedAreaCount 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. Input parameters: - `county` (string): Filter by designated area / county name substring (e.g., Harris, Los Angeles). Case-insensitive. - `date_from` (string): Start of declaration date range in ISO 8601 format (e.g., 2024-01-01). Inclusive. - `date_to` (string): End of declaration date range in ISO 8601 format (e.g., 2024-12-31). Inclusive. - `declaration_type` (string): Declaration type: DR (major disaster declaration), EM (emergency declaration), FM (fire management assistance declaration). - `incident_type` (string): Incident type filter (e.g., Flood, Hurricane, Tornado, Fire, Earthquake, Severe Storm). Case-insensitive substring match. - `limit` (integer): Maximum number of unique disaster declarations to return (1–1000, default 50). - `offset` (integer): Pagination offset in declarations (default 0). Use with limit to page through results. - `state` (string): Two-letter US state/territory code (e.g., TX, CA, FL, PR). Filters by state. Output parameters: - `declarations` (array): Disaster declarations matching the search, one entry per unique disaster number. - `notice` (string): Guidance when no results were found. - `returned_count` (number): Number of unique deduplicated declarations in this response. - `totalCount` (number): Total unique disaster declarations matching the query — the unit declaration-level pagination pages over. Exceeds returned_count when the matches span more than one page. - `total_area_rows` (number): Total matching designated-area rows from the API (raw row count, not declaration count). DisasterDeclarationsSummaries returns one row per designated area per disaster, so this is always ≥ the number… - `total_declarations` (number): Total 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 floor rather than… ### `fema_get_disaster` (~112 tokens) Get FEMA Disaster Details Fetch all designated-area rows for a specific FEMA disaster by disaster number (e.g., 4781). Returns every county/municipality designated under the declaration along with programs activated, 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. Input parameters: - `disaster_number` (integer, required): FEMA disaster number (e.g., 4781). Obtain from fema_search_disasters. Output parameters: - `declaration_date` (string): ISO 8601 date the declaration was signed. - `declaration_type` (string): Declaration type: DR (major disaster), EM (emergency), or FM (fire management). - `designated_area_count` (number): Total number of designated areas in this declaration. - `designated_areas` (array): All counties/municipalities designated for assistance under this declaration. - `disaster_number` (number): FEMA disaster number — use as the chain key for PA and housing assistance tools. - `hm_declared` (boolean): True when Hazard Mitigation grants were declared. - `ia_declared` (boolean): True when the Individuals and Households Program (IHP) was declared — indicates IA housing/personal grants are available. - `incident_begin_date` (string): ISO 8601 start date of the incident. Absent when not recorded. - `incident_end_date` (string): ISO 8601 end date of the incident. Absent for ongoing or unrecorded incidents. - `incident_type` (string): Type of incident (e.g., Flood, Hurricane, Severe Storm). - `pa_declared` (boolean): True when Public Assistance (infrastructure recovery grants) was declared. - `state` (string): Two-letter state/territory code. - `title` (string): Official declaration title (e.g., "SEVERE STORMS AND FLOODING"). ### `fema_get_public_assistance` (~198 tokens) Get FEMA Public Assistance Projects 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). Input parameters: - `county` (string): Filter by county name substring. - `disaster_number` (integer): FEMA disaster number to scope results to a single declaration. - `limit` (integer): Maximum number of projects to return (1–1000, default 100). - `offset` (integer): Pagination offset (default 0). - `state` (string): Two-letter state code to browse all PA projects for a state. Output parameters: - `notice` (string): Guidance when no results were found. - `projects` (array): Public assistance funded project records. - `returned_count` (number): Number of projects in this response. - `totalCount` (number): Total matching projects before pagination — exceeds returned_count when results were capped at the limit. - `total_count` (number): Total matching projects before pagination. ### `fema_get_housing_assistance` (~173 tokens) Get FEMA Housing Assistance Data Retrieve Individual Assistance (IA) housing data for a disaster by disaster number. Returns owner and/or renter breakdowns by county and ZIP code — valid registrations, total approved IHP amounts, repair/rental amounts, and inspection data. Use type to select owners, renters, or both (default). Use disaster_number from fema_search_disasters. Input parameters: - `disaster_number` (integer, required): FEMA disaster number. Obtain from fema_search_disasters. - `limit` (integer): Maximum records per dataset to return (default 100). - `offset` (integer): Pagination offset (default 0). - `state` (string): Two-letter state code to narrow results when a disaster spans multiple states. - `type` (string): Which housing assistance dataset to query: owners, renters, or both (default). Output parameters: - `notice` (string): Guidance when no results were found. - `owners` (array): Homeowner (HousingAssistanceOwners) records. Empty when type is "renters" or no owner data exists. - `owners_count` (number): Total owner records available before the per-dataset limit. - `renters` (array): Renter (HousingAssistanceRenters) records. Empty when type is "owners" or no renter data exists. - `renters_count` (number): Total renter records available before the per-dataset limit. - `totalCount` (number): Total owner + renter records available before the per-dataset limit — exceeds the returned count when either dataset was capped. ### `fema_search_nfip` (~392 tokens) Search NFIP Flood Insurance Claims Search National Flood Insurance Program (NFIP) claims data by state, county, ZIP code, and year range. Returns claim counts, amounts paid on building and contents, flood zones, and loss years. state is required — the full NFIP dataset is 2.7 million rows; unfiltered access is prohibited. When DataCanvas is enabled (CANVAS_PROVIDER_TYPE=duckdb) and results exceed the inline preview, the full result set is staged on a canvas for SQL aggregation via fema_dataframe_query. Use fema_dataframe_describe to inspect the staged table schema before writing SQL. Without canvas, results are returned inline up to the limit. Input parameters: - `canvas_id` (string): Optional canvas ID from a prior call. Omit to create a fresh canvas. The response returns the canvas_id to pass to fema_dataframe_query. - `county_code` (string): County code to narrow results within the state. Accepts the full 5-digit state+county FIPS (e.g., 48201 for Harris County TX) or the 3-digit county portion (e.g., 201) when state is provided — the se… - `limit` (integer): Maximum claim rows to return in the inline preview (1–10000, default 1000). When DataCanvas is enabled, the canvas stages the full matching result set regardless of this value. - `state` (string, required): Two-letter US state code (required). NFIP dataset is 2.7M rows — state filter is mandatory. - `year_from` (integer): Start year of loss, inclusive (e.g., 2020). - `year_to` (integer): End year of loss, inclusive (e.g., 2023). - `zip_code` (string): ZIP code to narrow results to a specific area (5-digit, e.g., 77002). Output parameters: - `canvas_id` (string): Canvas ID for the staged full result set. Pass to fema_dataframe_query and fema_dataframe_describe. Present only when spilled=true. - `canvas_table` (string): DuckDB table name on the canvas holding all fetched rows. Reference in SQL FROM clauses. Present when spilled=true. - `claims` (array): Inline preview of claim records (first N rows). Full dataset available via canvas_id when spilled=true. - `notice` (string): Guidance on canvas usage or result scope. - `returned_count` (number): Number of claim records in the inline preview. - `spilled` (boolean): True when the full result set was staged on DataCanvas; use canvas_id + fema_dataframe_query for SQL analysis. False when all results fit inline. - `total_count` (number): Total matching claims in the filtered dataset before the limit. - `truncated` (boolean): True when the canvas row cap (50,000) was reached before the full matching set was staged — the canvas holds a partial result. Apply tighter filters (county_code, zip_code, year range) to stage the c… ### `fema_dataframe_query` (~233 tokens) Query FEMA DataCanvas Table 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. Input parameters: - `canvas_id` (string, required): Canvas ID from the fema_search_nfip response (the canvas_id field). - `query` (string, required): SQL SELECT statement to run against the staged table. Use the table name from fema_dataframe_describe. Results are capped at the canvas row limit; append LIMIT/OFFSET to page through additional rows,… Output parameters: - `canvas_id` (string): Canvas ID that was queried — reuse for follow-up queries. - `cap` (number): The canvas row limit that was applied when the result was capped. - `notice` (string): Continuation guidance when capped — how to page the remainder with LIMIT/OFFSET. - `row_count` (number): Number of rows in this response (may be capped at the canvas row limit). - `rows` (array): Result rows from the query. May be capped at the canvas row limit — when the truncated enrichment field is set, page the remainder with LIMIT/OFFSET (see the notice guidance). - `shown` (number): Number of rows returned in this (capped) response. - `truncated` (boolean): True when the result was capped at the canvas row limit — more rows match than were returned. ### `fema_dataframe_describe` (~103 tokens) Describe FEMA DataCanvas Tables 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. Input parameters: - `canvas_id` (string, required): Canvas ID from the fema_search_nfip response. Output parameters: - `canvas_id` (string): Canvas ID that was described — pass to fema_dataframe_query. - `tables` (array): All tables and views available on this canvas. ### `fema_query_dataset` (~316 tokens) Query Any OpenFEMA Dataset Generic OData query against any OpenFEMA v2 dataset — the escape hatch for datasets the convenience tools do not cover (e.g., FimaNfipPolicies, IndividualAssistanceHousingRegistrantsLargeDisasters, FemaWebDeclarationAreas, PublicAssistanceApplicants). Accepts raw OData filter, select, orderby, and pagination parameters. For NFIP Policies, use propertyState (not state) as the state field — always include a county or ZIP filter to avoid timeout. The dataset name must match the exact OpenFEMA v2 entity name (case-sensitive, e.g., FimaNfipClaims). Unknown dataset names return an unknown_dataset error. Input parameters: - `dataset` (string, required): OpenFEMA v2 dataset entity name (case-sensitive, e.g., FimaNfipPolicies, FemaWebDeclarationAreas, PublicAssistanceApplicants). - `filter` (string): OData $filter expression (e.g., "state eq 'TX' and declarationDate ge '2024-01-01T00:00:00.000Z'"). String values in single quotes. - `limit` (integer): Maximum records to return (1–10000, default 100). - `offset` (integer): Pagination offset (default 0). - `orderby` (string): OData $orderby expression (e.g., "declarationDate desc"). - `select` (string): Comma-separated field names to return (e.g., "disasterNumber,state,declarationDate"). Output parameters: - `dataset` (string): The dataset that was queried. - `notice` (string): Guidance when no results were found. - `returned_count` (number): Number of records in this response. - `rows` (array): Records returned from the dataset. Field names depend on the queried dataset. - `totalCount` (number): Total matching records before pagination — exceeds returned_count when results were capped at the limit. - `total_count` (number): Total matching records before pagination. ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/cyanheads-fema-mcp-server/fema#diagnostics ## Score history - 2026-08-03: 68 - 2026-08-02: 67 - 2026-08-01: 67 - 2026-07-31: 67 - 2026-07-30: 65 - 2026-07-29: 64 - 2026-07-28: 64 - 2026-07-27: 63 - 2026-07-26: 62 ## Links - Remote endpoint: https://fema.caseyjhand.com/mcp - Repository: https://github.com/cyanheads/fema-mcp-server - Changelog RSS feed: https://verifymcp.io/servers/cyanheads-fema-mcp-server/fema/changelog.xml - Changelog JSON feed: https://verifymcp.io/servers/cyanheads-fema-mcp-server/fema/changelog.json - HTML version of this page: https://verifymcp.io/servers/cyanheads-fema-mcp-server/fema