Skip to main content
Glama
pgang002

nfip-mcp-server

by pgang002
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to nfip-mcp-server

No user-submitted related servers found.

    Related Servers

    • fema-nfhl-mcp

      Revex-Agency
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that gives AI assistants direct access to the FEMA National Flood Hazard Layer (NFHL) for flood zone lookups, FIRM panel information, and flood map data in the United States.
      6
      5 npm
      MIT

    • fema-nfhl-mcp-server

      Graysonf12
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that queries FEMA's National Flood Hazard Layer (NFHL) for flood zone information, including flood zone codes, Base Flood Elevation, FIRM panel numbers, and identifies LOMRs/LOMAs from provided coordinates, enabling automated flood risk lookups.
      -

    • mcp-hazards

      jsuich
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that gives AI agents grounded access to US natural-hazard data — weather alerts, forecasts, earthquakes, and FEMA flood zones — from free, keyless US government APIs.
      MIT

    • census-mcp

      sohrab4748
      F
      license
      Not graded
      quality
      C
      maintenance
      Remote MCP server exposing US Census (ACS 5-year) and FEMA flood data. Works as a connector in both Claude and ChatGPT.
      -

    • fema-mcp-server

      cyanheads
      A
      license
      Not graded
      quality
      A
      maintenance
      Query FEMA disaster declarations, public assistance grants, housing aid, and NFIP flood insurance claims via MCP. Supports STDIO and Streamable HTTP.
      83 npm
      1
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing flood events, retrieving a single claim, searching claims by filters, and producing aggregate statistics. There is minimal overlap in functionality, and descriptions make the boundaries obvious.

    Naming Consistency4/5

    Three tools follow a consistent verb_noun pattern: list_flood_events, get_claim, and search_claims. claims_summary breaks the pattern by using a noun phrase, though it is still clear and readable.

    Tool Count5/5

    Four tools is a well-scoped size for a read-only NFIP claims data server. Each tool covers a distinct query need without redundancy or bloat.

    Completeness4/5

    The surface covers the core read-only workflows: enumeration, single-record lookup, filtered search, and aggregate statistics. Minor gaps exist, such as summary filtering by flood event or year, but these do not create dead ends for common use cases.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources