
ProvenPaid
com.provenpaidv0.1.0Updated Oct 9, 2026
Check an x402 endpoint before your agent pays it: challenge validity and on-chain payer evidence.
Overview
Lets an assistant run a paid pre-payment check on an x402 endpoint, validating its payment challenge and reporting on-chain payer evidence.
- What it does
- Exposes a check_x402_endpoint tool that validates an endpoint's x402 payment challenge and reports public on-chain evidence for its receiving address, including distinct payers, repeat-payer share, payer concentration and coverage. Two free tools, provenpaid_methodology and provenpaid_status, explain how signals are computed and show the paying wallet address, network, price cap and remaining daily checks. The check itself is paid automatically in USDC on Base, about $0.01 per check.
- When to use it
- Useful once before an agent relies on an unfamiliar paid x402 endpoint, to see whether the challenge is valid and whether real wallets actually pay it. It is not intended to run before every call, and results are evidence rather than a verdict on service quality.
- Requirements
- Local process, Python 3.11+, installed via uvx or pip. Requires the secret PROVENPAID_WALLET_PRIVATE_KEY for a dedicated low-balance wallet holding USDC on Base, plus network access to the ProvenPaid API. Optional settings include PROVENPAID_DAILY_LIMIT, PROVENPAID_MAX_PRICE_USD, PROVENPAID_NETWORK, PROVENPAID_API_URL and PROVENPAID_STATE_DIR.
Installation
In SourceWeft
- Open ProvenPaid in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
provenpaid-mcp
Give your agent a pre-payment check for paid x402 endpoints. Evidence before you pay.
ProvenPaid checks an x402 endpoint before your agent relies on it: is its payment challenge valid, and do real wallets actually pay it on-chain, come back, and how concentrated are payments? This MCP server exposes that check as a tool and pays for it automatically, about $0.01 in USDC on Base per check, from a wallet you control.
Use it once before relying on an unfamiliar endpoint, not before every call.
Tools
You are not charged when the URL is invalid or unsafe, is not an x402 endpoint, or offers no payment option in USDC on Base. Results are evidence, not a verdict: ProvenPaid does not verify service quality or that an endpoint controls its receiving address.
Install
Requires Python 3.11+. With uv:
or pip install provenpaid-mcp.
Claude Desktop / Claude Code / Cursor
Wallet safety
- Use a dedicated wallet holding only a few dollars of USDC on Base. Never use a wallet with meaningful funds.
- The key stays on your machine, in memory only. It is never logged, returned by a tool, or sent anywhere; only signed payment authorizations leave the process.
- No ETH is needed: the payment facilitator pays network fees.
Guardrails enforced before anything is signed:
How it works
The server calls GET https://api.provenpaid.com/v1/check?url=.... The API answers HTTP 402 with x402 payment requirements; the official x402 SDK signs a single-use USDC authorization within the guardrails above and retries. Settlement happens only when the check delivers evidence. Methodology: https://api.provenpaid.com/methodology
License
MIT
Source: README.md at commit 3ba55a5
Tools
0Version history
1- v0.1.0LatestOct 9, 2026


