blumify.io
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/blumify.io.
| URL | Transport | Registry Name | Last State | HTTP | Protocol | Tools | Recent Checks OK | Median ms | TLS | Last Checked |
|---|---|---|---|---|---|---|---|---|---|---|
https://blumify.io/api/media/v1/mcp/public | streamable-http | io.blumify/transcripts-public | ok | 200 | 2025-06-18 | 1 | – | 734 | ok | 9 h ago |
https://blumify.io/api/media/v1/mcp | streamable-http | io.blumify/transcripts | auth_required | 401 | – | 711 | ok | 2 h ago |
MCP Check Receipts (Newest First, Up To 10 Per Server)
| Receipt | UTC Time | Path | State | HTTP | ms | Tools | Tools sha256 | Signed |
|---|---|---|---|---|---|---|---|---|
| c87896a61f05f792da42 | 2026-10-24T10:30:44Z | /api/media/v1/mcp | auth_required | 401 | 711 | per-receipt | ||
| 04a64b4a4565dbd1b23e | 2026-10-24T03:15:40Z | /api/media/v1/mcp/public | ok | 200 | 734 | 1 | 8d94325bdef2 | per-receipt |
Operator? Reply, dispute or opt out.