BotsRatedBETA

fysio.care

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; 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/fysio.care.

URLTransportRegistry NameLast StateHTTPProtocolToolsRecent Checks OKMedian msTLSLast Checked
https://fysio.care/api/mcpstreamable-httpcare.fysio/discoveryok2002025-06-184–740ok3 h ago

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

ReceiptUTC TimePathStateHTTPmsToolsTools sha256Signed
27d50de192704e0e21302026-10-24T09:27:43Z/api/mcpok2004044ef0f2c1c17e1per-receipt
38ad1885669f4137e4542026-10-23T18:03:41Z/api/mcpok2007404ef0f2c1c17e1per-receipt

Operator? Reply, dispute or opt out.