Settled
REMOTE · SETTLED.TOOLS · 2 COMPONENTS · SCANNED OCT 8
Check x402 endpoints before your agent pays: payTo, paid test purchases, payee and buyer reports
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3415 tokens (~189/item across 18 items; 18 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Settled MCP server?
Settled is a hosted endpoint at https://settled.tools/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · settled.tools
claude mcp add --transport http tools-settled-settled 'https://settled.tools/mcp'
{
"mcpServers": {
"tools-settled-settled": {
"url": "https://settled.tools/mcp"
}
}
} {
"servers": {
"tools-settled-settled": {
"type": "http",
"url": "https://settled.tools/mcp"
}
}
} [mcp_servers.tools-settled-settled] url = "https://settled.tools/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tools-settled-settled": {
"type": "remote",
"url": "https://settled.tools/mcp",
"enabled": true
}
}
} openclaw mcp add tools-settled-settled --url 'https://settled.tools/mcp' --transport streamable-http
mcp_servers:
tools-settled-settled:
url: "https://settled.tools/mcp" {
"McpServers": {
"tools-settled-settled": {
"Transport": "http",
"Url": "https://settled.tools/mcp"
}
}
} assistant mcp add tools-settled-settled -t streamable-http -u 'https://settled.tools/mcp'
{
"mcpServers": {
"tools-settled-settled": {
"type": "http",
"url": "https://settled.tools/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 8 Oct 26 +1
- Server version: 0.9.45-discord → 0.9.60-buy functional
- 6 Oct 26 +8
- Authorization: fail → partial ▲ security
- Tool “settled_events” rewrote its description, which is the text the model reads security
- Tool “settled_find_endpoints” rewrote its description, which is the text the model reads security
- Tool “settled_income_check” rewrote its description, which is the text the model reads security
- Tool “settled_income_listings” rewrote its description, which is the text the model reads security
- Tool “settled_income_venues” rewrote its description, which is the text the model reads security
- Tool “settled_peek” rewrote its description, which is the text the model reads security
- Tool “settled_preflight” rewrote its description, which is the text the model reads security
- Tool “settled_report” rewrote its description, which is the text the model reads security
- Tool “settled_seller_reputation” rewrote its description, which is the text the model reads security
- Tool “settled_sellers” rewrote its description, which is the text the model reads security
- Tool “settled_status” rewrote its description, which is the text the model reads security
- Tool “settled_submit” rewrote its description, which is the text the model reads security
- Tool “settled_verify” rewrote its description, which is the text the model reads security
- Tool “settled_watch” rewrote its description, which is the text the model reads security
- Tool “settled_watch_alerts” rewrote its description, which is the text the model reads security
- Tool “settled_weekly_report” rewrote its description, which is the text the model reads security
- Tool “settled_check” rewrote its description, which is the text the model reads security
- Tool “settled_claim” rewrote its description, which is the text the model reads security
- Tool “settled_claim” no longer declares itself destructive security
- Schema quality: 145 → 189 ▼ functional
- Server version: 0.9.21-sellerwatch → 0.9.45-discord functional
- “settled_claim” reworded the description of “docs” cosmetic
- “settled_claim” reworded the description of “issued_at” cosmetic
- “settled_claim” reworded the description of “name” cosmetic
- “settled_claim” reworded the description of “signature” cosmetic
- “settled_claim” reworded the description of “wallet” cosmetic
- “settled_claim” reworded the description of “website” cosmetic
- “settled_income_listings” reworded the description of “min_reward” cosmetic
- “settled_income_listings” reworded the description of “rail” cosmetic
- “settled_income_listings” reworded the description of “venue” cosmetic
- “settled_report” reworded the description of “signature” cosmetic
- “settled_report” reworded the description of “tx” cosmetic
- “settled_seller_reputation” reworded the description of “address” cosmetic
- “settled_watch” reworded the description of “url” cosmetic
- “settled_watch” reworded the description of “watch_id” cosmetic
- “settled_watch” reworded the description of “webhook” cosmetic
- “settled_watch_alerts” reworded the description of “watch_id” cosmetic
- “settled_find_endpoints” reworded the description of “status” cosmetic
- “settled_claim” reworded the description of “contact” cosmetic
- 4 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.9.20-holds → 0.9.21-sellerwatch functional
- 3 Oct 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 8 Oct 2026 · Probed https://settled.tools/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=settled.tools | CN=WE1,O=Google Trust Services,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 5607d37fee256be50e0c798177c869a8 |
| SANs: settled.tools, www.settled.tools, *.www.settled.tools | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of settled.tools. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| tools. | present | 13831 | 8 | Verified |
| settled.tools. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://settled.tools/mcp | Verified | 200 | |
| http (plaintext) | http://settled.tools/mcp | HTTPS enforced | 301 | https://settled.tools/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
settled_check Check an x402 endpoint ~219
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 last real purchase, paying agents’ reports, seller claim, quality breakdown and risk flags. Use when: deciding whether to call an endpoint, and for routine re-checks. Not for: a fresh probe right now (settled_preflight) or searching (settled_find_endpoints). If status is unknown, call settled_submit; after paying, call settled_report.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | true to probe now instead of using the 5-minute cache; needs a pass |
| pass | string | – | Settled day pass token: lifts the free daily cap; or send it as the x-settled-pass header |
| url | string | yes | Full URL of the x402 endpoint, e.g. https://api.example.com/search |
| Name | Type | Req | Description |
|---|---|---|---|
| asset | – | – | Asset of the cheapest option |
| attestation | – | – | EIP-191 signature over the answer; verify it with settled_verify or any EVM library |
| attested_at | – | – | When Settled signed this answer (ISO 8601) |
| cached | – | – | Whether this came from Settled's 5-minute cache |
| checked_at | – | – | When this answer was built |
| delivery_receipt | – | – | The scout's last purchase, with its settlement transaction and checks (when the scout has bought it) |
| delivery_verified | – | – | Whether a real payment by Settled's scout came back with content |
| description | – | – | The listing's description |
| error | – | – | Present only when the call failed or needs another step: an error code such as pass_required, next to the fields that explain it |
| first_seen | – | – | When Settled first saw it |
| flags | – | – | Risk flags |
| http_status_last | – | – | HTTP status of the latest probe |
| last_delivery_at | – | – | When the scout last bought it |
| last_ok_at | – | – | When it last answered with a valid quote |
| last_probe_at | – | – | When Settled last probed it |
| latency_ms | – | – | Latency of the latest probe |
| network | – | – | Network of the cheapest option (CAIP-2) |
| network_name | – | – | Readable network name |
| onchain | – | – | Settlements and unique payers over the last 30 days |
| pay_to | – | – | The payTo Settled's probe sees; compare it with the quote you are about to pay |
| payability | – | – | Payability verdict and the verb that pays |
| payee | – | – | Whether the payTo has on-chain history |
| price_usd | – | – | Price per call in USD (cheapest option) |
| quality | – | – | Quality score breakdown |
| reports | – | – | Paying agents' reports |
| scheme | – | – | Payment scheme, e.g. exact |
| seller_claim | – | – | The seller's claim and profile, if claimed |
| service_name | – | – | The listing's service name |
| status | – | – | Endpoint status, e.g. live, degraded, dead, free, auth_gated, not_found or quote_invalid |
| url | – | – | The endpoint |
| x402_version | – | – | x402 version of the quote |
No examples provided.
settled_claim Claim your endpoints (sellers) ~333
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: buyers or third parties; only the payTo wallet can sign. Flow: call with wallet and profile to get message_to_sign and issued_at; sign with that wallet; call again with issued_at and signature. action=remove withdraws a claim (reversible by claiming again). Claims never change scores.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | claim (default) or remove to withdraw an existing claim |
| contact | string | – | How buyers can reach you, e.g. hello@example.com or @handle on X |
| docs | string | – | Your API documentation, as a full https URL |
| issued_at | string | – | The issued_at timestamp returned by the first call; send it back unchanged with the signature |
| name | string | – | Seller name to show on your endpoints, up to 80 characters, e.g. Acme Data |
| signature | string | – | Signature of message_to_sign by the wallet: EIP-191 personal_sign (0x hex) on Base, ed25519 (base58) on Solana; omit on the first call |
| wallet | string | yes | The payTo wallet your endpoints are paid to: 0x + 40 hex characters on Base, or a base58 address on Solana |
| website | string | – | Your website, as a full https URL |
| Name | Type | Req | Description |
|---|---|---|---|
| attestation | – | – | EIP-191 signature over the answer; verify it with settled_verify or any EVM library |
| attested_at | – | – | When Settled signed this answer (ISO 8601) |
| claimed | – | – | true once the claim is recorded |
| covers | – | – | The endpoints and hosts the claim covers |
| error | – | – | signature_required on the first call (sign message_to_sign and call again), or why the claim was refused |
| issued_at | – | – | Timestamp to send back with the signature |
| message_to_sign | – | – | The exact message to sign with the wallet |
| network | – | – | The wallet's network |
| note | – | – | What the claim does |
| profile | – | – | The published profile: name, website, contact, docs |
| removed | – | – | true once a claim is withdrawn |
| wallet | – | – | The wallet |
| would_cover | – | – | The endpoints and hosts the claim would cover |
No examples provided.
settled_events Change feed ~148
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 since last time. Not for: the full picture (settled_income_venues) or endpoint-level changes (settled_watch). Poll this instead of re-reading the scorecard.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many events to return, newest first, 1-200 (default 50) |
| pass | string | – | Settled day pass token: lifts the free daily cap; or send it as the x-settled-pass header |
| Name | Type | Req | Description |
|---|---|---|---|
| attestation | – | – | EIP-191 signature over the answer; verify it with settled_verify or any EVM library |
| attested_at | – | – | When Settled signed this answer (ISO 8601) |
| count | – | – | Number of events returned |
| error | – | – | Present only when the call failed or needs another step: an error code such as pass_required, next to the fields that explain it |
| events | – | – | Changes newest first: venue verdict flips, new suspected honeypots, settlement-integrity changes |
| generated_at | – | – | When this list was built |
No examples provided.
settled_find_endpoints Find live x402 endpoints ~287
Free up to 300 calls/day per client (a pass lifts the cap). 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 endpoint for a capability and want candidates that are live, payable and, where possible, proven to deliver. Not for: verifying one known URL (settled_check). After: run settled_check or settled_preflight on the one you pick before paying.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many endpoints to return, 1-50 (default 20) |
| max_price | number | – | Highest price per call in USD, e.g. 0.01 |
| network | string | – | Only endpoints on this network, as a CAIP-2 id, e.g. eip155:8453 for Base |
| pass | string | – | Settled day pass token: lifts the free daily cap; or send it as the x-settled-pass header |
| q | string | – | Keywords to match in endpoint names, descriptions and URLs, e.g. weather or gift cards |
| sort | string | – | Order of results: quality (default), price, latency or payers |
| status | string | – | Only endpoints with this status; live (default) or any for every status |
| Name | Type | Req | Description |
|---|---|---|---|
| attestation | – | – | EIP-191 signature over the answer; verify it with settled_verify or any EVM library |
| attested_at | – | – | When Settled signed this answer (ISO 8601) |
| count | – | – | Number of endpoints returned |
| error | – | – | Present only when the call failed or needs another step: an error code such as pass_required, next to the fields that explain it |
| filters | – | – | The filters applied |
| generated_at | – | – | When this list was built |
| items | – | – | Ranked endpoints, each with payability and delivery status |
No examples provided.
settled_income_check Honeypot / trust scan of one listing ~169
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 anomalies). Returns trust, label and every flag with its reason. Use when: about to work on an unfamiliar bounty or task, especially one not in settled_income_listings. Not for: x402 API endpoints (settled_check). Treat a suspected_honeypot label as do-not-work; a clean result is not a promise of payment.
| Name | Type | Req | Description |
|---|---|---|---|
| pass | string | – | Settled day pass token, if you did not send it as the x-settled-pass header |
| url | string | yes | URL of the bounty issue, repository or listing page to scan |
| Name | Type | Req | Description |
|---|---|---|---|
| attestation | – | – | EIP-191 signature over the answer; verify it with settled_verify or any EVM library |
| attested_at | – | – | When Settled signed this answer (ISO 8601) |
| error | – | – | Present only when the call failed or needs another step: an error code such as pass_required, next to the fields that explain it |
| flags | – | – | Every flag found, with its reason |
| indexed | – | – | Settled's listing for this URL, if it has one |
| label | – | – | verified_paying, unverified, gated, suspected_honeypot, dead or closed_to_agents |
| note | – | – | How to read the result |
| repo | – | – | Repository facts, for GitHub links |
| scanned_at | – | – | When the scan ran |
| source | – | – | What was scanned, e.g. page_text |
| trust | – | – | Trust score 0-100 |
| url | – | – | The page scanned |
No examples provided.
settled_income_listings Verified agent-income listings ~306
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 when: an agent is looking for work it is allowed to do. Not for: venue-level questions (settled_income_venues). Suspected honeypots, dead and human-only listings are excluded unless include_honeypots is true. Before working one, run settled_income_check on its URL.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_access | string | – | allowed (default) for listings agents may take, or any to include human-only ones |
| include_honeypots | boolean | – | true to include suspected honeypots and dead listings |
| limit | integer | – | How many listings to return, 1-50 (default 20) |
| min_reward | number | – | Smallest reward to include, in USD, e.g. 50 |
| pass | string | – | Settled day pass token, if you did not send it as the x-settled-pass header |
| rail | string | – | Only listings paid on this rail, e.g. usdc-base |
| sort | string | – | Order of results: trust (default), reward or recent |
| venue | string | – | Only listings from this venue, by its slug from settled_income_venues, e.g. superteam-earn |
| Name | Type | Req | Description |
|---|---|---|---|
| attestation | – | – | EIP-191 signature over the answer; verify it with settled_verify or any EVM library |
| attested_at | – | – | When Settled signed this answer (ISO 8601) |
| count | – | – | Number of listings returned |
| error | – | – | Present only when the call failed or needs another step: an error code such as pass_required, next to the fields that explain it |
| filters | – | – | The filters applied |
| generated_at | – | – | When this list was built |
| items | – | – | Open bounties and tasks with reward, agent access, gating, honeypot flags, trust score and the venue's payout record |
| label_vocabulary | – | – | The possible listing labels |
No examples provided.
settled_income_venues Which venues actually pay agents ~134
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-custody wallet), open listings and on-chain payouts. Use when: choosing where an agent should look for paid work, or checking whether a venue actually pays. Not for: individual listings (settled_income_listings) or x402 endpoints (settled_find_endpoints). Poll settled_events for changes instead of re-reading this.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| attestation | – | – | EIP-191 signature over the answer; verify it with settled_verify or any EVM library |
| attested_at | – | – | When Settled signed this answer (ISO 8601) |
| count | – | – | Number of venues |
| error | – | – | Present only when the call failed or needs another step: an error code such as pass_required, next to the fields that explain it |
| generated_at | – | – | When this list was built |
| venues | – | – | Each venue with its verdict, agent policy, gating, open listings and on-chain payouts |
| verdict_vocabulary | – | – | The possible verdicts |
No examples provided.
settled_peek Peek at an endpoint ~123
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 pay — use settled_check (free, fuller) or settled_preflight (paid, fresh). If the URL is unknown, call settled_submit, then check again later.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full URL of the x402 endpoint, e.g. https://api.example.com/search |
| Name | Type | Req | Description |
|---|---|---|---|
| attestation | – | – | EIP-191 signature over the answer; verify it with settled_verify or any EVM library |
| attested_at | – | – | When Settled signed this answer (ISO 8601) |
| detail | – | – | Where to get the full check |
| error | – | – | Present only when the call failed or needs another step: an error code such as pass_required, next to the fields that explain it |
| last_probe_at | – | – | When Settled last probed it |
| quality | – | – | Quality score 0-100 |
| seller_claimed | – | – | Whether the seller has claimed it |
| status | – | – | Endpoint status, e.g. live, degraded, dead, free, auth_gated, not_found or quote_invalid |
| url | – | – | The endpoint |
No examples provided.
settled_preflight Pre-spend check (pay / caution / avoid) ~209
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 answer with a recommendation (pay, caution or avoid) and reasons. Use when: real money is about to leave your wallet and settled_check was stale or not enough. Not for: browsing (settled_find_endpoints) or endpoints you already verified. After: compare pay_to and price with the 402 you receive, pay, then call settled_report.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | true to probe the endpoint now instead of reusing a result up to 5 minutes old |
| pass | string | – | Settled day pass token, if you did not send it as the x-settled-pass header |
| url | string | yes | Full URL of the x402 endpoint, e.g. https://api.example.com/search |
| Name | Type | Req | Description |
|---|---|---|---|
| attestation | – | – | EIP-191 signature over the answer; verify it with settled_verify or any EVM library |
| attested_at | – | – | When Settled signed this answer (ISO 8601) |
| cached | – | – | Whether the probe came from Settled's 5-minute cache |
| checked_at | – | – | When this check ran |
| delivery | – | – | The scout's last real purchase and whether it matched the listing |
| description | – | – | The listing's description |
| error | – | – | Present only when the call failed or needs another step: an error code such as pass_required, next to the fields that explain it |
| flags | – | – | Risk flags |
| honeypot | – | – | Honeypot scan of the listing text |
| liveness | – | – | Fresh probe results |
| onchain | – | – | Settlements and unique payers over the last 30 days |
| payability | – | – | Payability verdict and the verb that pays |
| payee | – | – | Whether the payTo exists on-chain, and the seller's other endpoints and settlement integrity |
| quality | – | – | Quality score breakdown |
| quote | – | – | The parsed 402 quote Settled sees: network, asset, price_usd, pay_to |
| reasons | – | – | Why, in plain words |
| recommendation | – | – | pay, caution or avoid |
| reports | – | – | Paying agents' reports |
| seller_claim | – | – | The seller's claim and profile, if claimed |
| url | – | – | The endpoint |
No examples provided.
settled_report Report whether a paid call worked ~243
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 chains. Flow: call without signature to get message_to_sign; sign it with the paying wallet (EIP-191 personal_sign); call again with signature. One report per payment, one vote per wallet per endpoint; Settled keeps only per-endpoint tallies.
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | true if the call delivered what you paid for, false if it did not |
| signature | string | – | EIP-191 personal_sign of message_to_sign by the wallet that paid (0x + 130 hex characters); omit on the first call to get message_to_sign |
| tx | string | yes | Transaction hash of your USDC payment to that endpoint on Base, from the last 30 days: 0x followed by 64 hex characters, e.g. 0x3f9a...c21e |
| url | string | yes | The x402 endpoint you paid |
| Name | Type | Req | Description |
|---|---|---|---|
| accepted | – | – | true once the report is recorded |
| attestation | – | – | EIP-191 signature over the answer; verify it with settled_verify or any EVM library |
| attested_at | – | – | When Settled signed this answer (ISO 8601) |
| error | – | – | signature_required when no signature was given (sign message_to_sign and call again), or why the report was refused |
| message_to_sign | – | – | The exact message to sign with the paying wallet |
| ok | – | – | Your verdict, as recorded |
| paid_at | – | – | When your payment was made |
| paid_usd | – | – | What your transaction paid the endpoint, in USD |
| privacy | – | – | What Settled keeps about you |
| reports | – | – | This endpoint's report tallies |
| url | – | – | The endpoint |
No examples provided.
settled_seller_reputation Seller reputation by payTo address ~161
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 seller and you want to judge the seller rather than one URL, or a payTo looks unfamiliar. Not for: a single endpoint’s status (settled_check). Input is the wallet address from a 402 quote.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The payTo address from a 402 quote: 0x followed by 40 hex characters (Base) |
| pass | string | – | Settled day pass token, if you did not send it as the x-settled-pass header |
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | – | The payTo address |
| attestation | – | – | EIP-191 signature over the answer; verify it with settled_verify or any EVM library |
| attested_at | – | – | When Settled signed this answer (ISO 8601) |
| claim | – | – | The seller's claim and profile, if claimed |
| dead | – | – | How many are dead |
| endpoints | – | – | Endpoints paid to it |
| error | – | – | Present only when the call failed or needs another step: an error code such as pass_required, next to the fields that explain it |
| first_seen | – | – | When Settled first saw one |
| flags | – | – | Seller flags such as clone_farm or quote_only |
| generated_at | – | – | When this answer was built |
| hosts | – | – | Hosts serving them |
| live | – | – | How many are live |
| onchain | – | – | On-chain settlements and unique payers |
| price_range_usd | – | – | Lowest and highest price |
| settlement_integrity | – | – | Whether paid activity looks organic or self-generated |
| top_endpoints | – | – | Its main endpoints |
No examples provided.
settled_sellers Claimed sellers ~132
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. Not for: judging an endpoint’s quality (claims never change scores; use settled_check). Paged: limit (max 50) and offset, with a total.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many sellers to return, 1-50 (default 25) |
| offset | integer | – | How many sellers to skip, for paging (default 0) |
| Name | Type | Req | Description |
|---|---|---|---|
| attestation | – | – | EIP-191 signature over the answer; verify it with settled_verify or any EVM library |
| attested_at | – | – | When Settled signed this answer (ISO 8601) |
| error | – | – | Present only when the call failed or needs another step: an error code such as pass_required, next to the fields that explain it |
| generated_at | – | – | When this list was built |
| limit | – | – | Page size used |
| note | – | – | What a claim proves |
| offset | – | – | Offset used |
| sellers | – | – | Claimed sellers with their profile and endpoint counts |
| total | – | – | Total claimed sellers |
No examples provided.
settled_status Settled index status ~70
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 (use settled_check). No input.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| attestation | – | – | EIP-191 signature over the answer; verify it with settled_verify or any EVM library |
| attested_at | – | – | When Settled signed this answer (ISO 8601) |
| by_status | – | – | Endpoint counts by status (live, dead, ...) |
| docs | – | – | Where the docs are |
| endpoints_probed | – | – | How many have been probed |
| endpoints_tracked | – | – | Number of x402 endpoints Settled tracks |
| error | – | – | Present only when the call failed or needs another step: an error code such as pass_required, next to the fields that explain it |
| last_probe_at | – | – | When the latest probe ran |
| live_share_of_probed | – | – | Percentage of probed endpoints that are live |
| mcp | – | – | This MCP server's URL |
| network | – | – | Network Settled's own paid routes settle on (CAIP-2) |
| onchain_ledger | – | – | Coverage of Settled's on-chain settlement ledger |
| prices_usd | – | – | Prices of Settled's paid routes, in USD |
| scout | – | – | Totals for the scout's paid test purchases |
| service | – | – | Always Settled |
| settlement_7d | – | – | USDC settled to tracked sellers in the last 7 days |
| sources | – | – | Discovery sources and how far each import has got |
| total_probes | – | – | Probes run so far |
| version | – | – | Settled's software version |
No examples provided.
settled_submit Submit an endpoint ~104
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 minutes, then call settled_check; the first probe runs within minutes. Idempotent.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full URL of an x402 endpoint to add to Settled's index |
| Name | Type | Req | Description |
|---|---|---|---|
| already_indexed | – | – | true when Settled already tracks it |
| attestation | – | – | EIP-191 signature over the answer; verify it with settled_verify or any EVM library |
| attested_at | – | – | When Settled signed this answer (ISO 8601) |
| error | – | – | Present only when the call failed or needs another step: an error code such as pass_required, next to the fields that explain it |
| hint | – | – | What to call next |
| next_check_at | – | – | When it will next be probed |
| ok | – | – | true when accepted |
| queued | – | – | true when queued for its first probe |
| status | – | – | Its current status, if already indexed |
No examples provided.
settled_verify Verify a signed Settled response ~112
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 you need to trust it. Not for: answers you just received directly over this server (already signed and fresh). Use the full response object, unchanged.
| Name | Type | Req | Description |
|---|---|---|---|
| document | object | yes | A complete signed Settled answer, including its attestation block |
| Name | Type | Req | Description |
|---|---|---|---|
| attested_at | – | – | When the document was signed |
| hash | – | – | Hash recomputed from the document |
| hash_matches | – | – | Whether it matches the signed hash |
| reason | – | – | Why it is not valid |
| signer_matches | – | – | Whether the two addresses match |
| signer_published | – | – | Settled's published signing address |
| signer_recovered | – | – | Address recovered from the signature |
| valid | – | – | true when the hash matches and the signer is Settled's published key |
No examples provided.
settled_watch Buy a Watchdog for an x402 endpoint ~223
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 whenever status, payability, price or payTo changes. Use when: your agent depends on one endpoint and must learn quickly if it changes. Not for: one-off checks (settled_check). Give url to start or watch_id to renew; give webhook to have alerts POSTed, else read them with settled_watch_alerts. Returns watch_id.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | – | The x402 endpoint to watch, e.g. https://api.example.com/search; required unless watch_id is given |
| watch_id | string | – | The watch_id of an existing watch to renew for 10 more days; give this or url, not both |
| webhook | string | – | https URL that receives each alert as a signed POST; omit to poll with settled_watch_alerts |
| Name | Type | Req | Description |
|---|---|---|---|
| accepts | – | – | Present when payment is needed: the x402 payment requirements; pay one and call again with the payment in _meta |
| alert_format | – | – | What an alert contains |
| alerts | – | – | URL of the alerts feed |
| attestation | – | – | EIP-191 signature over the answer; verify it with settled_verify or any EVM library |
| attested_at | – | – | When Settled signed this answer (ISO 8601) |
| baseline | – | – | The endpoint's state when the watch started |
| created_at | – | – | When the watch started |
| delivery | – | – | webhook or poll |
| error | – | – | Present only when the call failed or needs another step: an error code such as pass_required, next to the fields that explain it |
| expires_at | – | – | When it ends unless renewed |
| manage | – | – | URL of the watch |
| note | – | – | What happens next |
| renewed | – | – | true when this call renewed an existing watch |
| status | – | – | active or expired |
| url | – | – | The watched endpoint |
| watch_id | – | – | The watch's id: keep it to read alerts and to renew |
| webhook_host | – | – | Host the alerts are POSTed to, if a webhook was given |
| x402Version | – | – | Present when payment is needed: the x402 version of the requirements |
No examples provided.
settled_watch_alerts Read a Watchdog's alerts ~172
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_watch and did not give a webhook. Not for: endpoints without a watch (use settled_check). Poll it whenever your agent runs; the endpoint is probed about every 15 minutes.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Most alerts to return, 1-100 (default 50) |
| since | integer | – | Return alerts with an id above this; pass next_since from your last call, or 0 for all |
| watch_id | string | yes | The watch_id returned by settled_watch when the Watchdog was bought |
| Name | Type | Req | Description |
|---|---|---|---|
| alerts | – | – | Alerts since the given id, oldest first: each change to status, payability, price or payTo |
| attestation | – | – | EIP-191 signature over the answer; verify it with settled_verify or any EVM library |
| attested_at | – | – | When Settled signed this answer (ISO 8601) |
| delivery | – | – | webhook or poll |
| endpoint_now | – | – | The endpoint's state now: status, payability, price, payTo, last probe |
| error | – | – | Present only when the call failed or needs another step: an error code such as pass_required, next to the fields that explain it |
| expires_at | – | – | When the watch ends unless renewed |
| how | – | – | How to poll |
| more | – | – | true when more alerts are waiting |
| next_since | – | – | Pass this as since on your next call |
| status | – | – | active or expired |
| url | – | – | The watched endpoint |
| watch_id | – | – | The watch |
No examples provided.
settled_weekly_report Weekly Agent Income Report ~92
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. Not for: live numbers (settled_status, settled_income_venues). Published Mondays; the window and ledger coverage are in the body.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| attestation | – | – | EIP-191 signature over the answer; verify it with settled_verify or any EVM library |
| attested_at | – | – | When Settled signed this answer (ISO 8601) |
| endpoints | – | – | x402 index health |
| error | – | – | Present only when the call failed or needs another step: an error code such as pass_required, next to the fields that explain it |
| generated_at | – | – | When it was built |
| key | – | – | The report's key, e.g. weekly:2026-W40 |
| kind | – | – | Always weekly |
| links | – | – | Where the report is published |
| listings | – | – | Listings and honeypots |
| settlements | – | – | On-chain settlement totals |
| venues | – | – | Venues that paid agents on-chain |
| week | – | – | ISO week of the report |
| window | – | – | The 7 days covered |
No examples provided.
What is the Settled MCP server?
Settled is an MCP server listed in the public MCP registry as tools.settled/settled. Check x402 endpoints before your agent pays: payTo, paid test purchases, payee and buyer reports. This page covers its hosted endpoint (https://settled.tools/mcp).
Is the Settled MCP server safe to use?
Settled scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Settled MCP server expose?
Settled exposes 18 tools: settled_status, settled_peek, settled_submit, settled_report, settled_sellers, and 13 more. Their descriptions and schemas cost roughly 3,237 tokens of context every time the server is loaded.
Does the Settled MCP server require authentication?
No. We connected to Settled without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Settled MCP server still maintained?
Settled is still listed as active in the MCP registry. We last reached this channel on 8 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.