NYC Flooding (FloodNet)

NYC Flooding (FloodNet) MCP Connector for Claude

A+

Keyless NYC flooding data: DEP FloodNet street-flooding events with depths and durations, plus the flood sensor installation metadata — no API key.

5 tools Official Updated Oct 1, 2026 Official Vinkius Partner

New York City Department of Environmental Protection (DEP) FloodNet records, keyless.

What you can do

  • Flood events — street-flooding events recorded at FloodNet sensors since 2020: start/end times, max depth in inches, onset and drain durations and time spent above 4, 12 and 24 inches
  • Sensors by activity — the sensors with the most recorded flood events, ranked
  • Sensor lookup — the installation record for one sensor ID: name, install date, tidal influence, street, borough, geography fields and the lowest-point height delta
  • Sensor list — the installed sensors citywide (about 500), filtered by borough, NTA, ZIP or tidal influence
  • Events per sensor — all recorded events for one sensor with its deepest recorded flood

Who is this for

Flood-risk research, resilience planning, drainage engineering and journalism. Sensor IDs are slugs of the form "BK-richardson-st-n-11th-st-1x59w1" — list_flood_sensors shows installed IDs and names.

new-yorknycfloodfloodnetdepsensorsresiliencedurations

5 tools expose this connector's capabilities to your AI agent.

flood_events_by_sensor

The response includes the event count and the deepest recorded flood at that sensor. sensor_id is the full ID slug; lookup_flood_sensor shows installed IDs and their names. Street-flooding events for one FloodNet sensor

list_flood_sensors

About 500 sensors are installed; filter by borough, NTA or ZIP. List FloodNet flood sensor locations

lookup_flood_sensor

g. "Brooklyn"), ZIP, community board, council district, census tract, NTA, the lowest-point height delta in inches and coordinates. sensor_id is the full ID slug — list_flood_sensors shows installed IDs and names. Look up a FloodNet flood sensor installation

search_flood_events

Events have been recorded since 2020 and the dataset is small (a few thousand events) — no date window is applied by default; bound the result with on/after and on/before if needed. Sensor names are of the form "Q - Beach 84 St" (borough-letter prefix + intersection); sensor IDs are slugs (e.g. "BX-ditmars-st-hunter-ave-1kwrk0"). The sensor_name filter is an exact match against the stored name. Search NYC street-flooding events (FloodNet)

top_flood_sensors

Each row is one sensor name with its event count. Use it to find the most flood-prone monitored locations, then drill in with flood_events_by_sensor or lookup_flood_sensor. FloodNet sensors with the most recorded flood events

See how to talk to your AI agent using NYC Flooding (FloodNet).

Which NYC locations have had the most recorded street floods?

top_flood_sensors returns the sensors ranked by the number of recorded flood events; lookup_flood_sensor then shows where a sensor is and flood_events_by_sensor its recorded events.

How deep did the flood get at the Ditmars St / Hunter Ave sensor?

flood_events_by_sensor with the sensor ID returns every recorded event for that sensor plus its deepest recorded flood; search_flood_events with sensor_name: "Ditmars" finds the events across sensors at that intersection.

Show me the most recent street-flooding events citywide.

search_flood_events with no filters returns the events newest first (max depth in inches, onset and drain durations included); add after ("YYYY-MM-DD") to narrow to a period.

No. NYC Open Data serves all public datasets anonymously over its SODA API (data.cityofnewyork.us). This MCP defines no credentials and needs nothing configured.

Related Connectors