Skip to main content
Glama

US Flood Zone & Property Risk (FEMA, NOAA, USGS, Census)

Server Details

FEMA flood zone, hazard history and demographics for any US address, with sources on every answer.

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
ChatGPT
–
Claude
–

TDQS

A4.5/5.0

Scored across 6 tools

Disambiguation4/5

The aggregate address_profile intentionally overlaps flood_zone, hazard_history and area_demographics, but every description explicitly states when to use the one-call report versus the single-fact tools. admin_areas, census_geocode and the specific tools have clearly distinct roles. Only the deliberate aggregate overlap keeps this from a 5.

Naming Consistency4/5

All names are lowercase snake_case, which is consistent. Most are noun phrases (flood_zone, hazard_history, admin_areas) while census_geocode uses a provider+verb form, a minor deviation that stays readable.

Tool Count5/5

Six tools is well-scoped for a property-risk domain: one geocoder, one boundary resolver, one demographics reader, two hazard readers and one aggregate. Each earns its place with no redundancy.

Completeness4/5

The surface covers the full screening lifecycle: address-to-point, administrative resolution, demographics, flood zone, multi-source hazard history, and a combined report. Minor gaps exist (no reverse-only lookup or elevation-certificate-level detail), but core workflows have no dead ends.

Available Tools

6 tools
address_profileAddress ProfileA
Read-onlyIdempotent
Inspect

One-call US property report for an address or coordinate: FEMA flood zone (SFHA, base flood elevation, FIRM panel), county demographics, and 10-year hazard history (FEMA disaster declarations, NOAA storm events, USGS earthquakes), with a plain-English summary and a source for every part.

Everything the property pack knows about one US address, in one call:

  • location: the point used, and the state, county and census tract. - flood: the FEMA flood zone at the point, exactly as flood_zone returns it.

  • demographics: county population and median household income (ACS 5-year estimates).

  • hazards: counts of FEMA declarations (and major disasters) and their types, NOAA storm events, deaths and reported damage, and USGS earthquakes within 100 km (since 1950), over the last ten years.

Every section has a status. The flood zone is required: if FEMA's map cannot be read, no report is produced and the call is not charged. Any other section that fails is marked unavailable and the report still returns. Informational screening only; see the disclaimer in the answer.

When to use: Use when the user wants an overview of a US property or address (flood risk, neighbourhood, disaster history) rather than one specific fact. One call replaces flood_zone, hazard_history and area_demographics; quote the summary and keep the disclaimer.

Billed as property.address_profile at 8c.

Every response includes a sources[] array naming the data origin and licence.

Inputs: lat, lon, address. Returns: flood, hazards, summary, location, +2 more

admin_areasAdmin AreasA
Read-onlyIdempotent
Inspect

State and county for a coordinate, with Census GEOIDs. Free - answered from boundaries the platform ingests and holds, with no provider call.

Point-in-polygon against Census TIGER/Line boundaries (§22.2). Returns the administrative areas containing the point, most specific first, each with the GEOID that every other census dataset is keyed by. Tract, ZCTA and place follow when those layers are ingested. A coordinate exactly on a county line is genuinely in both counties and both are returned - the alternative is an address falling into a gap. Take the first if you need one answer.

When to use: Use to turn a coordinate into a county or state GEOID before asking for any census-keyed data. Free, so there is no reason to guess a FIPS code.

This tool is free and does not consume plan credits.

Every response includes a sources[] array naming the data origin and licence.

Inputs: lat (required), lon (required). Returns: areas

area_demographicsArea DemographicsA
Read-onlyIdempotent
Inspect

Population and median household income for the county containing a point, from American Community Survey 5-year estimates.

Composes two ingested datasets (§22.2): TIGER/Line resolves the coordinate to a county GEOID, then the ACS layer is read by that key. Pass geoid directly to skip the boundary lookup. Values are survey ESTIMATES with margins of error, not counts, and a suppressed estimate is returned as null rather than filled in. The release that produced them is in dataset_version and in each metric's period.

When to use: Use for "how many people live in this area" or "what is the median income there". Give a coordinate, or a county GEOID from admin_areas.

Billed as property.area_demographics at 1c.

Every response includes a sources[] array naming the data origin and licence.

Inputs: lat, lon, geoid. Returns: area, metrics

census_geocodeCensus GeocodeA
Read-onlyIdempotent
Inspect

Free. Turns a US street address into a latitude/longitude plus the state, county and census tract it is in (with GEOIDs), using the U.S. Census Bureau geocoder. Use it first, then pass the point to the paid property tools.

One-line address to point, with the Census Bureau's own match: the matched address, ZIP code, coordinates and the state, county and tract containing them. An address the geocoder cannot place is reported as not found, never guessed. US addresses only; PO boxes and rural routes often do not match.

When to use: Use when you have a US street address and need its coordinates, county or census tract. Free. flood_zone, hazard_history and address_profile also accept the address directly, so call this only when the user wants the location itself.

This tool is free and does not consume plan credits.

Every response includes a sources[] array naming the data origin and licence.

Inputs: address (required). Returns: areas, address

flood_zoneFlood ZoneA
Read-onlyIdempotent
Inspect

FEMA flood zone for a US address or coordinate: zone (A, AE, VE, X ...), whether it is in the Special Flood Hazard Area (where lenders generally require flood insurance), base flood elevation with its datum, FIRM panel and effective date, NFIP community, and any Letter of Map Revision. Live from FEMA's National Flood Hazard Layer, with a plain-English summary.

Reads FEMA's National Flood Hazard Layer at one point, live, so the answer is FEMA's current effective map: the flood zone and subtype, a risk level (high, coastal high, moderate, minimal, undetermined, unmapped), whether the point is in the Special Flood Hazard Area or a floodway, the base flood elevation in its unit and vertical datum (null, never 0, where no single elevation is published: it then varies along the flooding source and is read from the FIRM profile), the FIRM panel and its effective date, the NFIP community, any Letter of Map Revision in effect, and notes where FEMA's own flags disagree with the zone. Answers are cached for up to 30 days. An address is geocoded with the Census Bureau geocoder first, and the point used is returned; an ambiguous address is refused with its candidates. A point FEMA has not mapped digitally is reported as unmapped, not as low risk, and a point with no FEMA data at all (outside the US) is not found and not charged. On a zone boundary the higher-risk zone is reported and the others listed. Informational screening only: not an official flood zone determination (Standard Flood Hazard Determination Form), not an elevation certificate, and not insurance or lending advice. Every answer carries that disclaimer.

When to use: Use when asked whether a US property is in a flood zone, needs flood insurance, is in the SFHA or a floodway, or for its FEMA zone, base flood elevation or FIRM panel. Quote the summary and keep the disclaimer with it. For flood plus everything else about an address in one call, use address_profile.

Billed as property.flood_zone at 2c.

Every response includes a sources[] array naming the data origin and licence.

Inputs: lat, lon, address. Returns: flood, point, summary, disclaimer

hazard_historyHazard HistoryA
Read-onlyIdempotent
Inspect

Natural-hazard history for a US county or address: FEMA declarations (major disasters, emergencies and fire management, by type, with links), NOAA storm events with deaths and reported property damage by type and year, and USGS earthquakes within 100 km since 1950. One call, each source reported apart.

Three federal sources, fetched together:

  • FEMA declarations for the county since 1 January of the first year: the total (major disasters, emergencies and fire management), major disasters alone, count by incident type, and the declarations themselves with FEMA ids and links. Statewide declarations are included.

  • NOAA Storm Events for the county: events, deaths, injuries and reported property and crop damage (nominal dollars; unreported damage counts as 0, so it is a floor), by type and by year, plus the worst events. Events NOAA records for a forecast zone covering only this county (most heat and winter-storm deaths) count as the county's own; a zone covering several counties is counted, but its casualties and damage are reported apart in zone_based, because they are shared. The current year is incomplete; NOAA can trail by months.

  • USGS earthquakes of magnitude 2.5 or more within 100 km of the point since 1950: the count and the five largest. This needs a point, so it is skipped when only a county GEOID is given.

Each section has its own status; if one source is down the others still answer. If neither FEMA nor NOAA can answer, the call fails and is not charged. Connecticut's planning regions (since 2022) are not yet matched to the old counties FEMA and NOAA still use, so they are not answered; the old county GEOIDs (09001-09015) work. A GEOID that is not a county is not found. A geoid is used only when no address or coordinate is given.

When to use: Use for "has this area had floods, hurricanes or earthquakes", disaster declarations, storm damage history, or natural-hazard due diligence for a US property or county. For the flood zone at a property use flood_zone; for everything about an address in one call use address_profile.

Billed as property.hazard_history at 2c.

Every response includes a sources[] array naming the data origin and licence.

Inputs: lat, lon, geoid, years, +1 more. Returns: point, years, county, storms, +3 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Assesses natural hazard exposure (flood, wildfire, earthquake, coastal proximity) for a single US property address using only free, keyless public data.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables location-aware emergency preparedness planning by providing FEMA hazard risk profiles, disaster declaration history, and combined community context.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      ollect comprehensive environmental data from 80+ US federal sources (FEMA, EPA, USGS, NOAA, NRCS, USFWS, DOE, DOT, CDC, Census) for any US location. One tool returns flood zones, soils, wetlands, rainfall, water quality, contamination, seismic risk, infrastructure, ecology, energy, and demographics.
      3
      32 npm
      7
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources