
X402 Trust Mcp
io.github.JonasFuchssPublished by GitHub account JonasFuchssv1.16.0Updated Oct 24, 2026
Discover x402 endpoints and check their trust score before your agent pays them.
Overview
MCP server that lets an assistant search the x402 endpoint catalog and check an endpoint's trust score before paying it.
- What you can do
- Search and discover x402 endpoints by keyword or meaning, and browse ecosystem stats, the trust leaderboard and verified providers
- Get a full trust verdict for one endpoint (score, grade, recommendation, price, flags), with unknown endpoints live-probed
- Review raw probe and event history for an endpoint over 1-90 days
- Find semantically similar endpoints that out-score a given one, or score up to 500 endpoints in one bulk call
- Create, poll, edit, cancel and renew 30-day endpoint watches that alert on payTo or price changes, delisting, spec regressions and downtime
- When to use it
- Useful when an agent is about to pay an x402 endpoint and wants an auditable trust check first, or when you need to discover x402 services by capability and compare candidates before committing funds.
- Requirements
- Runs locally via npx (Node.js). Free tools need no configuration. Paid tools need a funded Base USDC wallet private key in X402_PRIVATE_KEY for auto-pay, or return a price quote for the host to pay. Optional caps: X402_MAX_USD, X402_MAX_TOTAL_USD, X402_MAX_CALLS, plus X402_TIMEOUT_MS, X402_TRUST_API_BASE and X402_BASE_RPC_URL. Network access to the x402-trust API and a Base RPC.
Installation
In SourceWeft
- Open X402 Trust Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
x402-trust-mcp
An MCP server for discovering x402 endpoints and checking their trust before paying them: semantic and keyword search across the monitored catalog, plus trust scores, history, bulk scoring, and watches for any endpoint.
Backed by x402-trust.com, which monitors the x402 ecosystem on Base and Solana 24/7: uptime probes, 402-envelope spec compliance, price history, and real on-chain USDC settlement volume per endpoint. Every score is computed deterministically, no LLM involved, so the breakdown is fully auditable.
Tools
Paid tools cost from $0.005 (single lookup) to ~$0.50 (500-endpoint
bulk), charged over x402 (USDC on Base). With X402_PRIVATE_KEY set the server
auto-pays within your limits; otherwise it returns the price quote for your
host to pay. List tools page with limit (max 25) + offset and return a
total.
Field-level documentation, verdict semantics, watch cursor rules and webhook signature details live at x402-trust.com/llms.txt; every response is self-describing via its schema at x402-trust.com/schemas.
Install
Add to your MCP client config (e.g. Claude Desktop claude_desktop_config.json):
To enable autonomous payment for the paid tools, add a funded Base USDC wallet:
Configuration (env vars)
The free tools work with no configuration at all.
Security
X402_PRIVATE_KEY is a hot wallet: fund it with only what you are willing to
spend on trust lookups. The key never leaves your machine; it signs EIP-3009
payment authorizations locally, after policy checks: chain allow-list (Base
mainnet by default), canonical USDC contract verification, and the spend and
call-count caps above. Before every payment the client re-reads the wallet's
USDC balance: a wallet that cannot cover the quote is refused locally, before
anything is signed, so an empty wallet never produces failed settlement
attempts, and a top-up takes effect on the very next call.
Response signatures
Signed tool results carry a top-level signature block: an Ed25519 signature
over the JCS-canonicalized (RFC 8785) response. It proves the content was
assembled by x402-trust and not modified afterwards.
One rule matters when verifying: pin the trust anchor, never follow it from
the response. signature.publicKeys is a discovery hint; a forged response
would point at the attacker's own key document and still verify. Pin the public
key itself or fetch https://x402-trust.com/.well-known/x402-trust-keys.json
once at bootstrap and cache it. A worked test vector and a 20-line reference
verifier live at x402-trust.com/schemas.
Watch management responses are unsigned by design: they carry capability
secrets that must never be forwarded as evidence.
License
MIT
Source: README.md at commit 7c59676
Tools
0Version history
4- v1.16.0LatestOct 15, 2026
- v1.15.0Oct 5, 2026
- v1.14.0Oct 1, 2026
- v1.13.0Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts