Flood Zone Lookup (FEMA Flood Map) MCP
REMOTE · FLOOD-ZONE-LOOKUP-FEMA-FLOOD-MAP-MCP.LIPMICHAL.WORKERS.DEV
FEMA flood zone for any US address: zone, base flood elevation, FIRM panel, insurance meaning.
Available components
Last scanned (19 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Maps and Location
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 666 tokens (~222/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 Management13
- Stability observed for 4 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 (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
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.
- 19 Nov 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.
- 18 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 Nov 26 66
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 21 Nov 2026 · Probed https://flood-zone-lookup-fema-flood-map-mcp.lipmichal.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lipmichal.workers.dev | CN=WE1,O=Google Trust Services,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ebf145553d5751d20e0d3cd51e3d7a94 |
| SANs: lipmichal.workers.dev, *.lipmichal.workers.dev | ||||||
| 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 insecure
Validation of flood-zone-lookup-fema-flood-map-mcp.lipmichal.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| workers.dev. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://flood-zone-lookup-fema-flood-map-mcp.lipmichal.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://flood-zone-lookup-fema-flood-map-mcp.lipmichal.workers.dev/mcp | Inconclusive | 405 |
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 →
flood_zone_explain What a flood zone means ~152
What a FEMA flood zone code means and its flood insurance rules: A, AE, AH, AO, AR, A99, V, VE, shaded X (old B, 0.2% annual chance), unshaded X (old C), D. Omit the zone for the full list. No address needed.
| Name | Type | Req | Description |
|---|---|---|---|
| subtype | string | – | Optional zone subtype from a map, e.g. "FLOODWAY" or "0.2 PCT ANNUAL CHANCE FLOOD HAZARD". |
| zone | string | – | Zone code, e.g. AE, VE, X, "shaded X", B, C, D. Omit for every zone. |
No output schema declared.
No examples provided.
flood_zone_lookup Flood zone lookup by address ~189
The FEMA flood zone at a US street address or latitude/longitude, from the National Flood Hazard Layer: zone code (A, AE, AH, AO, V, VE, shaded or unshaded X, D), whether it is in the Special Flood Hazard Area (high risk, 1% annual chance), the base flood elevation or flood depth, the FIRM panel number and effective date, Letters of Map Revision, the NFIP community, whether flood insurance is federally required, and a link to the official FEMA map.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | US street address with city and state or ZIP, e.g. "701 Bourbon St, New Orleans, LA 70116". "lat,lon" also works. |
| latitude | number | – | Latitude in decimal degrees, instead of an address. |
| longitude | number | – | Longitude in decimal degrees (negative west), with latitude. |
No output schema declared.
No examples provided.
flood_zone_nearby Flood zones near an address ~193
High-risk (A and V zones, including floodways), moderate-risk (shaded X, 0.2% annual chance) and undetermined (D) FEMA flood zones within a radius of a US address or point (default 500 m, up to 2000 m), with the straight-line distance to the nearest of each and their base flood elevations. Answers "how far is this house from the floodplain".
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | US street address with city and state or ZIP, e.g. "701 Bourbon St, New Orleans, LA 70116". "lat,lon" also works. |
| latitude | number | – | Latitude in decimal degrees, instead of an address. |
| longitude | number | – | Longitude in decimal degrees (negative west), with latitude. |
| radius_m | number | – | Search radius in metres, 50 to 2000. Default 500. |
No output schema declared.
No examples provided.
How do I install the Flood Zone Lookup (FEMA Flood Map) MCP server?
Flood Zone Lookup (FEMA Flood Map) MCP is a hosted endpoint at https://flood-zone-lookup-fema-flood-map-mcp.lipmichal.workers.dev/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 · flood-zone-lookup-fema-flood-map-mcp.lipmichal.workers.dev
claude mcp add --transport http theluckystrike-flood-zone-lookup-fema-flood-map- 'https://flood-zone-lookup-fema-flood-map-mcp.lipmichal.workers.dev/mcp'
What is the Flood Zone Lookup (FEMA Flood Map) MCP server?
Flood Zone Lookup (FEMA Flood Map) MCP is listed in the public MCP registry as io.github.theluckystrike/flood-zone-lookup-fema-flood-map-m…. FEMA flood zone for any US address: zone, base flood elevation, FIRM panel, insurance meaning. This page covers its hosted endpoint (https://flood-zone-lookup-fema-flood-map-mcp.lipmichal.workers.dev/mcp).
Is the Flood Zone Lookup (FEMA Flood Map) MCP server safe to use?
Flood Zone Lookup (FEMA Flood Map) MCP scores 67 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 Flood Zone Lookup (FEMA Flood Map) MCP server expose?
Flood Zone Lookup (FEMA Flood Map) MCP exposes 3 tools: flood_zone_lookup, flood_zone_nearby, flood_zone_explain. Their descriptions and schemas cost roughly 534 tokens of context every time the server is loaded.
Does the Flood Zone Lookup (FEMA Flood Map) MCP server require authentication?
No. We connected to Flood Zone Lookup (FEMA Flood Map) MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Flood Zone Lookup (FEMA Flood Map) MCP server still maintained?
Flood Zone Lookup (FEMA Flood Map) MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Flood Zone Lookup (FEMA Flood Map) MCP server?
VerifyMCP ran 12 checks on Flood Zone Lookup (FEMA Flood Map) MCP, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Flood Zone Lookup (FEMA Flood Map) MCP: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.