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.

x402 Counterparty Score

REMOTE · X402SCORE.ORG

Trust scores for x402 sellers: wash-trading, real buyers, verdict. $0.02/score via x402 on Base.

Available components

+4 this week 86 Trust /100

Last scanned (2 hours ago)

Scores higher than 93% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Crypto and Web3

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 Security74
Transport & Reachability100
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 248 tokens (~124/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 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.

  • 5 Nov 26 0
    • Stability: 0.97 → pass security
  • 4 Nov 26 0
    • Stability: pass → 0.97 functional
  • 3 Nov 26 +4
    • HTTPS: unverified → pass ▲ security
  • 18 Oct 26 +1
    • Stability: 0.97 → pass security
  • 16 Oct 26 +1

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

  • 14 Oct 26 +1

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

  • 12 Oct 26 +1

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

  • 10 Oct 26 +60
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.73 ▲ functional
    • MCP protocol: unverified → pass ▲ 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 5 Nov 2026 · Probed https://x402score.org/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=x402score.org CN=WE1,O=Google Trust Services,C=US 5 Nov 2026 3 Feb 2027 ECDSA 256 ECDSA-SHA256 dd59fa6f943938320e226645b9c72d03
SANs: x402score.org, *.x402score.org
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 x402score.org. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
org. present 725, 26974 8, 8 Verified
x402score.org. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://x402score.org/mcp Verified 200
http (plaintext) http://x402score.org/mcp HTTPS enforced 301 https://x402score.org/mcp
MCP tools · 2 exposed · ~248 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
get_sample_score ~102

Returns a clearly-marked stale sample counterparty score in the exact response schema of score_x402_counterparty (verdict, wash_trading_ratio, real_buyer_count, repeat_buyer_rate, source, updated_at, confidence). Free, no payment required, no input required. Sample data is fixed and expired by design — use it to validate response parsing, then call score_x402_counterparty ($0.02/call) for fresh decision-grade scores.

Input schema present but exposes no named parameters.

NameTypeReqDescription
confidencenumberyesObjective confidence from rule coverage and data completeness, 0 to 1. Never self-reported by an LLM.
deliveryobject–Result of the most recent real-money delivery probe (mystery-shopper purchase from the disclosed probe wallet). Absent if this subject has not been probe-purchased.
real_buyer_countintegeryesNumber of distinct real buyers after wash-trading filtering.
repeat_buyer_ratenumberyesShare of real buyers that purchased more than once, 0 to 1.
samplebooleanyesAlways true: this response is a sample, not a live score.
sample_noticestringyesMachine-readable warning that the data is stale sample data.
sourcestringyesOrigin of the underlying data, e.g. "base-settlements" or "bazaar-directory".
subjectstringyesThe x402 endpoint URL or pay-to address this score is about.
updated_atstringyesISO 8601 UTC timestamp of when this score was computed.
verdictstringyesDecision-grade trust verdict on the counterparty.
wash_trading_rationumberyesShare of nominal settlement volume attributed to wash trading (self-dealing or funding-loop patterns), 0 to 1.

No examples provided.

score_x402_counterparty ~146

Returns trust verdict (trusted/caution/avoid) with wash-trading ratio, real-buyer count, and repeat-buyer rate for an x402 endpoint URL or pay-to address. $0.02/call. Computed from Base on-chain settlement data and the x402 Bazaar catalog; a score is sold only if refreshed within the past 24 hours.

NameTypeReqDescription
subjectstringyesThe counterparty to score: an x402 endpoint URL (e.g. "https://api.seller.example/quote") or a pay-to address (e.g. "0x036C…"), exactly as advertised in the x402 Bazaar catalog or the 402 handshake.
NameTypeReqDescription
confidencenumberyesObjective confidence from rule coverage and data completeness, 0 to 1. Never self-reported by an LLM.
deliveryobject–Result of the most recent real-money delivery probe (mystery-shopper purchase from the disclosed probe wallet). Absent if this subject has not been probe-purchased.
real_buyer_countintegeryesNumber of distinct real buyers after wash-trading filtering.
repeat_buyer_ratenumberyesShare of real buyers that purchased more than once, 0 to 1.
sourcestringyesOrigin of the underlying data, e.g. "base-settlements" or "bazaar-directory".
subjectstringyesThe x402 endpoint URL or pay-to address this score is about.
updated_atstringyesISO 8601 UTC timestamp of when this score was computed.
verdictstringyesDecision-grade trust verdict on the counterparty.
wash_trading_rationumberyesShare of nominal settlement volume attributed to wash trading (self-dealing or funding-loop patterns), 0 to 1.

No examples provided.

Install

How do I install the x402 Counterparty Score MCP server?

x402 Counterparty Score is a hosted endpoint at https://x402score.org/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 · x402score.org

# add to Claude Code
claude mcp add --transport http org-x402score-counterparty-score 'https://x402score.org/mcp'
Common questions

What is the x402 Counterparty Score MCP server?

x402 Counterparty Score is an MCP server listed in the public MCP registry as org.x402score/counterparty-score. Trust scores for x402 sellers: wash-trading, real buyers, verdict. $0.02/score via x402 on Base. This page covers its hosted endpoint (https://x402score.org/mcp).

Is the x402 Counterparty Score MCP server safe to use?

x402 Counterparty Score scores 86 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 x402 Counterparty Score MCP server expose?

x402 Counterparty Score exposes 2 tools: score_x402_counterparty, get_sample_score. Their descriptions and schemas cost roughly 248 tokens of context every time the server is loaded.

Does the x402 Counterparty Score MCP server require authentication?

No. We connected to x402 Counterparty Score without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the x402 Counterparty Score MCP server still maintained?

x402 Counterparty Score is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.