# NYC Emergency Response AI Agent Connect

> NYC Emergency Response MCP provides your AI client with direct access to New York City emergency records. You can pull EMS and fire dispatches, locate FDNY firehouses and alarm boxes, analyze historical response times dating back to 2009, and access the FDNY line-of-duty deaths memorial. It works with any MCP-compatible client like Claude, Cursor, or Windsurf.

## Overview
- **Category:** government-public-data
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_642i7zJUz3CuEcflL2GxaCj9uEQ3exQkAQx7iLtT/ai-agent-connect
- **Tags:** new-york, nyc, fdny, ems, fire, dispatch, response-time, emergency

## Description

You can now query NYC emergency response data using your preferred AI agent. This MCP pulls directly from NYC Open Data to give you granular details on fire and EMS activity across the five boroughs. If you need to analyze how quickly ambulances are responding to calls in Manhattan versus Brooklyn, you can pull monthly averages or specific incident dispatches. You can also map out the physical infrastructure of the FDNY by locating firehouses and in-service alarm boxes. For researchers or journalists looking at historical trends, the data includes response times going back to 2009 and a memorial list of line-of-duty deaths. Because Vinkius hosts this MCP, you don't have to manage API keys or complex data connections yourself. Just connect your client and start asking questions about NYC's emergency response patterns.

## Tools

### get_fdny_response_times
This tool retrieves average FDNY response times for a specific month and borough. It provides historical data dating back to 2009.

### list_alarm_boxes
Use this to find the locations of in-service FDNY alarm boxes. You can filter the results by borough, zip code, or box type.

### list_fdny_duty_deaths
This tool accesses the FDNY memorial dataset. You can filter the list of line-of-duty deaths by specific units or ranks.

### list_fdny_firehouses
This tool provides the locations of FDNY firehouses. Results can be filtered by borough and include addresses and coordinates.

### search_ems_dispatches
This tool searches through FDNY EMS incident dispatches. It includes call types, severity, and response times for a specific date window.

### search_fire_company_incidents
Use this to find specific incidents handled by FDNY fire companies. You can filter by borough, fire box, or incident type.

### search_fire_dispatches
This tool pulls FDNY fire incident dispatches. It provides classification, alarm levels, and response times for recent incidents.

## Prompt Examples

**Prompt:** 
```
How many fire dispatches happened in the Bronx in the last 30 days?
```

**Response:** 
```
The search_fire_dispatches tool returns the number of incidents in the Bronx with their classification and response times.
```

**Prompt:** 
```
What was the average FDNY response time in June 2025?
```

**Response:** 
```
The get_fdny_response_times tool provides the average response time in seconds and incident counts for June 2025.
```

**Prompt:** 
```
List the FDNY firehouses in Staten Island.
```

**Response:** 
```
The list_fdny_firehouses tool returns all stations in Staten Island, including their addresses, postcodes, and coordinates.
```

## Capabilities

### Dispatch Analysis
Your agent can query specific EMS and fire incident details including severity and response times.

### Infrastructure Mapping
The AI can locate physical FDNY assets like firehouses and alarm boxes using coordinates and addresses.

### Historical Trends
Your client can pull monthly response time averages dating back to 2009 for long-term analysis.

### Memorial Access
The agent can retrieve specific records from the FDNY line-of-duty deaths memorial list.

## Use Cases

### Response Time Audits
Compare average response times across different boroughs to identify service gaps.

### Resource Mapping
Identify the proximity of firehouses and alarm boxes to specific neighborhoods or high-risk zones.

### Incident Investigation
Look up specific EMS or fire dispatches to understand the nature of recent emergency calls.

### Public Safety Reporting
Gather data on fire company incidents to write reports on city-wide emergency trends.

## Benefits

- No API keys required to access NYC Open Data.
- Vinkius handles all hosting and maintenance of the connection.
- Direct access to historical data back to 2009.
- Works with any MCP-compatible client you already use.

## How It Works

Connecting to this data is a single-step process through the Vinkius platform.

1. Connect your MCP-compatible client to Vinkius.
2. The MCP becomes available as a set of tools in your AI interface.
3. Ask your agent a question about NYC emergency data.
4. The agent calls the appropriate tool to fetch data from NYC Open Data.
5. Your agent processes the raw data and gives you a direct answer.

## Frequently Asked Questions

**Do I need an API key for NYC Open Data?**
No. This MCP provides keyless access to the data through Vinkius.

**How recent is the dispatch data?**
There is a data lag of a few months, so the most recent months may appear empty.

**How far back does the response time data go?**
You can access historical monthly response time averages dating back to 2009.

**Which AI clients can I use with this MCP?**
You can use any MCP-compatible client, including Claude, Cursor, Windsurf, and VS Code.

**Can I filter EMS dispatches by borough?**
Yes, you can filter by borough, but the borough names must be uppercase in the dispatch dataset.

**Do I need an API key?**
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.

**How current are the dispatch datasets?**
Dispatch rows lag a few months behind real time (the newest rows stop around mid-2026), so both dispatch search tools apply a 90-day window by default. Monthly response-time statistics are historical, back to 2009, and are stored as "YYYY/MM" — the year_month parameter accepts "YYYY-MM" and normalizes it.

**Which borough values should I use?**
Dispatch data stores boroughs in UPPERCASE — "BRONX", "BROOKLYN", "MANHATTAN", "QUEENS", "RICHMOND / STATEN ISLAND" (Staten Island), UNKNOWN. Location lists (firehouses, alarm boxes, fire-company incidents) use title case — "Staten Island", "Manhattan". Each tool states its case in its description.