# x402 Counterparty Score (remote · x402score.org)

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

- Trust score: 62/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `x402score.org`: 62/100 (this document), [markdown](https://verifymcp.io/servers/org-x402score-counterparty-score/x402score.md), [page](https://verifymcp.io/servers/org-x402score-counterparty-score/x402score)

## Channel facts

- Endpoint: `https://x402score.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 248 tokens (~124/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http org-x402score-counterparty-score https://x402score.org/mcp
```

### Codex

```toml
[mcp_servers.org-x402score-counterparty-score]
url = "https://x402score.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-x402score-counterparty-score": {
      "type": "remote",
      "url": "https://x402score.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-x402score-counterparty-score --url https://x402score.org/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  org-x402score-counterparty-score:
    url: "https://x402score.org/mcp"
```

### Other

```json
{
  "mcpServers": {
    "org-x402score-counterparty-score": {
      "type": "http",
      "url": "https://x402score.org/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 62, +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.

### 2026-08-01 (score 61, +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.

### 2026-07-31 (score 60, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 62, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 61, +1)

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

### 2026-07-27 (score 60, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 59)

First indexed and scored.

## MCP tools (2)

### `score_x402_counterparty` (~146 tokens)

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.

Input parameters:

- `subject` (string, required): The 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.

Output parameters:

- `confidence` (number): Objective confidence from rule coverage and data completeness, 0 to 1. Never self-reported by an LLM.
- `delivery` (object): 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_count` (integer): Number of distinct real buyers after wash-trading filtering.
- `repeat_buyer_rate` (number): Share of real buyers that purchased more than once, 0 to 1.
- `source` (string): Origin of the underlying data, e.g. "base-settlements" or "bazaar-directory".
- `subject` (string): The x402 endpoint URL or pay-to address this score is about.
- `updated_at` (string): ISO 8601 UTC timestamp of when this score was computed.
- `verdict` (string): Decision-grade trust verdict on the counterparty.
- `wash_trading_ratio` (number): Share of nominal settlement volume attributed to wash trading (self-dealing or funding-loop patterns), 0 to 1.

### `get_sample_score` (~102 tokens)

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.

Output parameters:

- `confidence` (number): Objective confidence from rule coverage and data completeness, 0 to 1. Never self-reported by an LLM.
- `delivery` (object): 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_count` (integer): Number of distinct real buyers after wash-trading filtering.
- `repeat_buyer_rate` (number): Share of real buyers that purchased more than once, 0 to 1.
- `sample` (boolean): Always true: this response is a sample, not a live score.
- `sample_notice` (string): Machine-readable warning that the data is stale sample data.
- `source` (string): Origin of the underlying data, e.g. "base-settlements" or "bazaar-directory".
- `subject` (string): The x402 endpoint URL or pay-to address this score is about.
- `updated_at` (string): ISO 8601 UTC timestamp of when this score was computed.
- `verdict` (string): Decision-grade trust verdict on the counterparty.
- `wash_trading_ratio` (number): Share of nominal settlement volume attributed to wash trading (self-dealing or funding-loop patterns), 0 to 1.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/org-x402score-counterparty-score/x402score#diagnostics

## Score history

- 2026-08-03: 62
- 2026-08-02: 61
- 2026-08-01: 61
- 2026-07-31: 60
- 2026-07-30: 62
- 2026-07-29: 61
- 2026-07-28: 61
- 2026-07-27: 60
- 2026-07-26: 59

## Links

- Remote endpoint: https://x402score.org/mcp
- Website: https://x402score.org/
- Changelog RSS feed: https://verifymcp.io/servers/org-x402score-counterparty-score/x402score/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-x402score-counterparty-score/x402score/changelog.json
- HTML version of this page: https://verifymcp.io/servers/org-x402score-counterparty-score/x402score