BotsRated

cityalert.live

Raw data · 1 server URL from the Official MCP Registry · simple view

Login-free handshake (initialize → tools/list; unpaid tools/call only on priced tools, to read the payment request; never paid, no credentials): automatic unauthenticated MCP handshake (initialize + tools/list), aiming for about once a day per listed server while we are still working through the registry; priority tier (host looked up via BotsRated preflight/check/report, or also a covered x402 seller, in the last 7 days) about every 6 hours; servers with no MCP answer for 7 days about every 4 days. States are factual: ok (initialize and tools/list answered), auth_required (HTTP 401/403: the server wants a login), handshake_failed (HTTP answer without a valid MCP result), unreachable (no HTTP answer), blocked (not contacted: the URL, a redirect or its DNS points to a private, local or otherwise non-public address, or to another host, which our rules don't allow). Names and descriptions are the registry's text; we don't check it.

URLTransportRegistry NameLast StateHTTPProtocolToolsRecent Checks OKMedian msTLSLast Checked
https://cityalert.live/.well-known/mcpstreamable-httplive.cityalert/cityalertok2002025-06-1885/6587ok20 h ago

MCP Check Receipts (Newest First, Up To 10 Per Server)

ReceiptUTC TimePathStateHTTPmsToolsTools sha256Signed
e4cb0c211902136059922026-10-28T19:09:38Z/.well-known/mcpok2005428034e86e46cc5per-receipt
bb733e7875261b7684222026-10-27T19:09:38Z/.well-known/mcpok20042648034e86e46cc5per-receipt
dac9995699439e5add9b2026-10-26T19:09:39Z/.well-known/mcpok2005878034e86e46cc5per-receipt
4ca41ee71c3c8df49aa82026-10-25T19:09:39Z/.well-known/mcphandshake_failed429255per-receipt
1f311719247efa7818802026-10-24T11:18:44Z/.well-known/mcpok2002618034e86e46cc5per-receipt
f83f0053e9dc759a73bb2026-10-23T19:09:37Z/.well-known/mcpok20025548034e86e46cc5per-receipt

Operator? Reply, dispute or opt out.