ZERO Payment Guard
RemoteAbout ZERO Payment Guard
ZERO Payment Guard is a read-only paid API and MCP server for applications and agents, covering Base checks and web information processing. It charges USDC through x402 and does not hold private keys.
Key features
- 01Check Base wallets, transactions, and tokens
- 02Extract web pages and process batches
- 03Retrieve domain and company information
- 04Offer paid HTTP API and MCP tools
Use cases
- 01Verify Base wallet balances and transaction status
- 02Check token or payment details
- 03Extract pages to Markdown and compile company information
MCP support
It provides 10 paid tools and a free `sample_report` over Streamable HTTP and stdio. MCP payments use x402-over-MCP with USDC on Base.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://zero-payment-guard.worker.beacon.host/mcpclaude mcp add --transport http host-beacon-worker-zero-payment-guard-payment-guard https://zero-payment-guard.worker.beacon.host/mcp{"mcpServers":{"host-beacon-worker-zero-payment-guard-payment-guard":{"type":"http","url":"https://zero-payment-guard.worker.beacon.host/mcp"}}}Open in Cursor{"servers":{"host-beacon-worker-zero-payment-guard-payment-guard":{"type":"http","url":"https://zero-payment-guard.worker.beacon.host/mcp"}}}Open in VS Code{"mcpServers":{"host-beacon-worker-zero-payment-guard-payment-guard":{"type":"http","url":"https://zero-payment-guard.worker.beacon.host/mcp"}}}{"mcpServers":{"host-beacon-worker-zero-payment-guard-payment-guard":{"serverUrl":"https://zero-payment-guard.worker.beacon.host/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEZERO Payment Guard: server
This is the source of the hosted x402 API and MCP server at https://zero-payment-guard.worker.beacon.host. It is a Hono app that runs on Cloudflare-Workers-compatible runtimes and on Node.
What it exposes
| Surface | Path | Notes |
|---|---|---|
| Paid HTTP API (x402 v2, USDC on Base) | GET /v1/* | x402-preflight, usdc-payment, token-check, wallet-snapshot, tx-status, basename, page-extract, page-extract-batch, domain-enrich, company-brief |
| MCP, streamable HTTP | POST /mcp | 10 paid tools + free sample_report; payments use x402-over-MCP (@x402/mcp) |
| MCP, stdio | npm run stdio | same tools, for local clients and directory introspection |
| Free discovery | /openapi.json, /llms.txt, /.well-known/x402, /sample/* |
Every handler is read-only: public Base RPC reads, public DNS/RDAP, and fetching public web pages on request (it honours robots.txt and blocks private hosts). The server holds no private keys. It only names a PAY_TO address that receives payments, and the facilitator settles them.
Run locally
cd server
npm ci
npm start # HTTP on 127.0.0.1:8790 (PORT to change)
npm run stdio # MCP over stdio
MCP client config for the stdio server:
{
"mcpServers": {
"zero-payment-guard": { "command": "npx", "args": ["tsx", "/path/to/zero-payment-guard/server/src/stdio.ts"] }
}
}
Or with Docker, from the repo root: docker build -t zero-payment-guard . && docker run -i --rm zero-payment-guard.
Configuration
Set these in wrangler.toml [vars] or as environment variables. They are not secrets.
| Variable | Default | Meaning |
|---|---|---|
PAY_TO | operator wallet | address that receives USDC; change it to your own if you deploy a copy |
NETWORK | eip155:8453 | Base mainnet |
FACILITATOR_URL | https://facilitator.payai.network | x402 facilitator (no key needed) |
Optional secrets, set with wrangler secret put and never committed: CDP_API_KEY_ID and CDP_API_KEY_SECRET switch to the Coinbase CDP facilitator. DEV_FREE=1 (local testing only) disables the paywall.
Deploy
npx wrangler deploy (Cloudflare) or any Workers-compatible host. The hosted copy runs on beacon.host.
Layout
src/index.ts: routes, paywall (@x402/hono), discovery documentssrc/mcp.ts: MCP server (buildMcp) and the streamable-HTTP handlersrc/stdio.ts: stdio entrypoint;src/node.ts: Node HTTP entrypointsrc/checks*.ts: Base payment, token, wallet and tx checkssrc/extract.ts,src/enrich.ts,src/bundle.ts: web page extraction and company enrichmentsrc/fac.ts: facilitator client that caches/supportedas data (safe on Workers)
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.