CrimeMapsUK
REMOTE · CRIMEMAPSUK.COM
Published UK police street-crime figures by postcode district, with a page link and citation.
Available components
Last scanned (17 hours ago)
Scores higher than 74% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 739 tokens (~184/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
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.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 21 Nov 2026 · Probed https://crimemapsuk.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=crimemapsuk.com | CN=YE2,O=Let's Encrypt,C=US | 1 Nov 2026 | 30 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5bbba51bc6ccfd9a317c000be8c5ed870d2 |
| SANs: crimemapsuk.com, www.crimemapsuk.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of crimemapsuk.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| crimemapsuk.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://crimemapsuk.com/mcp | Verified | 200 | |
| http (plaintext) | http://crimemapsuk.com/mcp | HTTPS enforced | 301 | https://crimemapsuk.com/mcp |
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 →
area_rankings Rank postcode districts by published crime rate ~136
Postcode districts in England and Wales ranked by published street-crime records, anti-social behaviour included, per 1,000 Census 2021 residents. Each row has the rate, the counts behind it, and its page_url. These are published rates, not safety ratings.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Empty for all street-crime records, anti-social behaviour included, or one of: burglary, vehicle-crime, violent-crime, anti-social-behaviour. |
| limit | integer | – | How many districts to return. |
| order | string | – | 'highest' or 'lowest' published rate first. |
Structured output declared, but exposes no named fields.
No examples provided.
area_summary Crime figures for a postcode district ~152
Published street-crime figures for a UK postcode district. Given a postcode, answers for its whole postcode district (E8 for E8 1AA), never for the exact postcode. Returns the district's last 12 published months: total, monthly series, categories, and the covering police force, with page_url, a citation, and the attribution. For a full postcode that is not known to be outside England and Wales, the result also has free_report_url, the free result page for the 0.5 km around it.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | yes | A UK postcode such as 'E8 1AA', or a postcode district such as 'E8'. |
Structured output declared, but exposes no named fields.
No examples provided.
methodology How CrimeMapsUK builds its figures ~48
Notes on how CrimeMapsUK builds its figures: coverage, approximate locations, postcode assignment, rates, rankings, outcomes, and how to cite a page, with the methodology page_url.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
postcode_summary Crime counts around a postcode ~145
Published street-crime records in the fixed 0.5 km circle around a postcode, over the 12 months up to the latest published month: the total, the month window, the coverage state, and the largest category, with page_url, a citation, and free_report_url. Called with a CrimeMapsUK API key, it returns every category's count. The free figures come from a snapshot up to six hours old and keyed ones from one up to 15 minutes old, so they can differ briefly after new data is published.
| Name | Type | Req | Description |
|---|---|---|---|
| postcode | string | yes | A full UK postcode such as 'E8 1AA'. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the CrimeMapsUK MCP server?
CrimeMapsUK is a hosted endpoint at https://crimemapsuk.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · crimemapsuk.com
claude mcp add --transport http com-crimemapsuk-crime-data 'https://crimemapsuk.com/mcp'
What is the CrimeMapsUK MCP server?
CrimeMapsUK is an MCP server listed in the public MCP registry as com.crimemapsuk/crime-data. Published UK police street-crime figures by postcode district, with a page link and citation. This page covers its hosted endpoint (https://crimemapsuk.com/mcp).
Is the CrimeMapsUK MCP server safe to use?
CrimeMapsUK scores 79 out of 100 on VerifyMCP. 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 CrimeMapsUK MCP server expose?
CrimeMapsUK exposes 4 tools: area_summary, area_rankings, methodology, postcode_summary. Their descriptions and schemas cost roughly 481 tokens of context every time the server is loaded.
Does the CrimeMapsUK MCP server require authentication?
No. We connected to CrimeMapsUK without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CrimeMapsUK MCP server still maintained?
CrimeMapsUK is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the CrimeMapsUK MCP server?
VerifyMCP ran 13 checks on CrimeMapsUK, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.