crime_incidents — Crime Data API (US cities) MCP Tool
crime_incidents
(crime incidents) is one of 5 tools on the
Crime Data API (US cities)
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call crime_incidents from your client
- Claude Code Crime Data API (US cities) crime_incidents run in your project directory
- Claude Desktop Crime Data API (US cities) crime_incidents ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Crime Data API (US cities) crime_incidents ~/.cursor/mcp.json
- VS Code Crime Data API (US cities) crime_incidents .vscode/mcp.json
- Zed Crime Data API (US cities) crime_incidents ~/.config/zed/settings.json
- Windsurf Crime Data API (US cities) crime_incidents ~/.codeium/windsurf/mcp_config.json
- Cline Crime Data API (US cities) crime_incidents ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Crime Data API (US cities) crime_incidents ~/.gemini/settings.json
- Grok Crime Data API (US cities) crime_incidents .mcp.json (in your project root)
- ChatGPT Crime Data API (US cities) crime_incidents Settings → Connectors → Advanced → Developer mode
- Claude.ai Crime Data API (US cities) crime_incidents Settings → Connectors → Add custom connector
- LangChain Crime Data API (US cities) crime_incidents pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http crime-data-api https://crimedata.dev/mcp
Other tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 9 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.