BotsRated (beta)
com.botsrated/botsratedVersion 0.4.0-betaSigned checks of x402 sellers on Base and remote MCP servers, before your agent pays.
Status
Responds277 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 13:49 UTC
- Latency
- 277 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://botsrated.com/mcpResponds277 msNo sign-in
Claude Code
claude mcp add --transport http botsrated https://botsrated.com/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: botsrated
Remote MCP server URL: https://botsrated.com/mcpCursor
{
"mcpServers": {
"botsrated": {
"url": "https://botsrated.com/mcp"
}
}
}VS Code
code --add-mcp '{"name":"botsrated","type":"http","url":"https://botsrated.com/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
12 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
bestCall this when you want a short list of covered providers for a task. PAID $0.01 USDC on Base mainnet via x402. Top 3 covered providers for a task, sorted by reliability (default), price or latency, with matching routes and the numbers behind the order. An unpaid call returns an x402 v2 PaymentRequired tool error (isError, structuredContent with accepts); an x402-aware MCP client signs it and retries with the payment in _meta["x402/payment"]. Input is checked before any payment request; charged only when the tool returns an answer (settlement in result _meta["x402/payment-response"]). | No | Yes | Yes | No |
checkCall this when you want the measured facts for one host. PAID $0.01 USDC on Base mainnet via x402 after the shared free daily quota (the first 25 checks per client per UTC day are free on this tool and on HTTP GET /v1/check; one quota, not two). Measured facts for one host (an x402 seller, or a remote MCP server host: handshake state, protocol version, tools count/hash and change history, auth needed, latency): valid-402 rate, latency p50/p90, price and payTo vs listing, paid test-buys with Base tx links, freshness, last 5 receipts. An unpaid call returns an x402 v2 PaymentRequired tool error (isError, structuredContent with accepts); an x402-aware MCP client signs it and retries with the payment in _meta["x402/payment"]. Input is checked before any payment request; charged only when the tool returns an answer (settlement in result _meta["x402/payment-response"]). | No | Yes | Yes | No |
check_mcp_setupCall this when you want to check the MCP servers in your config or a list of hosts. Free. Same report as POST /v1/dependency-watch/report: up to 50 hosts or an mcp.json. Each server comes back with its last handshake, tool count, tools-hash change date and receipt link. Then watch up to 3 hosts free, or use Desk for more. Nothing is fetched or stored. | No | Yes | Yes | No |
coverageCall this when you want to know how many sellers and MCP servers are covered. No arguments are required. FREE. How many x402 seller hosts and remote MCP servers BotsRated covers (mcp_servers: servers, hosts, probed, last-state counts; chains: measured hosts quoting Base USDC / Solana USDC in the last 48 h, null until measured), from which discovery sources, the probe schedules and when the last probe runs finished. | No | Yes | Yes | No |
findCall this when you need covered sellers or MCP servers for a task and you have not picked a host yet. FREE (uses 1 of the 25 free checks per client per UTC day, shared with /v1/check). Top matching covered x402 sellers and remote MCP servers for what you need, each with a one-line factual reason (text match, recent valid 402s or handshakes, median latency, quoted price) and its page URL. Same filters as best, without the full ranking and receipts. Seller text is the seller's own words; we don't check it. Optional category is a Works Today slug; it is ignored unless that directory is live and the category is published. | No | Yes | Yes | No |
preflightCall this when you have a host, or you just pasted an MCP config, and you want the latest check before anything else. Not charged. Is this x402 seller or remote MCP server covered, and what did its latest unpaid probe show? For MCP server hosts: last handshake state (ok, auth_required, handshake_failed, unreachable, or blocked = not contacted because the URL, a redirect or its DNS points somewhere our rules don't allow), protocol version, tool count and tools hash. Returns status, whether the 402 challenge was valid, quoted vs listed price and payTo, freshness (age, stale flag) and the receipt link. Use before paying any x402 seller. Cap: 1000 per client IP (IPv6 /48) per UTC day, then an error preflight_cap. A key allows 25000 per key per UTC day. No public price is listed for a key. | No | Yes | Yes | No |
reportCall this when you want the full receipt history for one host. PAID $0.002 USDC on Base mainnet via x402 (the first 3 calls per client per UTC day are free over HTTP GET /v1/report/{host}). Full receipt history for one host (up to 1000 probes plus all paid test-buys). An unpaid call returns an x402 v2 PaymentRequired tool error (isError, structuredContent with accepts); an x402-aware MCP client signs it and retries with the payment in _meta["x402/payment"]. Input is checked before any payment request; charged only when the tool returns an answer (settlement in result _meta["x402/payment-response"]). | No | Yes | Yes | No |
sampleCall this when you want to see a real paid answer before you pay. No arguments are required; route defaults to check. FREE. Returns a real sample of a paid response (check, report or best) for a fixed example, so you can see exactly what you would buy. | No | Yes | Yes | No |
seller_announceCall this when you are the verified owner and you are posting a planned price or payTo. FREE. Verified owner posts a planned price and/or payTo set, effective_at, note, and sig_b64 over the canonical statement. Sign with the key you made at claim. The server stored only that public key. Does not change a measurement. A payTo alert is not suppressed. | No | No | No | No |
seller_self_checkCall this when you want the stored measurements for a host. FREE. Read stored measurements for a host you operate or anyone can read: listing versus quoted price, whether recent unpaid checks returned a valid payment request, payTo observations. Not a judgement. The owner key is made on your side; claim stores only the public key. Pass probe:true with session (the verified-owner token from POST /v1/seller/claim/verify) to run one on-demand unpaid probe with the same receipt code as buyer checks. probe is rate-limited. | No | Yes | Yes | No |
watch_freeCall this when you want an email only when a covered host's measured facts change. Free. Same watch as POST /v1/alerts/subscribe: 1 covered host, email only, at most once per UTC day when measured facts change, 30 days, up to 3 active watches per client. The confirmation email is the existing alerts email. Not a price change. Slack, Discord and webhook stay on a paid plan. The success payload returns handle, the same value as token, shown once. Next step: confirm the email, then call what_changed with that handle. | No | No | No | No |
what_changedCall this when you have a handle from watch_free and you want what changed on that free watch. Free. Pass handle from watch_free (token is the same value). Reads measured changes for the host on that alerts-free watch only: price, payTo, valid 402, listing or status, and tools-hash or tool changes already stored, plus a receipt link when a receipt was stored. If since is omitted, the window starts when the watch was created (window.basis is since_watch_created). If that time is missing, the window is the last 7 days. Confirm the email before the first read. Not charged. A paid plan token is rejected. changes_since stays the plan-bearer tool. | No | Yes | Yes | No |
Details
- Registry status
- Active
- Published
- Oct 24, 2026
- Updated
- Oct 24, 2026
- Categories (suggested)
- E-commerceSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared