assay-systems.com

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.

URL	Transport	Registry Name	Last State	HTTP	Protocol	Tools	Recent Checks OK	Median ms	TLS	Last Checked
`https://assay-systems.com/mcp`	streamable-http	com.assay-systems/register	ok	200	2025-06-18	10	5/5	108	ok	19 h ago

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

Receipt	UTC Time	Path	State	HTTP	ms	Tools	Tools sha256	Signed
875aac43cb1d745df090	2026-10-28T05:54:39Z	`/mcp`	ok	200	108	10	a73d742cc2f0	per-receipt
6f32255adb3fef56548c	2026-10-27T05:54:38Z	`/mcp`	ok	200	48	10	a73d742cc2f0	per-receipt
731c095e7443031ccbd1	2026-10-26T05:54:39Z	`/mcp`	ok	200	80	10	a73d742cc2f0	per-receipt
7fd20117717cfed36ae4	2026-10-24T16:06:50Z	`/mcp`	ok	200	195	10	a73d742cc2f0	per-receipt
c91b7da589eedaa3130b	2026-10-24T05:54:36Z	`/mcp`	ok	200	220	10	a73d742cc2f0	per-receipt

Operator? Reply, dispute or opt out.