com.x402-list/x402-list-mcp

Est-ce que com.x402-list/x402-list-mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.x402-list/x402-list-mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 7 outils

• x402_assess_services≈ 870 tokens

  Call this when the free signals have run out: you hold 2 to 8 finalists from x402_search_services or x402_find_best_service, their stored fields do not separate them for YOUR stated need, and choosing wrong costs more than a quarter. It buys one fresh AI assessment reasoned against your question, not a cached grade; reading an already-computed assessment stays free via x402_get_service. Price: a one-time $0.25 USDC on Base, over two calls. Call once WITHOUT payment_signature_b64 to receive the x402 payment challenge verbatim (accepts[], amount, payTo, and a base64 PAYMENT-REQUIRED header); sign accepts[0] client-side with your own wallet; call again with the SAME question and services plus payment_signature_b64 to receive the report and a base64 PAYMENT-RESPONSE settlement receipt. This server holds no keys, never signs and never settles: it only relays the challenge. Optionally add probe { slug, endpoint_path? } to have one listed service paid and called for real and its answer analyzed: the challenge is then priced at $0.25 plus that endpoint price X, and the report gains a probe_report block with a verdict and truncated extracts, never the verbatim third-party body. When live probing is not armed the probe is ignored. Caveats: read the amount to sign from accepts[0].amount, never from a fixed figure, since a probe changes it; probe fees are non-refundable whatever the verdict; if the fresh run cannot be produced the server answers before settling, so you are never charged for nothing; there is no refund. Prices are US dollars.

  Paramètres, retour & exemple (4)

  Paramètres

  • probe · object · optionnel
    Optional live-probe request: pay one listed service for real and analyze what it returns. When the server has probing armed the price becomes $0.25 plus that endpoint price X (non-refundable); the report gains a probe_report block with a verdict and truncated extracts, never the verbatim third-party body. Ignored when probing is not armed.
  • question · string · requis
    The need to assess the shortlist against (1 to 1000 characters).
  • services · array · requis
    Service slugs to compare for the need (1 to 8; find them with x402_search_services or x402_find_best_service).
  • payment_signature_b64 · string · optionnel
    Base64 PAYMENT-SIGNATURE for the x402 payment, produced by signing the accepts[0] challenge client-side. Omit on the first call to receive the challenge; set it on the retry to run the paid assessment.

  Exemple d'appel

  {"name": "x402_assess_services", "arguments": {"question": "texte", "services": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• x402_change_events≈ 502 tokens

  Call this before you trust anything you cached about a service, and right after a payment failed for no obvious reason: the monitor's log of what moved under you. Returns payTo, price and 402-schema changes observed on listed services, most recent first, in exactly three event types (payto_changed, price_changed, schema_changed). Filter with service (the slug), type, and days (1 to 365, default 90). Caveats: prices here are atomic token amounts, never dollars, and every payTo is masked by design, so the feed reports THAT the payout address changed, never the address. Free and read-only.

  Paramètres, retour & exemple (5)

  Paramètres

  • days · integer · optionnel
    Lookback window in days, 1 to 365 (default 90). Events older than the window are not in the feed.
  • page · integer · optionnel
    1-based page index into the filtered event set (see total_pages).
  • type · string · optionnel · payto_changed | price_changed | schema_changed
    Restrict to one kind of change: 'payto_changed' (the payout address set changed), 'price_changed' (at least one endpoint's price changed), 'schema_changed' (the 402 envelope gained or lost accepts entries or priced endpoints). Omit for all three.
  • service · string · optionnel
    Service slug to restrict the feed to, e.g. 'exa' (the same slug x402_get_service takes). Omit for changes across every listed service.
  • per_page · integer · optionnel
    Events per page, 1 to 100 (default 25). Each event carries the full before/after envelope snapshots, so a large page is heavy.

  Exemple d'appel

  {"name": "x402_change_events", "arguments": {"days": 1, "page": 1, "type": "payto_changed", "service": "texte", "per_page": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• x402_check_health≈ 311 tokens

  Call this before you send a payment, or right after a call unexpectedly failed: is this service up right now. With no slug, the directory snapshot: five status counts across the directory (include_services=true attaches every row). With a slug: that service's status, its 24h/7d/30d/90d uptime windows, response time, consecutive failures, daily snapshots. No money fields.

  Paramètres, retour & exemple (3)

  Paramètres

  • slug · string · optionnel
    Service slug for a single-service health report. Omit for the whole directory.
  • uptime_period · string · optionnel · 24h | 7d | 30d | 90d
    Daily uptime snapshot window for single-service mode.
  • include_services · boolean · optionnel
    Directory mode only (no slug): if true, also attach the full per-service status array. Off by default so a directory health check returns just the five status counts, not every service.

  Exemple d'appel

  {"name": "x402_check_health", "arguments": {"slug": "texte", "uptime_period": "24h", "include_services": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• x402_facilitator_volumes≈ 432 tokens

  Call this when the question is about the rail rather than the service: which x402 facilitator actually settles money, and how much. Returns on-chain-verified settlement volume and transaction counts per facilitator for today (UTC), 7d, 30d and all-time, plus a verification flag ('on-chain' once volume has been observed on-chain, else 'listed'), across more than 30 facilitators. Optional daily timeseries (up to 90 days) and per-chain breakdown. Volume is decimal USD. Caveats: PER-FACILITATOR, never per-service; the *_24h fields cover today (UTC) so far, not a trailing 24 hours, and reset at 00:00 UTC, so prefer 7d.

  Paramètres, retour & exemple (6)

  Paramètres

  • days · integer · optionnel
    Length of the timeseries in days (only used when include_timeseries is true).
  • page · integer · optionnel
  • per_page · integer · optionnel
  • timeframe · string · optionnel · 24h | 7d | 30d | all
    Drives the sort order of the returned facilitators. '24h' sorts by today (UTC) so far, not by a trailing 24-hour window.
  • include_chains · boolean · optionnel
    Include a per-chain (network/asset) volume breakdown per facilitator.
  • include_timeseries · boolean · optionnel
    Include a daily volume_usd / tx_count series per facilitator.

  Exemple d'appel

  {"name": "x402_facilitator_volumes", "arguments": {"days": 1, "page": 1, "per_page": 1, "timeframe": "24h", "include_chains": true, "include_timeseries": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• x402_find_best_service≈ 614 tokens

  Call this when you have a need in words and want one service to call rather than a list to read: it is the free ranking step between searching and paying. Pass the need as q, plus any category, network, price cap or verification requirement, and get up to 20 ranked recommendations with the basis each one placed on. Ranking is mostly per-service reliability (live status, verification, uptime, response time), x402 compliance, and price in USD, with a small (about 10%) weight on measured on-chain settlement traction that can never dominate those three. The response carries ranking_version (currently 3), need_blind_ranking (true when no q was given, so the order is global quality rather than your need), and a units map holding every scoring caveat in full: the compliance cap, the pro-quota rule for shared payout addresses, renormalization, the $10 volume floor, and the single-buyer discount. Read units before comparing scores across generations.

  Paramètres, retour & exemple (8)

  Paramètres

  • q · string · optionnel
    Free-text need description to match against name/description.
  • limit · integer · optionnel
    How many ranked recommendations to return.
  • prefer · string · optionnel · balanced | cheapest | fastest | most_reliable
    Tie-breaking emphasis for the ranking weights.
  • network · string · optionnel
    Required network name or abbreviation, e.g. 'Base' or 'BSE'; any network code returned by /api/v1/networks is accepted.
  • category · string · optionnel
    Desired service category.
  • max_price_usd · number · optionnel
    Cap on min_price_usd in US dollars; cheaper or equal passes.
  • require_verified · boolean · optionnel
    If true, only verified services are eligible.
  • include_facilitator_context · boolean · optionnel
    If true, also return top facilitators by 7d settlement volume as separate ecosystem context (NOT per-service).

  Exemple d'appel

  {"name": "x402_find_best_service", "arguments": {"q": "texte", "limit": 1, "prefer": "balanced", "network": "texte", "category": "texte", "max_price_usd": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• x402_get_service≈ 339 tokens

  Call this once you hold a slug and are deciding whether to commit to that service: the full record behind a directory row. Live status, uptime over 24h/7d/30d/90d, average response time, networks and settlement asset, every priced endpoint, and the assessment block. When the live 402 of an endpoint asks to be paid at a different address than the listed pay_to and the change is still in review, the response carries top-level warnings and endpoints[].pay_to_divergence. include_series=true adds 90 daily points of on-chain volume and distinct buyers. Read the units map in the response: the per-endpoint price field is atomic token units, not dollars.

  Paramètres, retour & exemple (2)

  Paramètres

  • slug · string · requis
    Service slug, e.g. 'my-api'.
  • include_series · boolean · optionnel
    If true, also attach this service's daily on-chain series under `series` (settlement volume and distinct buyers, one point per UTC day over the most recent 90 days, oldest first). Off by default to keep the response small.

  Exemple d'appel

  {"name": "x402_get_service", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• x402_search_services≈ 782 tokens

  Your first call when you do not know which x402 service exists for a job: it narrows the directory of listed services to candidates. Filter by free-text query, category, network, live status, and whether the last observed 402 envelope is signable by a standard x402 client; sort by newest, uptime, cheapest, or endpoints. Returns up to 100 compact summaries a page: price in decimal USD, uptime, status, verification. Then x402_get_service for the full record.

  Paramètres, retour & exemple (10)

  Paramètres

  • q · string · optionnel
    Free-text search across name, description, category, base_url.
  • page · integer · optionnel
    1-based page index into the filtered result set (see meta.total_pages).
  • sort · string · optionnel · newest | uptime | cheapest | endpoints
    Server-side sort order.
  • fields · string · optionnel · compact | full
    Response detail: 'compact' (default) = lean summaries (identity, price, status, uptime, verification, networks, compliance grade), 'full' = every field including the per-service assessment block. Compact keeps a directory sweep small enough to not truncate.
  • status · string · optionnel · online | degraded | offline | unknown | all
    Filter by live monitoring status.
  • network · string · optionnel
    Network name or abbreviation, e.g. 'Base' or 'BSE'; any network code returned by /api/v1/networks is accepted. Omit for all.
  • category · string · optionnel
    Exact category name (see categories context). Omit for all.
  • per_page · integer · optionnel
    Services per page, 1 to 100 (default 25). Higher values return larger results; with fields='full' a large page can be very heavy, so prefer compact when raising it.
  • signable · boolean · optionnel
    Filter on the signability of the last observed 402 envelope: true = no EVM route of the service was observed missing the EIP-712 domain parameters (extra.name and extra.version) that a standard x402 client requires in order to sign a payment, false = at least one such route was observed. It describes the payment envelope on the wire, not the merit of the service. A service whose latest assessment has not measured that check yet matches NEITHER value, so omit this parameter to include it. Filtered server-side, so the result total covers the whole filtered set.
  • verified_only · boolean · optionnel
    If true, return only verified services. Filtered server-side, so the result total covers the whole verified set, not just this page.

  Exemple d'appel

  {"name": "x402_search_services", "arguments": {"q": "texte", "page": 1, "sort": "newest", "fields": "compact", "status": "online", "network": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.x402-list.com/mcp