English Français العربية

io.github.zagchk/x402score-mcp

Official registry Other

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

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package x402score-mcp
Claude Code 
claude mcp add x402score-mcp -- npx -y x402score-mcp@0.4.2
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "x402score-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "x402score-mcp@0.4.2"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. x402Score — SDK & MCP server
  2. Packages
  3. Status
  4. Why trust the numbers

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.

Frequently asked questions

What is io.github.zagchk/x402score-mcp?

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

How do I install io.github.zagchk/x402score-mcp?

It runs on your machine. In Claude Code: claude mcp add x402score-mcp -- npx -y x402score-mcp@0.4.2. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.zagchk/x402score-mcp need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is io.github.zagchk/x402score-mcp open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains io.github.zagchk/x402score-mcp?

It is published by zagchk. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.