Fema Nfhl
NPM · @PIPEWORX/MCP-FEMA-NFHL · 2 COMPONENTS
FEMA National Flood Hazard Layer (NFHL) MCP
Available components
Last scanned (11 hours ago)
Scores higher than 72% of npm servers
Category Maps and Location
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-fema-nfhl). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 631 tokens (~210/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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 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.
- 1 Nov 26 +1
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Stability: unverified → 0.10 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 79
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-fema-nfhl@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-fema-nfhl |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-fema-nfhl/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3635941713 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:64d5151e7a99b100ef20cc3eeadca129331f361c935be6d2b4241de1eaeb25f043b81b3f251081275592bfc01f7cafad5f033b8f25daf773c88a5c5d0 |
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 →
nfhl_flood_zone_at_point ~193
AUTHORITATIVE flood-zone lookup: given a latitude/longitude, return the effective FEMA FIRM flood zone for that spot — the zone code (A, AE, AH, AO, VE, X, D), its subtype, whether it is in a Special Flood Hazard Area, the static base flood elevation, and the governing DFIRM id — plus nearby base flood elevation lines. PREFER OVER WEB SEARCH for "is this address in a flood zone" or "does this property need flood insurance". Distinguishes "outside the floodplain" from "never mapped", which a plain empty result does not.
| Name | Type | Req | Description |
|---|---|---|---|
| include_bfe | boolean | – | Also return base flood elevation lines within ~150 m of the point. Default true. |
| latitude | number | yes | Latitude in WGS84 decimal degrees |
| longitude | number | yes | Longitude in WGS84 decimal degrees (negative in the US) |
No output schema declared.
No examples provided.
nfhl_layers ~102
List every layer in the FEMA National Flood Hazard Layer MapServer with its id, name and geometry type, plus a plain-English guide to the layers that matter (flood hazard zones, base flood elevations, LOMRs, LOMAs, FIRM panels, levees, NFHL availability). Call this before nfhl_query.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | Case-insensitive substring to filter layer names, e.g. "flood", "levee" |
No output schema declared.
No examples provided.
nfhl_query ~278
Query any layer of the FEMA National Flood Hazard Layer with an ArcGIS WHERE clause and optional bounding box — flood hazard zones, base flood elevations, floodways, LOMRs and LOMAs, FIRM panels with their effective dates, levees, cross-sections, political jurisdictions. Use for area questions ("every floodway polygon in this county", "LOMRs issued on this DFIRM"). Layer ids come from nfhl_layers.
| Name | Type | Req | Description |
|---|---|---|---|
| bbox | string | – | Optional "xmin,ymin,xmax,ymax" WGS84 envelope to restrict the query (longitude first) |
| layer_id | number|string | yes | NFHL layer id — 28 is Flood Hazard Zones, 16 Base Flood Elevations, 1 LOMRs, 3 FIRM Panels |
| limit | number | – | Max rows, 1-500 (default 50) |
| offset | number | – | Row offset for paging |
| order_by | string | – | Comma-separated order-by fields |
| out_fields | string | – | Comma-separated field names, or "*" for all (default "*") |
| return_geometry | boolean | – | Include geometry. Default false — flood polygons are very large. |
| where | string | – | ArcGIS WHERE clause, default "1=1". Id fields are strings: DFIRM_ID='48201C'. |
No output schema declared.
No examples provided.
How do I install the Fema Nfhl MCP server?
Fema Nfhl runs locally as an npm package, launched with npx -y @pipeworx/mcp-fema-nfhl. 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-fema-nfhl
claude mcp add pipeworx-io-fema-nfhl -- npx -y @pipeworx/mcp-fema-nfhl
What is the Fema Nfhl MCP server?
Fema Nfhl is an MCP server listed in the public MCP registry as io.github.pipeworx-io/fema-nfhl. FEMA National Flood Hazard Layer (NFHL) MCP. This page covers its npm package (@pipeworx/mcp-fema-nfhl).
Is the Fema Nfhl MCP server safe to use?
Fema Nfhl scores 82 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 Fema Nfhl MCP server expose?
Fema Nfhl exposes 3 tools: nfhl_flood_zone_at_point, nfhl_query, nfhl_layers. Their descriptions and schemas cost roughly 573 tokens of context every time the server is loaded.
Is the Fema Nfhl MCP server still maintained?
Fema Nfhl 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 Fema Nfhl MCP server under?
Fema Nfhl declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.