_ registry / mcp http-sse · checked 6h ago

crime-mcp

https://crime-cz.vladinux.dev

Registry code: e711d0cf27513280

api record

An MCP server providing access to crime data from the Czech Republic. Data sourced directly from the Czech Police Presidium — available through 5 simple tools, no authentication required.

from a public catalogue that lists it, not from the operator

endpoint
https://crime-cz.vladinux.dev/mcp
protocol
http-sse ·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 crime-mcp live?
Yes — it answered the hub's last check (checked 6h ago). It answered 99% of checks over the last 30 days.
Is crime-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does crime-mcp have?
5 tools: search, getCityCount, getCrimeRelevance, getCrimeStates, getCrimeTypes.
Is crime-mcp 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
live
uptime, 30 days
99%

90 days 99.4%· all time 99.4%

latency
893ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 315 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • search czech crime records
  • count crimes per city in czechia
  • list crime types
takes → gives
text → data
tools
5 reads
_ 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 5 tools
3 open 2 never probed 3 of 5 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.

  • getCrimeRelevance reads open 25h ago

    List all crime relevance levels.

    mcp-tool

    {
      "type": "object"
    }
    arguments 3 lines
  • getCrimeStates reads open 25h ago

    List all crime states.

    mcp-tool

    {
      "type": "object"
    }
    arguments 3 lines
  • getCrimeTypes reads open 6h ago

    List all crime types.

    mcp-tool

    {
      "type": "object"
    }
    arguments 3 lines
  • search reads unknown 25h ago

    Search crimes by filter.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "mp": {
          "type": [
            "null",
            "boolean"
          ],
          "description": "Filter by municipal police (MP) involvement"
        },
        "lat": {
          "type": [
            "null",
            "number"
          ],
          "description": "GPS latitude of the search centre (requires lon and radius_meters)"
        },
        "lon": {
          "type": [
            "null",
            "number"
          ],
          "description": "GPS longitude of the search centre (requires lat and radius_meters)"
        },
        "city": {
          "type": [
            "null",
            "string"
          ],
          "description": "City name (exact match)"
        },
        "limit": {
          "type": "integer",
          "description": "Maximum number of records to return (0 = no limit)"
        },
        "state": {
          "type": [
            "null",
            "integer"
          ],
          "maximum": 32767,
          "minimum": -32768,
          "description": "Crime state code"
        },
        "types": {
          "type": [
            "null",
            "array"
          ],
          "items": {
            "type": "integer",
            "maximum": 32767,
            "minimum": -32768
          },
          "description": "Crime type codes – records with ANY matching type are returned (array overlap)"
        },
        "offset": {
          "type": "integer",
          "description": "Number of records to skip for pagination"
        },
        "region": {
          "type": [
            "null",
            "string"
          ],
          "description": "Region name (exact match)"
        },
        "street": {
          "type": [
            "null",
            "string"
          ],
          "description": "Street name (exact match)"
        },
        "suburb": {
          "type": [
            "null",
            "string"
          ],
          "description": "Suburb name (exact match)"
        },
        "columns": {
          "type": [
            "null",
            "array"
          ],
          "items": {
            "type": "string"
          },
          "description": "Columns to include in the result. Supported: mp,date,state,relevance,types,coordinates,region,city,suburb,state_district,city_district,street – omit for all"
        },
        "date_to": {
          "type": [
            "null",
            "string"
          ],
          "description": "Maximum crime date (inclusive)"
        },
        "order_by": {
          "type": "string",
          "description": "Sort order: date ASC, date DESC, region ASC, region DESC, city ASC, city DESC, relevance ASC, relevance DESC, state ASC, state DESC, distance ASC"
        },
        "date_from": {
          "type": [
            "null",
            "string"
          ],
          "description": "Minimum crime date (inclusive)"
        },
        "relevance": {
          "type": [
            "null",
            "integer"
          ],
          "maximum": 32767,
          "minimum": -32768,
          "description": "Relevance level code"
        },
        "city_district": {
          "type": [
            "null",
            "string"
          ],
          "description": "City district name (exact match)"
        },
        "radius_meters": {
          "type": [
            "null",
            "number"
          ],
          "description": "Search radius in metres around lat/lon, minimum 0"
        },
        "state_district": {
          "type": [
            "null",
            "string"
          ],
          "description": "State district name (exact match)"
        }
      },
      "additionalProperties": false
    }
    arguments 142 lines
  • getCityCount reads unknown 6h ago

    Number of crimes per city.

    mcp-tool

    {
      "type": "object",
      "required": [
        "limit"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "description": "Maximum number of cities to return (required, must be greater than 0)"
        },
        "order": {
          "type": [
            "null",
            "string"
          ],
          "description": "Sort order: ASC or DESC (default DESC)"
        },
        "sort_by": {
          "type": [
            "null",
            "string"
          ],
          "description": "Field to sort by: count (default) or city"
        }
      },
      "additionalProperties": false
    }
    arguments 27 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 e711d0cf27513280.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e711d0cf27513280/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/e711d0cf27513280/badge.svg)](https://brick.blue/agent/e711d0cf27513280?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
90%

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.