Saltar al contenido
Logo de Settled

Servidor MCP de Settled

Qué servidores del registro oficial de MCP son de Settled, si responden y qué ofrecen. Un programa comprobó cada dato; nada está copiado de la página del producto.

leído el 2026-10-15

← Volver a Settled

De quién es el servidor
  • Nombre en el registrotools.settled/settledverificado en el registro MCP

El nombre en el registro está bajo settled.tools. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

Cuando le preguntamoscomprobado el 2026-10-15
  • Estadorespondecomprobado el 2026-10-15
  • Herramientas18
  • El servidor se llamasettled
  • Versión del servidor0.9.88-count-note
  • Versión del protocolo2025-06-18

El 2026-10-15 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 68 ms.

Herramientas que ofrece18 herramientas · leído el 2026-10-15
  • settled_status

    Free. Size and freshness of the x402 endpoint index and the on-chain ledger. Use when: you need to know how current Settled’s data is, or what the paid routes cost, before relying on any other tool. Not for: looking up a specific endpoint…

  • settled_peek

    Free, rate-limited. Coarse status and quality score for one x402 endpoint URL, from the index only (no fresh probe). Use when: you only need a quick yes/no on whether Settled knows the URL and its last status. Not for: deciding whether to…

  • settled_submit

    Free, rate-limited. Queue an x402 endpoint URL for indexing. Use when: settled_check or settled_peek reports the URL as unknown or not indexed. Not for: URLs already indexed (it just returns their status) or non-x402 URLs. After: wait a…

  • settled_report

    Free. After paying an x402 endpoint on Base, tell Settled whether you got what you paid for. Use when: your agent has just made a real USDC payment and has the transaction hash. Not for: endpoints you did not pay, or payments on other…

  • settled_sellers

    Free. Sellers who proved control of the wallet their x402 endpoints are paid to, with their published profile and endpoint counts. Use when: you want a contact or docs link for a seller, or to see which sellers stand behind their…

  • settled_claim

    Free. For sellers: claim every x402 endpoint paid to your wallet with one signature, on every host, so your name, website, contact and docs show next to them (plus a 10-day Seller Watch trial). Use when: you operate x402 endpoints. Not…

  • settled_preflight

    Pass required. The call to make right before paying an unfamiliar x402 endpoint: a fresh probe, parsed quote, payability, payTo on-chain history, seller integrity, the scout’s real-payment delivery result and a honeypot scan, as one…

  • settled_check

    Free up to 300 calls/day per client (a pass lifts the cap). Check an x402 endpoint before paying it, from Settled’s index (cached up to 5 min): status, payability, latency, parsed price/network/payTo, payee on-chain history, the scout’s…

  • settled_find_endpoints

    Free up to 50 calls/day per client (a pass allows 1,000). Ranked live endpoints by keyword, network and max price (sort by quality, price, latency or payers), each with payability and delivery verification. Use when: you need an x402…

  • settled_seller_reputation

    Pass required. Everything Settled knows about one payTo address: the endpoints it is paid for, live/dead counts, price range, clone-farm and quote-only flags, on-chain settlements and unique payers. Use when: several endpoints share a…

  • settled_income_venues

    Free. Scorecard of bounty boards, task markets, audit contests and the x402 sell-side: verdict (paying / paying small / measuring / no payouts seen / unmeasured / closed to agents / defunct), agent policy, gating (KYC, human claim…

  • settled_income_listings

    Pass required. Open bounties and tasks an agent can actually work on, from sanctioned venue APIs, each with reward, agent-access policy, gating, honeypot scan flags with reasons, a trust score and the venue’s on-chain payout record. Use…

  • settled_income_check

    Pass required. Fetches a bounty issue, repository or listing page and scans it for patterns used to bait agents (hidden HTML-comment instructions, prompt injection, credential requests, fork/star anomalies, dead or archived repos, reward…

  • settled_events

    Free up to 300 calls/day per client. Recent changes worth acting on: venue verdict flips, new suspected honeypots, settlement-integrity changes, newest first. Use when: your agent runs on a schedule and wants to react to what changed…

  • settled_watch

    Paid: $1.00 USDC on Base over x402 inside MCP (the first call returns the payment requirements; @x402/mcp clients pay automatically). Buys 10 days of monitoring for one x402 endpoint: probed about every 15 minutes, with a signed alert…

  • settled_watch_alerts

    Free. Everything a Watchdog has recorded for its endpoint since a given alert id: each change to status, payability, price or payTo, the endpoint’s state now, and next_since to pass on the next call. Use when: you created a watch with…

  • settled_weekly_report

    Free. The latest published Agent Income Report as JSON: which venues paid agents on-chain, worker wallets, honeypots flagged, x402 index health. Use when: you want the week’s summary, for a digest or a decision about where to look for…

  • settled_verify

    Free. Pass any signed Settled response (attestation included) to recompute its hash and recover the signer; tells you whether it is authentic and unaltered. Use when: a Settled answer reached you through a third party, a cache or a log…

Cómo conectar

Añade el servidor a la configuración de tu cliente MCP. Claude Desktop, Cursor y la mayoría de los demás clientes leen este formato:

{
  "mcpServers": {
    "settled": {
      "type": "http",
      "url": "https://settled.tools/mcp"
    }
  }
}

También se distribuye por: npm

Especificación OpenAPI

51 rutas, leído el 2026-10-15. Abrir la especificación ↗

Cada línea es algo que un programa encontró al buscar: la entrada del registro, la respuesta del propio servidor, una especificación que se puede leer. Si falta una línea, es que no la encontramos, no que no exista.