invokely.ai
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/invokely.ai.
| URL | Transport | Registry Name | Last State | HTTP | Protocol | Tools | Recent Checks OK | Median ms | TLS | Last Checked |
|---|---|---|---|---|---|---|---|---|---|---|
https://invokely.ai/mcp/trial | streamable-http | io.github.estevecastells/invokely | ok | 200 | 2025-06-18 | 24 | – | 807 | ok | 13 h ago |
https://invokely.ai/mcp | streamable-http | io.github.estevecastells/invokely | auth_required | 401 | – | 138 | ok | 10 h ago |
MCP Check Receipts (Newest First, Up To 10 Per Server)
| Receipt | UTC Time | Path | State | HTTP | ms | Tools | Tools sha256 | Signed |
|---|---|---|---|---|---|---|---|---|
| e0793bbe3389e9734612 | 2026-10-24T04:21:47Z | /mcp | auth_required | 401 | 138 | per-receipt | ||
| 39f3067b1044241b475f | 2026-10-24T01:54:49Z | /mcp/trial | ok | 200 | 807 | 24 | 26186ab70584 | per-receipt |
Operator? Reply, dispute or opt out.