Odel
MCP server: One MCP server.

X402score

@zagchkMCP server · External

Check an x402-paid API endpoint's trust score before paying it - live-probed, not self-reported.

v0.4.2TypeScript
Freeno charge per call
How to install

Runs on your machine from its package; the steps are below.

What it does

  1. Reads
  2. Writes
  3. High impact

Not assessed yet.

What it costs

Free

Odel charges nothing per call. The publisher may charge for its own service.

Runs locally over stdio

This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).

npmx402score-mcpv0.4.2

Run

npx -y x402score-mcp

MCP client config

{
  "mcpServers": {
    "x402score": {
      "command": "npx",
      "args": [
        "-y",
        "x402score-mcp"
      ]
    }
  }
}
README1 min read

x402Score — SDK & MCP server

Public client-side code for x402Score — free, automated reputation scores for x402-paid API endpoints. The scoring backend itself is closed-source (the exact weights, decay rate, and thresholds are deliberately unpublished, to keep scores harder to game — see /docs). This repo is just the two things a developer or agent needs to consume x402Score programmatically.

Packages

  • sdk/ — x402score-sdk, published on npm. TypeScript client for the full public API, plus signed-response verification. See sdk/README.md.
  • mcp/ — x402score-mcp, an MCP server exposing four agent tools (check_endpoint_score, search_leaderboard, get_calibration_report, submit_endpoint), built on the SDK above. Not yet published to any MCP registry — held until the on-chain payment signal's calibration gate closes (~2026-10-19, after three weekly calibration cycles). See mcp/README.md.

Status

Status
SDK (npm)Published — npm install x402score-sdk
MCP serverBuilt, tested, not yet published — see mcp/README.md for why

Why trust the numbers

Every API response can be verified two ways: a per-response signature proves a given response really came from x402Score and wasn't altered in transit, and a daily blockchain-anchored checkpoint proves the underlying historical data wasn't quietly altered after the fact either. Full explanation at /transparency.