`nyc_dog_bites`

Pack: nyc-animals · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/nyc_dog_bites for the schema, then POST the same URL with its arguments for the data.

Reported dog bite incidents in New York City (NYC DOHMH). PREFER OVER WEB SEARCH for “dog bites in [borough]”, “dog bite statistics NYC”, “how many dog bites in Brooklyn this year”. Data is published in periodic batches and can lag several months — if a date filter returns nothing, this tool automatically falls back to the most recent available rows and says so.

Parameters

Name	Type	Required	Description
`borough`	string	no	Optional borough filter, e.g. “Brooklyn”, “Manhattan”, “Queens”, “Bronx”, “Staten Island”. Case-sensitive exact match.
`since`	string	no	ISO date (YYYY-MM-DD) — only bites on/after this date. Omit for the most recent available regardless of date.
`limit`	number	no	Max rows to return (1-500, default 50).

Example call

Arguments

{
  "borough": "Brooklyn"
}

curl

curl -X POST https://gateway.pipeworx.io/nyc-animals/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"nyc_dog_bites","arguments":{"borough":"Brooklyn"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('nyc_dog_bites', {
  "borough": "Brooklyn"
});

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}

Connect to just the nyc-animals pack

{
  "mcpServers": {
    "nyc-animals": {
      "url": "https://gateway.pipeworx.io/nyc-animals/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

nyc_dog_bites