mcpField
Z
ZERO Payment Guard

ZERO Payment Guard

Remote
zero-payment-guard.worker.beacon.hostOther0Updated 1d ago

About 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

  1. 01Check Base wallets, transactions, and tokens
  2. 02Extract web pages and process batches
  3. 03Retrieve domain and company information
  4. 04Offer paid HTTP API and MCP tools

Use cases

  1. 01Verify Base wallet balances and transaction status
  2. 02Check token or payment details
  3. 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.

Endpointhttps://zero-payment-guard.worker.beacon.host/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

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 README

ZERO 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

SurfacePathNotes
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 HTTPPOST /mcp10 paid tools + free sample_report; payments use x402-over-MCP (@x402/mcp)
MCP, stdionpm run stdiosame 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.

VariableDefaultMeaning
PAY_TOoperator walletaddress that receives USDC; change it to your own if you deploy a copy
NETWORKeip155:8453Base mainnet
FACILITATOR_URLhttps://facilitator.payai.networkx402 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 documents
  • src/mcp.ts: MCP server (buildMcp) and the streamable-HTTP handler
  • src/stdio.ts: stdio entrypoint; src/node.ts: Node HTTP entrypoint
  • src/checks*.ts: Base payment, token, wallet and tx checks
  • src/extract.ts, src/enrich.ts, src/bundle.ts: web page extraction and company enrichment
  • src/fac.ts: facilitator client that caches /supported as data (safe on Workers)

Comments

Markdown supported

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.