Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

BotsRated (beta)

REMOTE · BOTSRATED.COM

Signed checks of x402 sellers on Base and remote MCP servers, before your agent pays.

Available components

+4 this week 76 Trust /100

Last scanned (19 hours ago)

Scores higher than 66% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability60
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1563 tokens (~173/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 80% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 1414 → 1563 ▼ functional
    • New tool “history” functional
  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 0
    • Schema quality: 1255 → 1414 ▼ functional
    • New tool “botsrated_policy_check” functional
  • 27 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “check” rewrote its description, which is the text the model reads security
    • Tool “find” rewrote its description, which is the text the model reads security
    • Tool “preflight” rewrote its description, which is the text the model reads security
    • Tool “report” rewrote its description, which is the text the model reads security
  • 26 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “best” rewrote its description, which is the text the model reads security
    • Tool “check” rewrote its description, which is the text the model reads security
    • Tool “report” rewrote its description, which is the text the model reads security
    • Schema quality: 143 → 175 ▼ functional
    • Server version: 0.4.0-beta → 0.4.0 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Probed https://botsrated.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=botsrated.com CN=WE1,O=Google Trust Services,C=US 23 Oct 2026 21 Jan 2027 ECDSA 256 ECDSA-SHA256 9afd3a4bd7cfca461376dee5b19468c9
SANs: botsrated.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of botsrated.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
botsrated.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
content-security-policy default-src 'none'; frame-ancestors 'none'; sandbox
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://botsrated.com/mcp Verified 200
http (plaintext) http://botsrated.com/mcp HTTPS enforced 301 https://botsrated.com/mcp
MCP tools · 9 exposed · ~1,296 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
best ~219

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"]).

NameTypeReqDescription
max_pricenumber–Optional max quoted price per call in USD, e.g. 0.01
sortstring––
taskstringyesWhat you need, 1-4 keywords, e.g. web search
typestring–all (default): x402 sellers in results plus remote MCP servers in mcp_results (matched on tool names and descriptions); x402 or mcp: only that kind

No output schema declared.

No examples provided.

botsrated_policy_check ~159

FREE, never charged. Your own pass / warn / block rules applied to BotsRated measurements. Private to your plan or org key: until MCP auth ships this tool checks your arguments and answers bearer_required; call POST /v1/policy/check with your Bearer token. decision null means no answer, never a pass: apply your own fail_mode.

NameTypeReqDescription
hoststring–Seller hostname or URL, e.g. blockrun.ai or https://blockrun.ai/api/v1/chat/completions
mcpobject––
quoteobject–Optional exact quote your client is about to sign
resource_urlstring–Optional 402 resource URL (host is taken from it when host is missing)

No output schema declared.

No examples provided.

check ~219

PAID $0.001 USDC on Base mainnet via x402 (the first 25 calls per client per UTC day are free over HTTP GET /v1/check). 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"]).

NameTypeReqDescription
hoststringyesSeller hostname or URL, e.g. blockrun.ai or https://blockrun.ai/api/v1/chat/completions

No output schema declared.

No examples provided.

coverage ~54

FREE. How many x402 seller hosts and remote MCP servers BotsRated covers (mcp_servers: servers, hosts, probed, last-state counts), from which discovery sources, the probe schedules and when the last probe runs finished.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

find ~128

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.

NameTypeReqDescription
qstringyesWhat you need, 1-4 keywords, e.g. weather or crypto price

No output schema declared.

No examples provided.

history ~140

FREE. Signed daily aggregates for one seller host, newest first: probes, valid-402 count, status and error counts, latency p50/p90, quoted amounts, payTo/asset/network seen, 402 check counts, the day's receipt ids and where the raw signed receipts are archived (archive_url + line range + sha256). Each aggregate is ed25519-signed (key botsrated-prober-1).

NameTypeReqDescription
daysinteger–How many UTC days to return (1-90)
hoststringyesSeller hostname or URL, e.g. blockrun.ai or https://blockrun.ai/api/v1/chat/completions

No output schema declared.

No examples provided.

preflight ~161

FREE. 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. Free, no key (normal per-IP rate limits apply).

NameTypeReqDescription
urlstringyesSeller hostname or URL, e.g. blockrun.ai or https://blockrun.ai/api/v1/chat/completions

No output schema declared.

No examples provided.

report ~170

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"]).

NameTypeReqDescription
hoststringyesSeller hostname or URL, e.g. blockrun.ai or https://blockrun.ai/api/v1/chat/completions

No output schema declared.

No examples provided.

sample ~46

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.

NameTypeReqDescription
routestringyes–

No output schema declared.

No examples provided.

Install

How do I install the BotsRated (beta) MCP server?

BotsRated (beta) is a hosted endpoint at https://botsrated.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · botsrated.com

# add to Claude Code
claude mcp add --transport http com-botsrated-botsrated 'https://botsrated.com/mcp'
Common questions

What is the BotsRated (beta) MCP server?

BotsRated (beta) is an MCP server listed in the public MCP registry as com.botsrated/botsrated. Signed checks of x402 sellers on Base and remote MCP servers, before your agent pays. This page covers its hosted endpoint (https://botsrated.com/mcp).

Is the BotsRated (beta) MCP server safe to use?

BotsRated (beta) scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the BotsRated (beta) MCP server expose?

BotsRated (beta) exposes 9 tools: preflight, find, coverage, sample, history, and 4 more. Their descriptions and schemas cost roughly 1,296 tokens of context every time the server is loaded.

Does the BotsRated (beta) MCP server require authentication?

No. We connected to BotsRated (beta) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the BotsRated (beta) MCP server still maintained?

BotsRated (beta) is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.