Openfema
NPM · @PIPEWORX/MCP-OPENFEMA · 2 COMPONENTS
OpenFEMA MCP — US Federal Emergency Management Agency open data.
Available components
Last scanned (11 hours ago)
Scores higher than 69% of npm servers
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-openfema). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 873 tokens (~291/item across 3 items; 3 tools + 0 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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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 0
- Security disclosure: unverified → fail ▼ functional
- 4 Nov 26 +1
- Security disclosure: fail → unverified ▼ functional
- Package version: 0.2.0 → 0.2.1 functional
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 78
First indexed and scored.
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 · Analysed npm/@pipeworx/mcp-openfema@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-openfema |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-openfema/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3685096970 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:fa0975eb054a4e367f69ffc9b2d15b2208fb783d05ccdc08437c5e1af0e1e129e733023e942acd4355a16328f1a559fdf47d380fd4a6afac7f80c07b3 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
disaster_declarations ~528
Look up and COUNT US federal disaster declarations (FEMA DisasterDeclarationsSummaries). Filters: state (2-letter), incidentType (e.g. 'Fire', 'Flood', 'Hurricane', 'Severe Storm'), declarationType ('DR' major disaster, 'EM' emergency, 'FM' fire management), year (fyDeclared, the federal FISCAL year), and since/until for a real calendar date range — use since/until for questions like 'in the past year', which a fiscal year does not answer. Counts are DISTINCT DISASTERS by default, not table rows: FEMA publishes one row per disaster per designated county, so Hurricane Harvey is ~60 rows for Texas but one declaration. Pass designatedArea or grain:'area' for county-level rows. Returns the most recent first. The response echoes `filters_applied` plus a `note`: declarationType/incidentType/state/designatedArea each narrow the total to a SUBSET (e.g. declarationType:'DR' excludes 'EM' and 'FM') — for an across-all-types/all-states total, call again WITHOUT that filter rather than treating one filtered call's total as the grand total; for a true breakdown, call once per value and sum the totals yourself.
| Name | Type | Req | Description |
|---|---|---|---|
| declarationType | string | – | 'DR' (major disaster), 'EM' (emergency), or 'FM' (fire management). |
| designatedArea | string | – | Filter to a designated area, e.g. 'Harris (County)'. Implies county-level grain. |
| grain | string | – | 'disaster' (default) = one record per declaration; 'area' = one record per designated county. |
| incidentType | string | – | Incident type, e.g. 'Fire', 'Flood', 'Hurricane', 'Severe Storm'. |
| limit | integer | – | Max records (default 50, max 1000). |
| orderby | string | – | OData $orderby, default 'declarationDate desc'. Live-API path only. |
| since | string | – | Only declarations on/after this date — ISO 'YYYY-MM-DD'. Use with until for windows like 'the past year'. |
| state | string | – | 2-letter state/territory code, e.g. 'CA', 'TX'. |
| until | string | – | Only declarations on/before this date — ISO 'YYYY-MM-DD'. |
| year | integer | – | Federal FISCAL year declared (fyDeclared), e.g. 2024. For a calendar window use since/until instead. |
No output schema declared.
No examples provided.
list_datasets ~54
List the OpenFEMA datasets this pack knows about, with their entity name, current version, and a description. Also documents the OData filter syntax and response shape. Call this first to discover what query_dataset can target.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
query_dataset ~237
Generic OData query against any OpenFEMA dataset. Specify the entity name (and optionally version; defaults to the verified current version) plus OData params: filter, select, orderby, top, skip. Use list_datasets to see available entities/versions and the filter syntax. Returns { metadata, records }.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | yes | Dataset entity name, e.g. 'PublicAssistanceFundedProjectsDetails'. |
| filter | string | – | OData $filter, e.g. "state eq 'TX' and fyDeclared eq 2023". |
| orderby | string | – | OData $orderby, e.g. 'declarationDate desc'. |
| select | string | – | Comma-separated $select fields, e.g. "disasterNumber,state,incidentType". |
| skip | integer | – | Records to skip ($skip) for paging. |
| top | integer | – | Max records ($top, default 50, max 1000). |
| version | string | – | Path version like 'v1'/'v2'/'v4'. Optional — defaults to the verified current version for known entities. |
No output schema declared.
No examples provided.
How do I install the Openfema MCP server?
Openfema runs locally as an npm package, launched with npx -y @pipeworx/mcp-openfema. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-openfema
claude mcp add pipeworx-io-openfema -- npx -y @pipeworx/mcp-openfema
What is the Openfema MCP server?
Openfema is an MCP server listed in the public MCP registry as io.github.pipeworx-io/openfema. OpenFEMA MCP, US Federal Emergency Management Agency open data. This page covers its npm package (@pipeworx/mcp-openfema).
Is the Openfema MCP server safe to use?
Openfema scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Openfema MCP server expose?
Openfema exposes 3 tools: disaster_declarations, query_dataset, list_datasets. Their descriptions and schemas cost roughly 819 tokens of context every time the server is loaded.
Is the Openfema MCP server still maintained?
Openfema 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.
What licence is the Openfema MCP server under?
Openfema declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Openfema MCP server?
VerifyMCP ran 16 checks on Openfema, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.