api.almmity.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://api.almmity.com/mcp`	streamable-http	com.almmity.api/pl-firmy	ok	200	2025-06-18	20	5/5	511	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
31a86229f9e1fc5d2ca6	2026-10-27T18:48:38Z	`/mcp`	ok	200	511	20	72fa4ecd014e	per-receipt
08200f46d999f743b8c4	2026-10-26T18:48:41Z	`/mcp`	ok	200	129	20	72fa4ecd014e	per-receipt
f93214bbcee6557e7375	2026-10-25T18:48:38Z	`/mcp`	ok	200	549	20	72fa4ecd014e	per-receipt
522fbbc1f4527c3a1451	2026-10-24T09:33:51Z	`/mcp`	ok	200	808	20	72fa4ecd014e	per-receipt
cd12550805f0066a366b	2026-10-23T18:48:36Z	`/mcp`	ok	200	117	20	72fa4ecd014e	per-receipt

Operator? Reply, dispute or opt out.