paidfor
REMOTE · MCP.PAIDFOR.DEV · 2 COMPONENTS
Check an x402 seller before paying: verdict, failure rate and evidence from paid calls on Base.
Available components
Last scanned (16 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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 Security74
- 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 966 tokens (~241/item across 4 items; 4 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 Management20
- Stability observed for 6 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 30 Oct 26 70
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 5 Nov 2026 · Probed https://mcp.paidfor.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.paidfor.dev | CN=Cloudflare TLS Issuing ECC CA 3,O=SSL Corporation,C=US | 28 Oct 2026 | 26 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 75fd2170435065a891858d03b9c5c0a2 |
| SANs: mcp.paidfor.dev | ||||||
| CN=Cloudflare TLS Issuing ECC CA 3,O=SSL Corporation,C=US (CA) | CN=SSL.com TLS Transit ECC CA R2,O=SSL Corporation,C=US | 29 May 2025 | 27 May 2035 | ECDSA 256 | ECDSA-SHA384 | 31eee88afb87cd9ef8336604743f9b27 |
| CN=SSL.com TLS Transit ECC CA R2,O=SSL Corporation,C=US (CA) | CN=SSL.com TLS ECC Root CA 2022,O=SSL Corporation,C=US | 21 Oct 2022 | 17 Oct 2037 | ECDSA 384 | ECDSA-SHA384 | 604d8af8d00ba8748b955853172c5f2e |
| CN=SSL.com TLS ECC Root CA 2022,O=SSL Corporation,C=US (CA) | CN=AAA Certificate Services,O=Comodo CA Limited,L=Salford,ST=Greater Manchester,C=GB | 1 Aug 2025 | 31 Dec 2028 | ECDSA 384 | SHA256-RSA | 173dca60ea9f8e1026dafcd72810e48e |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.paidfor.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| paidfor.dev. | No DS | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.paidfor.dev/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.paidfor.dev/mcp | HTTPS enforced | 301 | https://mcp.paidfor.dev/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 →
check_x402_seller Check an x402 seller before paying ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | x402 resource URL, or a bare seller domain such as api.example.com |
| Name | Type | Req | Description |
|---|---|---|---|
| candidate | – | yes | Queue state for a seller not yet measured; null otherwise |
| evidence_url | string|null | yes | – |
| generated_at | string | yes | When the index was generated |
| host | string|null | yes | – |
| methodology_url | string | yes | – |
| probe | – | yes | Hourly unpaid probes of the seller's 402 quote; null when not probed |
| resource | – | yes | Measured paid calls to this exact URL; null when not measured |
| seller | – | yes | Measured paid calls to this seller; null when the study never paid it |
| seller_url | string|null | yes | – |
| verdict | string | yes | – |
| verdict_text | string | yes | One sentence to act on, with the evidence link |
No examples provided.
list_reliable_sellers List reliable pay-per-call API sellers ~145
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Kind of service to list sellers for; omit to list every kind |
| limit | integer | – | How many sellers to return, most-called first; 50 when omitted |
| Name | Type | Req | Description |
|---|---|---|---|
| generated_at | string | yes | When the index was generated |
| sellers | array | yes | – |
No examples provided.
recent_changes Recent changes to x402 sellers ~167
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).
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | – | Seller to show changes for, as a bare domain such as api.example.com; omit for every seller |
| since | string | – | Show only changes after this time, in ISO 8601 (such as the generated_at of a verdict you already have); omit for the latest changes |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | Matching changes the index returned (it caps the feed at the newest 500); events holds at most the newest 100 |
| events | array | yes | – |
No examples provided.
report_x402_payment Report an x402 payment outcome ~221
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.
| Name | Type | Req | Description |
|---|---|---|---|
| http_status | integer | – | The HTTP status of the paid response, if known |
| outcome | string | yes | What came back: ok (the response was usable for its purpose), non_delivery (an error, an empty body or nothing usable after paying), wrong_goods (a usable response, but not what was asked for), overc… |
| quoted_usdc | – | – | The price the 402 quoted, in USDC, if known |
| tx_hash | string | yes | The settlement transaction hash on Base: the `transaction` field of the seller's PAYMENT-RESPONSE or X-PAYMENT-RESPONSE header (base64 JSON) |
| url | string | yes | The x402 resource URL that was paid for |
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usdc | string|null | yes | USDC moved, read from the transaction |
| pay_to | string|null | yes | – |
| payer | string|null | yes | The paying wallet, read from the transaction (never from the report) |
| reason | string|null | yes | Why a report was rejected; null otherwise |
| sentence | string | yes | The result in one sentence |
| status | string | yes | verified: counted once folded in (minutes); pending: checked on Base again within minutes; duplicate: this transaction was already reported; rejected: not counted, see reason |
| verification_url | string|null | yes | – |
No examples provided.
How do I install the paidfor MCP server?
paidfor is a hosted endpoint at https://mcp.paidfor.dev/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 · mcp.paidfor.dev
claude mcp add --transport http dev-paidfor-paidfor 'https://mcp.paidfor.dev/mcp'
What is the paidfor MCP server?
paidfor is an MCP server listed in the public MCP registry as dev.paidfor/paidfor. Check an x402 seller before paying: verdict, failure rate and evidence from paid calls on Base. This page covers its hosted endpoint (https://mcp.paidfor.dev/mcp).
Is the paidfor MCP server safe to use?
paidfor scores 73 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 paidfor MCP server expose?
paidfor exposes 4 tools: check_x402_seller, list_reliable_sellers, recent_changes, report_x402_payment. Their descriptions and schemas cost roughly 669 tokens of context every time the server is loaded.
Does the paidfor MCP server require authentication?
No. We connected to paidfor without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the paidfor MCP server still maintained?
paidfor is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the paidfor MCP server?
VerifyMCP ran 13 checks on paidfor, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.