Connect Nyc Emergency Response Fdny Ems to your AI

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Get direct access to FDNY and EMS dispatch records.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

How Vinkius works: one connection, every tool, in any AI
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Complete set · 7 capabilities

The complete NYC Open Data capability set.

These are the exact actions your AI can choose when you ask it to work with NYC Open Data.

Capability set01 / 02

01-04

4 capabilities in this set.

Part of 7 available through NYC Open Data.

  1. 01

    Get fdny response times

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

  2. 02

    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.

  3. 03

    List fdny duty deaths

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

  4. 04

    List fdny firehouses

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

Capability set02 / 02

05-07

3 capabilities in this set.

Part of 7 available through NYC Open Data.

  1. 05

    Search ems dispatches

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

  2. 06

    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.

  3. 07

    Search fire dispatches

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

One connector, every AI

NYC Open Data works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put NYC Open Data to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 7 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of NYC Open Data, so you can see the experience inside your AI.

It does not authenticate your account with NYC Open Data. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

NYC Open Data Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_642i7zJUz3CuEcflL2GxaCj9uEQ3exQkAQx7iLtT/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — NYC Open Data capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "nyc-emergency-response-fdny-ems-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_642i7zJUz3CuEcflL2GxaCj9uEQ3exQkAQx7iLtT/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? How to give Claude access to NYC Open Data

See all the AI clients this connector works with ↑

Who it's for

Built for the work NYC Open Data owners hand off.

This MCP is built for professionals who need to query NYC public safety data without writing custom scrapers or managing API connections.

  • 01

    Emergency Services Researchers

    They use the MCP to pull historical response time data for academic or policy studies.

  • 02

    Journalists

    They use the capability to investigate local emergency response patterns or incident trends.

  • 03

    Urban Safety Planners

    They use dispatch and station location data to inform city safety and resource allocation.

FAQ

Questions NYC Open Data owners ask.

  • 01

    Do I need an API key for NYC Open Data?

    No. This MCP provides keyless access to the data through Vinkius.

  • 02

    How recent is the dispatch data?

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

  • 03

    How far back does the response time data go?

    You can access historical monthly response time averages dating back to 2009.

  • 04

    Which AI clients can I use with this MCP?

    You can use any MCP-compatible client, including Claude, Cursor, Windsurf, and VS Code.

  • 05

    Can I filter EMS dispatches by borough?

    Yes, you can filter by borough, but the borough names must be uppercase in the dispatch dataset.

  • 06

    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.

  • 07

    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 capabilities 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.

  • 08

    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 capability states its case in its description.

Connect NYC Open Data to Claude, Cursor, ChatGPT & more