BotsRatedBETA

openpath.sh

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/openpath.sh.

URLTransportRegistry NameLast StateHTTPProtocolToolsRecent Checks OKMedian msTLSLast Checked
https://openpath.sh/mcp/searchstreamable-httpsh.openpath/openpathok2002025-06-182–469ok8 h ago
https://openpath.sh/mcpstreamable-httpsh.openpath/openpathauth_required401–239ok6 h ago

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

ReceiptUTC TimePathStateHTTPmsToolsTools sha256Signed
32363316b14e9e3e5fdf2026-10-24T05:57:42Z/mcpauth_required401239per-receipt
4b31d5a124ae115b3b0a2026-10-24T04:27:57Z/mcp/searchok2004692a24e2e279f43per-receipt

Operator? Reply, dispute or opt out.