paidfor MCP server
dev.paidfor/paidforpaidfor.devstreamable-httpv0.7.7Scanned
Check an x402 seller before paying: verdict, failure rate and evidence from paid calls on Base.
4 tools: 1 do something that can't be undone and 3 change things.
- Reads private data · 0
- Reads text others write · 4
- Can send data out · 2
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the paidfor MCP server can do
The paidfor MCP server is published by paidfor.dev, a domain the MCP Registry verified. It has 4 tools. It can do things that cannot be undone, such as sending, paying or publishing (report_x402_payment) and create or change data (3 tools: check_x402_seller, list_reliable_sellers and recent_changes), but cannot delete data. None of its tools only reads.
4 tools bring in text other people can write (check_x402_seller, list_reliable_sellers, recent_changes and 1 more); 2 tools can send data out of your system (check_x402_seller and report_x402_payment).
The fixed checks matched 3 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 20, 2026, version 0.7.7.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Can't be undone 1Claude Code: ask
report_x402_paymentAfter your agent pays an x402 seller with any wallet, report what came back.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "report_x402_payment" says "payment": a word that usually means money moves, which cannot be taken back.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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; the report counts only with on-chain proof.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- title: Report an x402 payment outcome
Changes things 3Claude Code: ask
check_x402_sellerCall 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 …Reads text others writeCan send data out1 finding
Why it is in this group
- The description's first verb is "call": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Findings
- Warn
The server marks "check_x402_seller" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "call": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- title: Check an x402 seller before paying
list_reliable_sellersCall this when choosing among sellers for a task, or when the user asks for a safe or reliable API.Reads text others write1 finding
Why it is in this group
- The name "list_reliable_sellers" says "list": a word for reading.
- The description's first verb is "call": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "list_reliable_sellers" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "list_reliable_sellers" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- title: List reliable pay-per-call API sellers
recent_changesCall this when the user asks what changed, or before relying on a verdict older than a day.Reads text others write1 finding
Why it is in this group
- The description's first verb is "call": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "recent_changes" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "call": a word for a change.
Description, as the server wrote it 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).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- title: Recent changes to x402 sellers
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 21, 2026, 19:23 UTC, unchanged since Oct 30, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (1 irreversible, 3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.paidfor.dev/mcp: tools/list returned 4 tools to an anonymous client, including report_x402_payment (irreversible), check_x402_seller (write), list_reliable_sellers (write), recent_changes (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "check_x402_seller" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "call": a word for a change.
The server marks "list_reliable_sellers" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "list_reliable_sellers" says "list": a word for reading.
- Warnrecent_changes
The server marks "recent_changes" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "call": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:report_x402_paymentCan't be undonedescription
Install
Pinned to version 0.7.7. Values in angle brackets are yours to fill in.
claude mcp add --transport http paidfor https://mcp.paidfor.dev/mcpclaude mcp add --transport http paidfor https://mcp.paidfor.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__paidfor__check_x402_seller",
"mcp__paidfor__list_reliable_sellers",
"mcp__paidfor__recent_changes",
"mcp__paidfor__report_x402_payment"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as paidfor. Review it before you use it.
Capability tags behind 4 rules
- mcp__paidfor__check_x402_seller untrusted-input, outbound
- mcp__paidfor__list_reliable_sellers untrusted-input
- mcp__paidfor__recent_changes untrusted-input
- mcp__paidfor__report_x402_payment untrusted-input, outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/dev.paidfor/paidfor/verify?hash=eb9112e8dc4c5cc88d3460cae13c193e5a502d5429bee5ffdf899cff6a3d356a" | jq -e '.changed == false'Pinned hash eb9112e8dc4c, from Nov 20, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.paidfor/paidfor/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.paidfor/paidfor)Source: MCP Registry · repository. Synced Nov 20, 2026, 23:17 UTC.
paidfor MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the paidfor MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 4 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the paidfor MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the paidfor MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: report_x402_payment.
What tools does the paidfor MCP server have?
- 4 tools: 1 irreversible, 3 write. report_x402_payment, check_x402_seller, list_reliable_sellers and recent_changes.
Does the paidfor MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the paidfor MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_x402_seller and report_x402_payment.
Has the paidfor MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 19, 2026. Every change is on this page and in its Atom feed.