Uk Police Crime Mcp Server

Overview

Monthly street-level crime, police outcomes, and stop and search records from data.police.uk, plus the neighbourhood policing teams behind them. Coverage is the 43 territorial forces of England and Wales and the Police Service of Northern Ireland, plus British Transport Police, whose station records are the only coverage of Scotland. Search by point, polygon, map point, neighbourhood, or whole force; follow a crime's outcome history; find who polices a place. Runs as a stdio process or a local Streamable HTTP server. No API key required.

Tools

Capability reference

ukcrime_list_reference _tool

• topic: forces, categories, availability, or neighbourhoods (needs force); name_contains filters forces and neighbourhoods by name, and month narrows availability to one row
• availability returns latest_month, earliest_month, and which forces published stop and search each month; with force, the months that force did and did not publish
• forces adds British Transport Police (btp) and each force's known coverage gaps; errors are typed (force_required, unknown_force, invalid_filter)

ukcrime_search_crimes _tool

• area: point (lat, lng; a 1-mile radius), polygon (3–2,500 vertices), location (location_id), neighbourhood (force + neighbourhood_id), or force_unplaced (force: the crimes it could not place); optional month (default: latest published) and category (default: every category)
• Returns total, by_category, by_outcome, up to 10 top_locations, and a page of crimes, each with the persistent_id that ukcrime_get_crime_outcomes takes; limit defaults to 25 (max 200), and next_offset continues
• Failures carry a typed reason, such as month_not_published, unknown_category, or area_too_large

ukcrime_search_outcomes _tool

• Same areas as ukcrime_search_crimes except force_unplaced; month is when the outcome was recorded, and category counts only outcomes for crimes in that category
• Returns total, unfiltered_total, by_outcome (code, name, count), by_crime_month, and a page of outcomes, each with its crime; limit defaults to 20 (max 200)
• Police outcomes only: court results are not published, and the result says when a force publishes no outcomes

ukcrime_get_crime_outcomes _tool

• persistent_ids: 1–25 64-character ids from ukcrime_search_crimes or ukcrime_search_outcomes; anti-social behaviour records carry none
• Each crime comes back with every outcome, oldest first; history_available: false marks a crime with no published history
• Ids data.police.uk does not hold land in not_found, failed lookups in failed, so one bad id never fails the batch

ukcrime_search_stops _tool

• area: point, polygon, location, neighbourhood, or force (every stop the force published, placed or not); up to 8 filters on type, self_defined_ethnicity, officer_defined_ethnicity, outcome, object_of_search, legislation, age_range, or gender
• Returns total, unfiltered_total, unplaced, force_published, a breakdown per filterable field, and a page of stops; limit defaults to 15 (max 200)
• Filters narrow the breakdowns and the page together, so filtering one field and reading another's breakdown is a cross-tab

ukcrime_find_neighbourhood _tool

• Look up by lat + lng or by force + neighbourhood_id; include picks priorities, team, events (the default three) and boundary
• Returns the force, the team's description, contact channels and stations, current priorities, up to 10 upcoming events (events_total counts all), and the boundary as a polygon string the search tools accept
• Team entries carry only each officer's rank and name, as forces publish them; biographies and personal contact details are dropped by design. A point outside coverage returns found: false with guidance

Features

Built on @cyanheads/mcp-ts-core: stdio and Streamable HTTP transports, pluggable auth (none / jwt / oauth), swappable storage (in-memory, filesystem, Supabase, Cloudflare KV/R2/D1), structured logging with optional OpenTelemetry tracing.

data.police.uk-specific:

• Every location is an anonymised map point covering at least eight addresses, never the place a crime or stop happened; outputs label it that way
• Validates locally what the upstream would silently widen: unknown categories, months outside the window, misspelled force ids, and area fields the chosen area does not use
• Omitting month searches the latest published month and echoes it; coverage gaps per force are dated and named in each result's notice
• One process-wide request pacer under data.police.uk's rate limit, with retries and in-process caches for reference data and area responses

Agent-friendly output:

• Every response carries the Open Government Licence attribution and a data_note on what the records can and cannot say
• Counts come with the page: totals and breakdowns cover every matched record, while limit / offset / next_offset page the rows
• Typed failure reasons with a recovery hint, and a notice that separates "no data published" from "nothing happened"

Known limitations

• Only the latest 36 months are served; longer trends need the bulk archive at data.police.uk, which this server does not read
• Greater Manchester Police publishes no crime, outcome or stop and search data; searches there return only other forces' or British Transport Police records
• Northern Ireland has no outcomes and no stop and search, and every crime other than anti-social behaviour carries the placeholder outcome Under investigation
• Scotland is covered only by British Transport Police station records
• Court outcomes from June 2019 onward are not published
• data.police.uk can refuse an area holding more than about 10,000 records, whatever the category, and the point radius is fixed at one mile; dense city centres need polygons smaller than a borough
• The API says which forces published stop and search each month, but not which supplied crime data, so a force that skipped a month shows as a thin or empty area; a low or zero count can mean missing data
• Many stops carry a blank outcome, reported as (not recorded); stop datetime is UTC while months follow UK local time

Getting started

Add the following to your MCP client configuration file.

{  "mcpServers": {    "uk-police-crime-mcp-server": {      "type": "stdio",      "command": "bunx",      "args": ["@cyanheads/uk-police-crime-mcp-server@latest"],      "env": {        "MCP_TRANSPORT_TYPE": "stdio",        "MCP_LOG_LEVEL": "info"      }    }  }}

Or with npx (no Bun required):

{  "mcpServers": {    "uk-police-crime-mcp-server": {      "type": "stdio",      "command": "npx",      "args": ["-y", "@cyanheads/uk-police-crime-mcp-server@latest"],      "env": {        "MCP_TRANSPORT_TYPE": "stdio",        "MCP_LOG_LEVEL": "info"      }    }  }}

Or with Docker:

{  "mcpServers": {    "uk-police-crime-mcp-server": {      "type": "stdio",      "command": "docker",      "args": ["run", "-i", "--rm", "-e", "MCP_TRANSPORT_TYPE=stdio", "ghcr.io/cyanheads/uk-police-crime-mcp-server:latest"]    }  }}

For Streamable HTTP, set the transport and start the server:

MCP_TRANSPORT_TYPE=http MCP_HTTP_PORT=3010 bun run start:http# Server listens at http://localhost:3010/mcp

Prerequisites

• Bun v1.4.0 or higher (or Node.js v24+).
• No API key: data.police.uk is open and keyless.

Installation

1. Clone the repository:

git clone https://github.com/cyanheads/uk-police-crime-mcp-server.git

2. Navigate into the directory:

cd uk-police-crime-mcp-server

3. Install dependencies:

bun install

Configuration

The server reads no environment variables of its own. data.police.uk allows 15 requests a second with a burst of 30 per client IP; the server paces every request process-wide under that limit, so a hosted deployment shares one budget behind its egress IP, and requests queue for their turn.

See .env.example for the common framework overrides.

Running the server

Local development

• Build and run the production version:

  sh

  # One-time buildbun run rebuild
  # Run the built serverbun run start:http# orbun run start:stdio

• Run checks and tests:

  sh

  bun run devcheck  # Lints, formats, type-checks, and morebun run test      # Runs the test suite

Project structure

Development guide

See CLAUDE.md for development guidelines and architectural rules. The short version:

• Handlers throw, framework catches — no try/catch in tool logic
• Use ctx.log for logging, ctx.state for storage
• Register new tools and resources in the createApp() arrays in src/index.ts
• Wrap external API calls: validate raw → normalize to domain type → return output schema; never fabricate missing fields

Contributing

Issues are welcome. Run checks and tests before submitting:

bun run devcheckbun run test

License

This project is licensed under the Apache 2.0 License. See the LICENSE file for details.

Data: Contains public sector information licensed under the Open Government Licence v3.0. Source: data.police.uk. Every tool response carries this attribution; storing, caching and redistributing the data are permitted with it. This project is independent of the Home Office, data.police.uk and the police forces.