polyfork.dev
Remote MCP server host. 1 server URL from the Official MCP Registry. Each is checked with a login-free MCP handshake (initialize, then tools/list; no tool is ever called, 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/polyfork.dev.
| URL | Transport | Registry Name | Last State | HTTP | Protocol | Tools | Recent Checks OK | Median ms | TLS | Last Checked |
|---|---|---|---|---|---|---|---|---|---|---|
https://polyfork.dev/mcp | streamable-http | dev.polyfork/polyfork | ok | 200 | 2025-06-18 | 12 | – | 593 | ok | 3 h ago |
MCP Check Receipts (Newest First, Up To 10 Per Server)
| Receipt | UTC Time | Path | State | HTTP | ms | Tools | Tools sha256 | Signed |
|---|---|---|---|---|---|---|---|---|
| f1b8b9c22952e546a0e8 | 2026-10-23T23:51:58Z | /mcp | ok | 200 | 593 | 12 | bc72c1294bd3 | per-receipt |
Operator? Reply, dispute or opt out.