Yes — it answered the hub's last check (checked 22h ago). It answered 100% of checks over the last 30 days.

What tools does crime-data have?

5 tools: crime_incidents, crime_compare, crime_stats, crime_score, crime_coverage.

Is crime-data 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.

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

crime-data

https://crimedata.dev

Registry code: 746a8a29b6b58c4a

api record

Police-reported incidents, stats, comparisons and safety scores for 11 US cities.

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

endpoint: https://crimedata.dev/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 crime-data live?: Yes — it answered the hub's last check (checked 22h ago). It answered 100% of checks over the last 30 days.
Is crime-data free to use?: Not measured yet.
What tools does crime-data have?: 5 tools: crime_incidents, crime_compare, crime_stats, crime_score, crime_coverage.
Is crime-data 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

100%

90 days 100%· all time 100%

latency

253ms

last good check

priced tools

of 5 tools

_ answered our checks, 90 days 2 checks · signed record

2026-11-08 21:58 unknown → live

_ 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

through this hub

calls served

successful

paid through this hub

0 USDC

what callers paid

_ what it can do 5 tools

5 never probed 0 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.

crime_incidents unknown never probed

Recent police-reported incidents near a point in covered US cities, newest first.

mcp-tool

{
  "type": "object",
  "properties": {
    "to": {
      "type": "string",
      "description": "ISO date, exclusive"
    },
    "lat": {
      "type": "number",
      "description": "Latitude (WGS84); or pass address instead"
    },
    "lon": {
      "type": "number",
      "description": "Longitude (WGS84)"
    },
    "from": {
      "type": "string",
      "description": "ISO date, inclusive; the free server covers the last 180 days"
    },
    "limit": {
      "type": "number",
      "description": "Max rows, 1-50 (default 50)"
    },
    "address": {
      "type": "string",
      "description": "US street address, used instead of lat and lon"
    },
    "category": {
      "enum": [
        "homicide",
        "sexual_offense",
        "robbery",
        "assault",
        "burglary",
        "vehicle_theft",
        "theft_from_vehicle",
        "theft",
        "fraud",
        "vandalism",
        "weapons",
        "drugs",
        "dui",
        "trespass",
        "harassment",
        "public_order",
        "traffic",
        "non_criminal",
        "other"
      ],
      "type": "string"
    },
    "radius_m": {
      "type": "number",
      "description": "Search radius in metres, 1-1000 (default 500)"
    }
  }
}

arguments 57 lines

crime_compare unknown never probed

Compare incident stats (by category, violent vs property, hour, weekday, 90-day trend) for 2-5 points with the same radius.

mcp-tool

{
  "type": "object",
  "required": [
    "points"
  ],
  "properties": {
    "to": {
      "type": "string",
      "description": "ISO date, exclusive"
    },
    "from": {
      "type": "string",
      "description": "ISO date, inclusive; the free server covers the last 180 days"
    },
    "points": {
      "type": "string",
      "description": "lat,lon;lat,lon (2-5 points)"
    },
    "category": {
      "enum": [
        "homicide",
        "sexual_offense",
        "robbery",
        "assault",
        "burglary",
        "vehicle_theft",
        "theft_from_vehicle",
        "theft",
        "fraud",
        "vandalism",
        "weapons",
        "drugs",
        "dui",
        "trespass",
        "harassment",
        "public_order",
        "traffic",
        "non_criminal",
        "other"
      ],
      "type": "string"
    },
    "radius_m": {
      "type": "number",
      "description": "Search radius in metres, 1-1000 (default 500)"
    }
  }
}

arguments 48 lines

crime_stats unknown 22h ago

Incident counts by category and by month near a point.

mcp-tool

{
  "type": "object",
  "properties": {
    "to": {
      "type": "string",
      "description": "ISO date, exclusive"
    },
    "lat": {
      "type": "number",
      "description": "Latitude (WGS84); or pass address instead"
    },
    "lon": {
      "type": "number",
      "description": "Longitude (WGS84)"
    },
    "from": {
      "type": "string",
      "description": "ISO date, inclusive; the free server covers the last 180 days"
    },
    "address": {
      "type": "string",
      "description": "US street address, used instead of lat and lon"
    },
    "category": {
      "enum": [
        "homicide",
        "sexual_offense",
        "robbery",
        "assault",
        "burglary",
        "vehicle_theft",
        "theft_from_vehicle",
        "theft",
        "fraud",
        "vandalism",
        "weapons",
        "drugs",
        "dui",
        "trespass",
        "harassment",
        "public_order",
        "traffic",
        "non_criminal",
        "other"
      ],
      "type": "string"
    },
    "radius_m": {
      "type": "number",
      "description": "Search radius in metres, 1-1000 (default 500)"
    }
  }
}

arguments 53 lines

crime_score unknown never probed
Safety score 0-100 (higher = fewer incidents) and A-F grade for a point: incident density percentile against sampled occupied-area cells of the city (same radius) over its last 12 months. Not a prediction of personal risk; not comparable across cities. Outside covered cities it returns coverage "city_fallback": the city's FBI city-wide violent/property rates per 100k and national percentiles, no grade. May include a "tract" block: 2020 Census tract population and incidents per 1,000 estimated residents in the radius per year (tract residents only, so commercial and nightlife areas overstate risk).

mcp-tool
{ "type": "object", "properties": { "lat": { "type": "number", "description": "Latitude (WGS84); or pass address instead" }, "lon": { "type": "number", "description": "Longitude (WGS84)" }, "address": { "type": "string", "description": "US street address, used instead of lat and lon" }, "radius_m": { "type": "number", "description": "Search radius in metres, 1-1000 (default 500)" } } }
arguments 21 lines
crime_coverage unknown never probed
Covered cities, data source, licence and freshness.

mcp-tool
{ "type": "object", "properties": {} }
arguments 4 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.

Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
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.
Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 746a8a29b6b58c4a.

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

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/746a8a29b6b58c4a/badge.svg)](https://brick.blue/agent/746a8a29b6b58c4a?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

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.