Remote MCP · Endpoint

CrimeMetric MCP server

No. CrimeMetric answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://api.crimemetric.com/mcp

The last check completed an MCP handshake.

Registry name
com.crimemetric/crime-index
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
147 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Crime rates for any U.S. address: block-group indexes, city profiles and incident records.
Listing
From the official MCP registry (active).
Recent checks of CrimeMetric
CheckedResultHandshake
34 minutes agoHandshake completed147 ms
3 days agoHandshake completed158 ms
13 days agoHandshake completed219 ms
13 days agoHandshake completed156 ms
15 days agoHandshake completed121 ms
16 days agoHandshake completed217 ms
17 days agoHandshake completed134 ms
18 days agoHandshake completed140 ms
18 days agoHandshake completed125 ms
20 days agoHandshake completed112 ms
22 days agoHandshake completed98 ms
25 days agoHandshake completed125 ms
27 days agoHandshake completed119 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with CrimeMetric and makes no claim about it beyond what these checks measured.