Ukpolice
NPM · @PIPEWORX/MCP-UKPOLICE · 2 COMPONENTS
UK Police MCP — wraps the UK Police Data API (free, no auth) https://data.police.uk/api
Available components
Last scanned (8 hours ago)
Scores higher than 38% of npm servers
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-ukpolice). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 359 tokens (~119/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (15)
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 1.1.0 → 1.1.1 functional
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 81
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Analysed npm/@pipeworx/mcp-ukpolice@1.1.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-ukpolice |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-ukpolice/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3706365135 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:404978990691fd1038cf0f758e8355e6425f4b0ad93102ffd20e62f88f8db8c02fa341b889b87e04510f2862aaec6c96bad77921892a1b55d6480ef96 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_crimes ~196
Get street-level crimes reported near a latitude/longitude in England, Wales or Northern Ireland, from the official police open data. Returns each crime's category, street, month and outcome status, plus the month the figures are actually for. Answers "what crime was reported near <place>" and "how much burglary is there around these coordinates". Omit `date` for the latest published month — the feed runs about two months in arrears, and a month that has not been published yet is reported as such rather than as an absence of crime.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Month in YYYY-MM form, e.g. "2026-05". Omit for the latest published month. Data lags roughly two months; if the requested month is not published yet, the most recent available month is returned and… |
| lat | number | yes | Latitude of the location |
| lng | number | yes | Longitude of the location |
No output schema declared.
No examples provided.
get_forces ~28
List all police forces in England, Wales, and Northern Ireland. Returns force ID and name.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_outcomes ~80
Get outcomes for crimes at a location for a given month. Returns outcome category and date for each crime.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Month to query in YYYY-MM format (e.g. "2024-01"). Defaults to latest available. |
| lat | number | yes | Latitude of the location |
| lng | number | yes | Longitude of the location |
No output schema declared.
No examples provided.
How do I install the Ukpolice MCP server?
Ukpolice runs locally as an npm package, launched with npx -y @pipeworx/mcp-ukpolice. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-ukpolice
claude mcp add pipeworx-io-ukpolice -- npx -y @pipeworx/mcp-ukpolice
What is the Ukpolice MCP server?
Ukpolice is an MCP server listed in the public MCP registry as io.github.pipeworx-io/ukpolice. UK Police MCP, wraps the UK Police Data API (free, no auth) https://data.police.uk/api. This page covers its npm package (@pipeworx/mcp-ukpolice).
Is the Ukpolice MCP server safe to use?
Ukpolice scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Ukpolice MCP server expose?
Ukpolice exposes 3 tools: get_crimes, get_forces, get_outcomes. Their descriptions and schemas cost roughly 304 tokens of context every time the server is loaded.
Is the Ukpolice MCP server still maintained?
Ukpolice is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Ukpolice MCP server under?
Ukpolice declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Ukpolice MCP server?
VerifyMCP ran 15 checks on Ukpolice, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about Ukpolice: Malware scan. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.