fateandstars.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://fateandstars.com/mcp`	streamable-http	com.fateandstars/tarot-knowledge	ok	200	2025-06-18	3	5/5	910	ok	11 h ago

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

Receipt	UTC Time	Path	State	HTTP	ms	Tools	Tools sha256	Signed
f93b67193a6f40b6e014	2026-10-27T22:57:37Z	`/mcp`	ok	200	1299	3	8c9db1b11d52	per-receipt
bf48d5435edaf259fcd5	2026-10-26T03:33:56Z	`/mcp`	ok	200	910	3	8c9db1b11d52	per-receipt
c635432ca46c9cc6f606	2026-10-25T22:57:39Z	`/mcp`	ok	200	544	3	8c9db1b11d52	per-receipt
2da735fcce9d0ad73b86	2026-10-24T18:51:44Z	`/mcp`	ok	200	929	3	8c9db1b11d52	per-receipt
b5f42ea486b6ced48368	2026-10-23T22:57:43Z	`/mcp`	ok	200	582	3	8c9db1b11d52	per-receipt

Operator? Reply, dispute or opt out.