# 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.

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `flood-zone-lookup-fema-flood-map-mcp.lipmichal.workers.dev`: 67/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-flood-zone-lookup-fema-flood-map-mcp/flood-zone-lookup-fema-flood-map-mcp.md), [page](https://verifymcp.io/servers/theluckystrike-flood-zone-lookup-fema-flood-map-mcp/flood-zone-lookup-fema-flood-map-mcp)

## Channel facts

- Endpoint: `https://flood-zone-lookup-fema-flood-map-mcp.lipmichal.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http theluckystrike-flood-zone-lookup-fema-flood-map- 'https://flood-zone-lookup-fema-flood-map-mcp.lipmichal.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-flood-zone-lookup-fema-flood-map-": {
      "url": "https://flood-zone-lookup-fema-flood-map-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-flood-zone-lookup-fema-flood-map-": {
      "type": "http",
      "url": "https://flood-zone-lookup-fema-flood-map-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-flood-zone-lookup-fema-flood-map-]
url = "https://flood-zone-lookup-fema-flood-map-mcp.lipmichal.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-flood-zone-lookup-fema-flood-map-": {
      "type": "remote",
      "url": "https://flood-zone-lookup-fema-flood-map-mcp.lipmichal.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-flood-zone-lookup-fema-flood-map- --url 'https://flood-zone-lookup-fema-flood-map-mcp.lipmichal.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-flood-zone-lookup-fema-flood-map-:
    url: "https://flood-zone-lookup-fema-flood-map-mcp.lipmichal.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-flood-zone-lookup-fema-flood-map-": {
      "Transport": "http",
      "Url": "https://flood-zone-lookup-fema-flood-map-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-flood-zone-lookup-fema-flood-map- -t streamable-http -u 'https://flood-zone-lookup-fema-flood-map-mcp.lipmichal.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-flood-zone-lookup-fema-flood-map-": {
      "type": "http",
      "url": "https://flood-zone-lookup-fema-flood-map-mcp.lipmichal.workers.dev/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-11-19 (score 67, +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-11-18 (score 66, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-17 (score 66)

First indexed and scored.

## MCP tools (3)

### `flood_zone_lookup` (~189 tokens)

Flood zone lookup by address

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.

Input parameters:

- `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.

### `flood_zone_nearby` (~193 tokens)

Flood zones near an address

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".

Input parameters:

- `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.

### `flood_zone_explain` (~152 tokens)

What a flood zone means

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.

Input parameters:

- `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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-flood-zone-lookup-fema-flood-map-mcp/flood-zone-lookup-fema-flood-map-mcp#diagnostics

## Score history

- 2026-11-21: 67
- 2026-11-20: 67
- 2026-11-19: 67
- 2026-11-18: 66
- 2026-11-17: 66

## Common questions

### 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.

## Links

- Remote endpoint: https://flood-zone-lookup-fema-flood-map-mcp.lipmichal.workers.dev/mcp
- Repository: https://github.com/theluckystrike/flood-zone-lookup-fema-flood-map-mcp
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-flood-zone-lookup-fema-flood-map-mcp/flood-zone-lookup-fema-flood-map-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-flood-zone-lookup-fema-flood-map-mcp/flood-zone-lookup-fema-flood-map-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theluckystrike-flood-zone-lookup-fema-flood-map-mcp/flood-zone-lookup-fema-flood-map-mcp.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-flood-zone-lookup-fema-flood-map-mcp/flood-zone-lookup-fema-flood-map-mcp
