Skip to content
paidfor logo

paidfor MCP server

Which MCP servers are paidfor's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-30

← Back to paidfor

Whose server it is
  • Registry namedev.paidfor/paidforverified in the MCP registry

The registry name sits under paidfor.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-30
  • Stateanswerschecked 2026-10-30
  • Tools4
  • Server calls itselfpaidfor
  • Server version0.4.0
  • Protocol version2025-06-18

On 2026-10-30 the server answered initialize and tools/list without a sign-in. First answer in 613 ms.

Should an agent connect itNot proven either way yet
  • Its tools do Check an x402 seller's failure record before paying; Report failed paid calls to update seller verdicts, but not Watch sellers and get emailed when verdicts change.
  • Checked on 3 of the 7 days it takes to judge reliability.

Once connected

  • For "Check an x402 seller's failure record before paying", the likely first call is check_x402_seller.
  • For "Report failed paid calls to update seller verdicts", the likely first call is report_x402_payment.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 3, the first on 2026-10-30
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
  • What an agent can do with it2 of 3 use cases
  • Use500 npm downloads a week
  • Answeredmeasuring3 of the 7 daily checks it takes to print a share
  • Median first answer537 ms
  • Space in an agent's context≈ 985 tokensthe definitions of all its tools (4), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results4 of 4 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • can do · Check an x402 seller's failure record before paying
  • cannot · Watch sellers and get emailed when verdicts change
  • can do · Report failed paid calls to update seller verdicts

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers4 tools · read 2026-10-30
  • 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…

  • 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%…

  • 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…

  • 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.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Add it

Claude Code, in a terminal

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

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.paidfor.dev/mcp as a custom connector in the settings.

Also shipped through: npm

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.