knowfulham.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://knowfulham.com/mcp`	streamable-http	com.knowfulham/places	ok	200	2025-06-18	7	5/5	413	ok	39 h ago

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

Receipt	UTC Time	Path	State	HTTP	ms	Tools	Tools sha256	Signed
e784a32bb0f675d362f1	2026-10-28T08:30:40Z	`/mcp`	ok	200	379	7	081e868e9dd4	per-receipt
e2954c1327428dc06f32	2026-10-27T08:30:48Z	`/mcp`	ok	200	737	7	081e868e9dd4	per-receipt
829fe3170c9e26ee29c5	2026-10-26T08:30:41Z	`/mcp`	ok	200	501	7	081e868e9dd4	per-receipt
7c74cab1a8cf69d72691	2026-10-25T08:30:39Z	`/mcp`	ok	200	413	7	081e868e9dd4	per-receipt
edae53826a908b953028	2026-10-24T08:30:42Z	`/mcp`	ok	200	66	7	081e868e9dd4	per-receipt

Operator? Reply, dispute or opt out.