Evaluates x402 endpoint reliability, pricing, settlement activity, alternatives, and change history before agents pay.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent ā or use 1-click editor setup below.
This server is confirmed live ā we successfully called its tools/list endpoint directly (see the verified badge above). We haven't yet sandbox-tested the stdio install command below specifically, which is a separate, ongoing check.
š” Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by X402 Trust MCP.
x402_ecosystem_statsFree aggregate snapshot of the entire x402 ecosystem (Base + Solana): how many endpoints are listed/active/delisted, what fraction are reachable and spec-compliant, and real on-chain USDC settlement volume / receivers / payers over the last 30 days. Use this to gauge market health before transacting.
x402_trust_leaderboardFree top-25 most trustworthy x402 endpoints, ranked by a deterministic trust score (uptime, envelope compliance, latency, age, on-chain settlement activity, price stability). Latency is measured from a single EU vantage point and includes network distance to the endpoint (so it is only lightly weighted). Use this to discover reliable paid endpoints.
x402_trust_previewFREE showcase of what x402_trust_score returns. You do NOT choose the endpoint: this returns the COMPLETE paid-grade trust report (every field ā exact score, scoreRange, full component breakdown, advertised price, on-chain settlement figures, all flags) for THREE endpoints picked from the current population ā the best-scored, the median, and the worst-scored ('samples' each carry 'role', 'populationRank', and the full 'report'). Use it to see exactly what the paid output looks like across the entire quality range BEFORE paying. It cannot score an endpoint you choose ā to evaluate YOUR OWN endpoint, call x402_trust_score (paid). Takes no arguments.
x402_trust_scoreTrust score (0-100, grade A-F, or '?' when unmeasured) for a SPECIFIC x402 endpoint -- cataloged or not (uncataloged endpoints are live-probed on first query, auto-adopted, score carries a low-confidence first-contact flag). PLUS a machine-readable verdict ('recommendation': proceed|caution|avoid|parameterize|unverified|not-payable|free), the advertised price ('advertised.amountUsd'), a confidence-adjusted band ('scoreRange'), and structured flags ('flagsDetailed' with code/severity/message; any severity 'error' means avoid). The 'parameterize' verdict (with 'templated':true) means the resource URL still contains an unresolved template placeholder (e.g. {slug}, :slug or %7Bā¦%7D) but we DO have a real signal (scored probes or a discovery fallback): substitute a valid value first, then the health metrics apply to the resolved URL. The 'unverified' verdict (grade '?') means we have NO measurement at all (every probe excluded and no discovery payment requirements to fall back on): it is unknown, not bad, so verify the endpoint yourself before paying. The 'not-payable' verdict (grade '?') means the URL answers a 402 with an EMPTY accepts[] (an auth/API-key gate such as sign-in-with-x), or answers a bare 401/403 with no payment envelope, so it is not an x402-payable resource at all and there is nothing to settle. The 'free' verdict (grade '?') means the endpoint answers plain requests with data (HTTP 200, no payment envelope) and has never presented a payment challenge: a free resource with no payment flow to grade, unmeasured by design, not a negative verdict. For templated per-item endpoints that ARE payable, a varying payTo/price is EXPECTED (one wallet/price per item): the report surfaces 'stats.payToVaries'+'payToDistinct30d' and 'advertised.amountRange30d' as a 'payto-varies'/'price-varies' note rather than a 'payto-changed-recently' hijack error; always pay the payTo in the live 402 quote, not a cached listing. 'stats.scoredProbes30d' vs 'stats.excluded30d' show how many probes actually back the score. Includes the full component breakdown, the provider-advertised 'serviceName' and 'description' (unverified provider claims, shown next to our independent metrics), and 30-day on-chain stats. Note: 'stats.avgLatencyMs' is measured from a single EU vantage point and includes network distance to the endpoint (see 'stats.latencyVantage'), so a geographically distant endpoint reads slower even when its server is fast. One call answers WHETHER and at WHAT PRICE to use an endpoint. Call this BEFORE paying an unknown x402 endpoint to avoid dead, fraudulent, or recently-hijacked services. Pay-per-call over x402; auto-pays if a wallet is configured, otherwise returns the price quote.
x402_endpoint_historyRaw observation time-series for a SPECIFIC x402 endpoint: listing/delisting/relisting events, advertised price changes, payTo changes, and probe results (uptime, latency, quoted amount) over the requested window (1-90 days). Per-probe 'latencyMs' is measured from a single EU vantage point and includes network distance to the endpoint. Pay-per-call over x402; auto-pays if a wallet is configured, otherwise returns the price quote.
x402_find_alternativesGiven an x402 endpoint URL, returns the top semantically-similar endpoints (matched on advertised purpose via description embeddings) that currently OUT-SCORE it on the deterministic trust score. Use this to route away from a mediocre/dead/expensive endpoint toward a more reliable, better-settled one serving the SAME function ā e.g. before paying, check if a higher-graded equivalent exists. Each alternative carries its trust 'score', 'grade', 'recommendation', cosine 'similarity' (0-1), 'amountUsd' price, 'priceCeiling' (true when amountUsd is an x402 'upto' authorization ceiling, not a fixed per-call price), and a free 'endpointPage' URL. Same-host siblings and 'avoid'-flagged endpoints are excluded. An empty 'alternatives' array is a valid answer meaning nothing beats the subject. Similarity is independent of latency/geography. Pay-per-call over x402 (~$0.005); auto-pays if a wallet is configured, otherwise returns the price quote.
The x402-trust-mcp MCP server helps agents assess x402 resources before sending payment. It reports a deterministic trust score from 0 to 100, a letter grade from A to F, a confidence-adjusted score range, advertised pricing, structured flags, and a recommendation such as proceed, caution, avoid, parameterize, unverified, not-payable, or free.
The service is backed by observations of the x402 catalog. Its metrics include uptime, 402 envelope compliance, latency, endpoint age, price stability, settlement activity, receivers, and payers. On-chain USDC activity is reported over a 30-day period. Provider-supplied service names and descriptions can be shown alongside independent measurements, but those provider claims are not verified by the score.
Use x402_semantic_search to find endpoints by describing a capability in plain language, then use x402_trust_score to inspect a candidate before paying. Search results can include similarity, price, score, grade, description, and a public endpoint page, but they do not include the full verdict or flags. x402_find_alternatives can identify semantically similar endpoints that score higher than a given resource.
The x402-trust-mcp MCP server also exposes free aggregate statistics and a top-25 leaderboard. x402_trust_preview demonstrates the complete paid report using the best, median, and worst current examples, without allowing a caller to choose the endpoint. For larger inventories, x402_trust_bulk scores up to 500 observed URLs using cached data; stale rows may be recomputed, but the operation does not perform a fresh live probe. Use the single-endpoint score when a new live probe is required.
A not-payable result indicates an empty payment accepts array or a bare 401/403 without a payment envelope. unverified means no usable measurement was available, while free identifies a resource that returned data without presenting a payment challenge. Template-bearing URLs may receive a parameterize result when a real signal exists but a path value must be substituted first.
Paid operations use x402 and can be handled in two ways. Without a configured wallet, the server returns a price quote for the host application to pay. With X402_PRIVATE_KEY configured, it can pay automatically, subject to X402_MAX_USD.
The service supports watch creation for one endpoint for 30 days. A successful watch returns a one-time bearer secret and URLs for polling, editing, renewal, and cancellation. Delivery can use signed HTTPS webhooks or Slack/Discord incoming webhooks, with up to five URLs of each type. URLs are connection-tested before payment or configuration changes are accepted.
Latency is measured from one EU vantage point and includes network distance, so it is only a lightly weighted signal and may disadvantage geographically distant services. Bulk results can be up to roughly 15 minutes old and are limited to 50 recomputations per eight seconds; unknown URLs return found: false while still being included in the paid batch.
The x402-trust-mcp MCP server does not guarantee that an endpoint is safe or suitable. Scores describe observed behavior and can be unavailable, stale, or affected by URL templates. Always use the live pay-to and price values in an endpoint's current 402 response, particularly for per-item resources whose destination and price can vary.
Always refer to the official documentation for the most accurate and up-to-date information.
Factual signals from GitHub, npm, and our automated checks ā not a rating.
No reviews yet ā be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/x402-trust-mcp)<a href="https://allmcps.com/mcp/x402-trust-mcp"><img src="https://allmcps.com/api/badge/x402-trust-mcp?style=directory" alt="X402 Trust MCP on AllMCPs" /></a>