Settled is a remote MCP server that gives an AI agent 18 tools, among them settled_check, settled_claim, settled_events. It answers at https://settled.tools/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 2 October 2026; the last check, on 17 November 2026, succeeded.
Check an x402 endpoint before your agent pays it: does it answer, what it charges, did it deliver
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
settled_check | Free: 25 calls/day per address, 300 with a payer record (free, keyed to your wallet), no daily cap with a pass. Check an x402 endpoint before paying it, from Settled’s index (cached up to 5 min): status, payability, latency, parsed price/ne Inputs: url, force, pass, payer_token |
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 for: Inputs: wallet, name, website, contact, docs, action |
settled_events | Free: 25 calls/day per address, 300 with a payer record, no daily cap with a pass. Recent changes worth acting on: venue verdict flips, new suspected honeypots, settlement-integrity changes, newest first. Use when: your agent runs on a sche Inputs: limit, pass, payer_token |
settled_find_endpoints | Free up to 50 calls/day per client (a pass allows 1,000). Live endpoints matching every word of q (in the URL, name, tags or description), best match first, then by quality, price, latency or payers; filter by network and max price; each wi Inputs: q, network, max_price, status, sort, limit |
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 an Inputs: url, pass |
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 whe Inputs: venue, rail, agent_access, min_reward, include_honeypots, sort |
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, self-cus |
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 p Inputs: url |
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 signed Inputs: url, force, pass, payer_token |
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 chain Inputs: url, tx, ok, signature |
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 selle Inputs: address, pass, payer_token |
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 endpoints. Inputs: limit, offset |
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_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 few Inputs: url |
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 and Inputs: document |
settled_watch | Paid: $2.00 USDC on Base over x402 inside MCP (the first call returns the payment requirements; @x402/mcp clients pay automatically). Buys 30 days of monitoring for one x402 endpoint: probed about every 15 minutes, with a signed alert whene Inputs: url, webhook, watch_id |
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 settl Inputs: watch_id, since, limit |
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 work. |
Every block below points at https://settled.tools/mcp. Pick your client and copy.
claude mcp add --transport http settled https://settled.tools/mcp
{
"mcpServers": {
"settled": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://settled.tools/mcp"]
}
}
}{
"mcpServers": {
"settled": {
"url": "https://settled.tools/mcp"
}
}
}{
"servers": {
"settled": {
"type": "http",
"url": "https://settled.tools/mcp"
}
}
}{
"context_servers": {
"settled": {
"url": "https://settled.tools/mcp"
}
}
}{
"mcpServers": {
"settled": {
"serverUrl": "https://settled.tools/mcp"
}
}
}{
"mcpServers": {
"settled": {
"url": "https://settled.tools/mcp"
}
}
}name: Settled
version: 0.0.1
schema: v1
mcpServers:
- name: Settled
type: streamable-http
url: https://settled.tools/mcp{
"mcpServers": {
"settled": {
"httpUrl": "https://settled.tools/mcp"
}
}
}{
"mcpServers": {
"settled": {
"type": "http",
"url": "https://settled.tools/mcp"
}
}
}{
"mcpServers": {
"settled": {
"url": "https://settled.tools/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fsettled.tools%2Fmcp&type=streamable_http&id=settled&name=Settled
It answered our last check on 17 November 2026 in 361 ms. Over 4 checks since 2 October 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by settled.tools and served from settled.tools, the vendor's own domain: https://settled.tools/mcp.
18, as returned by the server's own tools/list on 20 November 2026: settled_check, settled_claim, settled_events, settled_find_endpoints, settled_income_check, settled_income_listings, settled_income_venues, settled_peek, and 10 more.
It answered our last check on 17 November 2026 in 361 ms. Over 4 checks since 2 October 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://settled.tools/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: tools.settled. Endpoint host: settled.tools. ARD identifier: urn:air:tools.settled:mcp:settled.
First indexed 2 October 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.