mcp server
x402-list-mcp
x402-list directory MCP: services, facilitator volume, ranked picks, paid assessments.
Description as published by the maintainer. Source
- version 0.4.2
- active
active — Most recent push to the repository was 2026-07-28.
What this server can do
6 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
assess_services(probe, question, services, payment_signature_b64)- Run a fresh, PAID AI assessment comparing a shortlist of already-listed x402 services for a stated need. It charges a one-time $0.25 USDC on Base (x402) for the fresh reasoning only; reading an already-computed assessment stays free via get_service. This tool is a pure pass-through: it never holds keys, never signs, and never settles. Call it once WITHOUT payment_signature_b64 to receive the x402 payment challenge (accepts[], amount, payTo, and a base64 PAYMENT-REQUIRED header) verbatim; sign accepts[0] client-side with your own wallet; then call again with the SAME question and services plus payment_signature_b64 to receive the assessment report and a base64 PAYMENT-RESPONSE settlement receipt. Optionally include a probe target as probe { slug, endpoint_path? } to also test one listed service live: when the server has live probing armed, after the fresh reasoning it makes a real x402 payment to that endpoint and analyzes what it returns, and the challenge is then priced at $0.25 plus that endpoint price X (probe fees are non-refundable regardless of outcome); the report then carries a probe_report block with a verdict and truncated extracts, never the verbatim third-party response, and when live probing is not armed the probe is ignored. If the fresh run cannot be produced the server answers before settling, so the caller is never charged, and there is no refund. Prices are US dollars. Required: question, services.
check_health(slug, uptime_period, include_services)- Check live health of x402 services. With no slug, returns a directory-wide snapshot (counts of online/degraded/offline/unknown plus per-service status). With a slug, returns that service's status, uptime windows, response time, consecutive failures, and recent daily uptime snapshots. No money fields.
find_best_service(q, limit, prefer, network, category, max_price_usd, require_verified, include_facilitator_context)- Recommend the best x402 service(s) for a need. Ranked mostly on per-service reliability (live status, verification, uptime, response time), x402 compliance (the share of deterministic conformance checks the service passes, capped at 0.6 out of 1, the floor of the C band, when at least one of its EVM routes is missing the EIP-712 domain parameters a standard x402 client needs in order to sign a payment: a fact about the payment envelope, not a judgement on the service), and price (USD), filtered by category and network, with a SMALL (~10%) weight on on-chain traction: settlement volume, transaction count, and unique buyers measured per service over its known payTo addresses via recognized settlers (a conservative undercount, not an estimate). Traction never dominates; a service whose payTo is shared across services has only its settlement volume attributed PRO-QUOTA (divided across the services sharing that payout address), while transaction count and unique buyers stay whole operator-level figures, so sharing neither rewards nor spam-clones a service. A service on a network not yet measured, or a shared member whose probe has been failing, carries no traction term (the other weights are renormalized). Traction also requires real recent settlement: the term is 0 with no on-chain settlement in the last 30 UTC days, or when 30d volume is below a $10 floor (sub-floor volume is indistinguishable from dust and cannot move rank). Each recommendation also reports top_buyer_share_30d, the 30d volume share of the single largest buyer; a payout concentrated in one buyer is discounted (up to half the traction term when one buyer accounts for all of it), since one buyer is one relationship rather than broad demand. The response carries ranking_version, the scoring generation it was produced under, currently 3: it reflects the generation-2 compliance-signability cap plus the anti-wash traction rules above (the $10 volume floor, the single-buyer discount, and whole-integer buyer counts), so scores you stored under an earlier generation are not comparable with these. Optionally attach ecosystem facilitator-volume context separately.
get_facilitator_volumes(days, page, per_page, timeframe, include_chains, include_timeseries)- Get on-chain-verified settlement volume per x402 facilitator (the core x402-list metric). Returns USD settlement volume and transaction counts for today (UTC)/7d/30d/all-time, plus a `verification` flag ('on-chain' when volume has been observed on-chain, else 'listed'). Note: the fields named *_24h cover today (UTC) so far, not a trailing 24-hour window, so they reset at 00:00 UTC and read near zero just after midnight; prefer 7d for a stable recent-activity read. Optionally include a daily timeseries and per-chain breakdown. All volume figures are in US dollars. This is PER-FACILITATOR, not per-service.
get_service(slug, include_series)- Get full detail for one x402 service by slug: live status, uptime over 24h/7d/30d/90d, average response time, accepted networks and settlement asset, and every priced endpoint with its USD price. Use after search_x402_services to inspect a specific service. Prices are in US dollars; the per-endpoint `price` field is a raw on-chain atomic token amount, not dollars. Required: slug.
search_x402_services(q, page, sort, fields, status, network, category, per_page, signable, verified_only)- Search and filter the x402-list directory of services that accept x402 payments. Filter by free-text query, category, network, live status, and whether the service's last observed 402 envelope can be signed by a standard x402 client; sort by newest, uptime, cheapest, or endpoint count. Returns service summaries with price (USD), uptime, status, and verification. Prices are in US dollars.
Last successful function declaration observed on . Source: https://mcp.x402-list.com/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://mcp.x402-list.com/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 0 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-07-28 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 0 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Package downloads | 151 downloads | Package downloads from the npm registry in this window. Includes continuous integration runs, mirrors and automated installs, so it overstates the number of human users. | 2026-07-30 to 2026-08-05 | npm | |
| Latest published version | 0.4.2 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-28 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | MIT | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-07-28 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub | |
| mcp tools declared | 6 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | mcp.x402-list.com | |
| mcp endpoint status | ok | The server listed 6 functions when asked. | as of probe | mcp.x402-list.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json