paidfor MCP Server

by sarmadahsan Your server? Claim it

answering

paidfor is answering right now. Last checked 8 min ago. It exposes 4 tools.

Check an x402 seller before paying: verdict, failure rate and evidence from paid calls on Base.

Uptime history 4 days of history

4 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

700 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check paidfor every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add paidfor --transport http https://mcp.paidfor.dev/mcp

Settings → Connectors → Add custom connector, then paste this address

https://mcp.paidfor.dev/mcp

~/.codex/config.toml

[mcp_servers.paidfor]
url = "https://mcp.paidfor.dev/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "paidfor": {
      "url": "https://mcp.paidfor.dev/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "paidfor": {
      "type": "http",
      "url": "https://mcp.paidfor.dev/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

recent

recent_changes

Call this when the user asks what changed, or before relying on a verdict older than a day. Returns recent changes, newest first: verdict changes, new failures by type, moved quotes, changed pay-to addresses, sellers added or reaching 30 paid calls, published seller replies, the operator-reported series maturing or disagreeing with ours. Each change has its time, type, seller domain, seller page and type-specific details (for example the old and new quote).

reliable

list_reliable_sellers

Call this when choosing among sellers for a task, or when the user asks for a safe or reliable API. Returns sellers with zero failures across at least 30 paid calls, most-called first. For each: domain, category, paid-call count, the 95% upper bound on its failure rate, median quoted price in USDC, USDC paid to it in the last 30 days, when it was last seen, and its paidfor seller page.

report

report_x402_payment

After your agent pays an x402 seller with any wallet, report what came back. Needs the resource URL, the settlement transaction hash and the outcome. Free, no account, no key; the report counts only with on-chain proof.

x402

check_x402_seller

Call this before any x402 payment, before retrying a request that answered HTTP 402, or whenever the user is about to buy an API call with USDC on Base or names an API they intend to pay per call. Returns a verdict (avoid, caution, ok, unknown), one sentence to act on, the seller's paid-call count and failure rate with a 95% interval, listed price, modal quote and max overcharge ratio when known, and links to the seller page and raw evidence.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.paidfor.dev/mcp	streamable-http	answering	392 ms	8 min ago

Alternatives to paidfor

same job, measured the same way

paidfor

by paidfor

Check an x402 seller before paying: verdict, failure rate and evidence from paid calls on Base.

1 081 installs/wk 4 tools answering

Lumi Verdict: check an x402 seller before paying

by cypher-osiris

One signed label before paying an x402 seller, from Lumi's test-buys on XRPL, Base and Stellar

367 installs/wk local only

Verdix address risk

by verdixapi

Check an EVM address on Base before sending funds: safe/caution/danger. Pays per call via x402.

78 installs/wk local only

ProvenPaid

by provenpaid

Check an x402 endpoint before your agent pays it: challenge validity and on-chain payer evidence.

103 installs/wk local only

Lumi Trades: x402 seller checks and test-buys

by cypher-osiris

Free signed allow/warn/block before paying x402 sellers; test-buys on XRPL, Base and Stellar

2 764 installs/wk 11 tools answering

BotsRated (beta)

by botsrated

Signed checks of x402 sellers on Base and remote MCP servers, before your agent pays.

9 tools answering

Creator Desk Commerce Completion Verify

by creatordeskai-prog

Evidence-based commerce completion checks for agents. x402 paid calls and free standard metadata.

2 tools answering

agent-audit + page-read (x402)

by agent-audit-x402

Pay-per-call page reader, quote check, link check and x402 seller audit. USDC on Base via x402.

7 tools answering

paidfor — questions

Answers built from our own checks of this server.

What can paidfor do?

It exposes 4 tools, read directly from the server on our last check. Among them: check_x402_seller, list_reliable_sellers, recent_changes, report_x402_payment. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is paidfor working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 700 ms. The bar chart above shows every period we have measured.

How do I connect paidfor?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does paidfor need an API key?

No. paidfor completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is paidfor?

It answers our handshake in 700 ms on average, which is faster than 13% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.