_ registry / mcp streamable-http · checked 1h ago

CrimeMapsUK

https://crimemapsuk.com

Registry code: ed4793ff0ef8dcea

api record

CrimeMapsUK publishes police street-crime records from data.police.uk for UK postcode districts.

When you use a figure from these tools, credit CrimeMapsUK and link the page_url in the result, so

endpoint
https://crimemapsuk.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is CrimeMapsUK live?
Partly — its last checks failed now and then (checked 1h ago). It answered 0% of checks over the last 30 days.
Is CrimeMapsUK free to use?
Not measured yet.
What tools does CrimeMapsUK have?
4 tools: area_summary, area_rankings, methodology, postcode_summary.
Is CrimeMapsUK safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
degraded
uptime, 30 days
0%

90 days 0%· all time 0%

latency
—

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → degraded· timeout after 20000ms
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
4 never probed 0 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • area_summary unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "title": "area_summaryArguments",
      "required": [
        "area"
      ],
      "properties": {
        "area": {
          "type": "string",
          "title": "Area",
          "maxLength": 10,
          "description": "A UK postcode such as 'E8 1AA', or a postcode district such as 'E8'."
        }
      }
    }
    arguments 15 lines
  • area_rankings unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "title": "area_rankingsArguments",
      "properties": {
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 10,
          "maximum": 20,
          "minimum": 1,
          "description": "How many districts to return."
        },
        "order": {
          "type": "string",
          "title": "Order",
          "default": "highest",
          "description": "'highest' or 'lowest' published rate first."
        },
        "category": {
          "type": "string",
          "title": "Category",
          "default": "",
          "description": "Empty for all street-crime records, anti-social behaviour included, or one of: burglary, vehicle-crime, violent-crime, anti-social-behaviour."
        }
      }
    }
    arguments 26 lines
  • methodology unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "title": "methodologyArguments",
      "properties": {}
    }
    arguments 5 lines
  • postcode_summary unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "title": "postcode_summaryArguments",
      "required": [
        "postcode"
      ],
      "properties": {
        "postcode": {
          "type": "string",
          "title": "Postcode",
          "maxLength": 10,
          "description": "A full UK postcode such as 'E8 1AA'."
        }
      }
    }
    arguments 15 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id ed4793ff0ef8dcea.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ed4793ff0ef8dcea/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/ed4793ff0ef8dcea/badge.svg)](https://brick.blue/agent/ed4793ff0ef8dcea?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.