registry-mcp.remote-mcp.com

Remote MCP server host. 2 server URLs from the Official MCP Registry. Each is checked with a login-free MCP handshake (initialize, then tools/list; unpaid tools/call only on tools that state a price, to read the payment request; nothing is paid, no credentials are sent): 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 unsafe address, or to another host, which our safety rules don't allow). Server names and descriptions are copied from the registry (untrusted text). Friendlier view: /s/registry-mcp.remote-mcp.com.

URL	Transport	Registry Name	Last State	HTTP	Protocol	Tools	Recent Checks OK	Median ms	TLS	Last Checked
`https://registry-mcp.remote-mcp.com`	streamable-http	com.remote-mcp/registry-mcp	ok	200	2025-03-26	2	–	756	ok	2 h ago
`https://registry-mcp.remote-mcp.com/sse`	sse	com.remote-mcp/registry-mcp	ok	200	2025-03-26	2	–	408	ok	17 h ago

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

Receipt	UTC Time	Path	State	HTTP	ms	Tools	Tools sha256	Signed
474584e2fed98215b60c	2026-10-24T14:48:53Z	`/`	ok	200	756	2	7ddb76f13ea1	per-receipt
62a94253d14505cd26b6	2026-10-23T23:36:45Z	`/sse`	ok	200	408	2	7ddb76f13ea1	per-receipt
0de3b5c7d44767656df0	2026-10-23T20:15:43Z	`/`	ok	200	446	2	7ddb76f13ea1	per-receipt

Operator? Reply, dispute or opt out.