US Flood Zone & Property Risk (FEMA, NOAA, USGS, Census) MCP server
com.thestackunderflow/datum-propertythestackunderflow.comstreamable-httpv0.2.0Scanned
FEMA flood zone, hazard history and demographics for any US address, with sources on every answer.
6 tools: 6 change things.
- Reads private data · 0
- Reads text others write · 6
- Can send data out · 0
- 2 findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
6 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the US Flood Zone & Property Risk (FEMA, NOAA, USGS, Census) MCP server can do
The US Flood Zone & Property Risk (FEMA, NOAA, USGS, Census) MCP server is published by thestackunderflow.com, a domain the MCP Registry verified. It has 6 tools. It can create or change data (6 tools: address_profile, admin_areas, area_demographics, census_geocode and 2 more), but cannot delete data. None of its tools only reads.
6 tools bring in text other people can write (address_profile, admin_areas, area_demographics and 3 more).
The fixed checks matched 2 findings (long-description). Each one comes with the text it matched.
Last scanned Nov 14, 2026, version 0.2.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 6Claude Code: ask
address_profileOne-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 d…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
admin_areasState and county for a coordinate, with Census GEOIDs.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
area_demographicsPopulation and median household income for the county containing a point, from American Community Survey 5-year estimates.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
census_geocodeFree.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
flood_zoneFEMA 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 floo…Reads text others write1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description is 2,069 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...c. Every response includes a sources[] array naming the data origin and licence."
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
hazard_historyNatural-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 repo…Reads text others write1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description is 2,231 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...c. Every response includes a sources[] array naming the data origin and licence."
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write6
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:48 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The operation was aborted due to timeout
Posture changes
- Nov 20, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 6 to 0
- Protocol version: 2025-06-18 to none
Findings
Matches of fixed checks, with the text they matched.
- Infoflood_zone
The description is 2,069 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...c. Every response includes a sources[] array naming the data origin and licence."
- Infohazard_history
The description is 2,231 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...c. Every response includes a sources[] array naming the data origin and licence."
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 2 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 6 to 0
- Protocol version: 2025-06-18 to none
Install
Pinned to version 0.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http datum-property https://mcp.thestackunderflow.com/mcp/propertyclaude mcp add --transport http datum-property https://mcp.thestackunderflow.com/mcp/propertyRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__datum-property__address_profile",
"mcp__datum-property__admin_areas",
"mcp__datum-property__area_demographics",
"mcp__datum-property__census_geocode",
"mcp__datum-property__flood_zone",
"mcp__datum-property__hazard_history"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as datum-property. Review it before you use it.
Capability tags behind 6 rules
- mcp__datum-property__address_profile untrusted-input
- mcp__datum-property__admin_areas untrusted-input
- mcp__datum-property__area_demographics untrusted-input
- mcp__datum-property__census_geocode untrusted-input
- mcp__datum-property__flood_zone untrusted-input
- mcp__datum-property__hazard_history untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.thestackunderflow/datum-property/verify?hash=9f73c457e5985a4e9ad07f154161b2de1f5deb19e923ffcc19e76f3d39a648d6" | jq -e '.changed == false'Pinned hash 9f73c457e598, from Nov 14, 2026, 14:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.thestackunderflow/datum-property/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.thestackunderflow/datum-property)Source: MCP Registry. Synced Oct 21, 2026, 18:06 UTC.
US Flood Zone & Property Risk (FEMA, NOAA, USGS, Census) MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the US Flood Zone & Property Risk (FEMA, NOAA, USGS, Census) MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 6 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the US Flood Zone & Property Risk (FEMA, NOAA, USGS, Census) MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the US Flood Zone & Property Risk (FEMA, NOAA, USGS, Census) MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the US Flood Zone & Property Risk (FEMA, NOAA, USGS, Census) MCP server have?
- 6 tools: 6 write. address_profile, admin_areas, area_demographics, census_geocode, flood_zone and hazard_history.
Does the US Flood Zone & Property Risk (FEMA, NOAA, USGS, Census) MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the US Flood Zone & Property Risk (FEMA, NOAA, USGS, Census) MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the US Flood Zone & Property Risk (FEMA, NOAA, USGS, Census) MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.