PayGate MCP
This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
PayGate MCP
Monetization gateway for Model Context Protocol servers. Put any MCP server behind a pay-per-call toll that AI agents can settle autonomously — no signup, no API keys, no human in the loop.
Live endpoint: https://paygate-mcp.rendercriativo.workers.dev/mcp
What it does
An agent calls a tool. If the tool is monetized, PayGate answers with an x402 v2 payment challenge instead of the result. The agent signs a USDC transfer authorization, retries, and gets its answer. Settlement happens on Base; the developer never touches payment code.
agent ──tools/call──▶ PayGate ──▶ 402 challenge (price, asset, payTo)
agent ──signed payload──▶ PayGate ──verify──▶ facilitator
PayGate ──▶ developer's MCP server ──▶ result
PayGate ──settle──▶ facilitator ──▶ USDC on Base
agent ◀── result + settlement receiptPayment is verified before the tool runs and settled after it returns. If the tool fails or returns an error, nothing is charged.
Related MCP server: @true402.dev/mcp-server
For agents
Discovery is free. Ask PayGate what is for sale:
curl -X POST https://paygate-mcp.rendercriativo.workers.dev/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
"params":{"name":"list_registered_servers","arguments":{}}}'Calling a monetized tool without payment returns a spec-compliant challenge — a tool result with isError: true whose structuredContent holds the PaymentRequired object:
{
"x402Version": 2,
"error": "Payment required: calculate_fator_r custa $0.02 USDC.",
"resource": { "url": "mcp://tool/calculate_fator_r", "mimeType": "application/json" },
"accepts": [{
"scheme": "exact",
"network": "eip155:8453",
"amount": "20000", // 6-decimal USDC units
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"payTo": "0x82e3...999e",
"maxTimeoutSeconds": 120,
"extra": { "name": "USD Coin", "version": "2" } // EIP-712 domain
}]
}Sign an EIP-3009 TransferWithAuthorization using exactly the domain in extra, then retry the call with the payment attached under params._meta["x402/payment"]. The settlement receipt comes back in _meta["x402/payment-response"].
The USDC EIP-712 domain name is
"USD Coin"on Base mainnet and"USDC"on Base Sepolia. Using the wrong one makes every signature fail verification.
A working reference client is in scripts/pay-test.mjs:
PRIVATE_KEY=0x... node scripts/pay-test.mjsThe paying wallet needs USDC on Base — but no ETH: gas is covered by the facilitator.
Both x402 transports are supported. HTTP clients can use the base64 PAYMENT-REQUIRED / PAYMENT-SIGNATURE / PAYMENT-RESPONSE headers instead of the MCP _meta binding.
For sellers
The whole seller lifecycle is exposed as MCP tools, so an agent can run it end to end — tell your assistant to monetize your server and it can do everything below on its own:
Tool | What it does |
| Lists your server. Its tools are imported automatically; you get a proxy URL and a secret |
| Serve the token from registration at |
| Reprice a tool or take it off the market. |
| Revenue report and current listing. |
Buyers pay your wallet directly on-chain. PayGate never holds your funds — there is no payout to wait for, no balance to withdraw, and no commission on direct payments. Your server is never modified: PayGate forwards initialize, tools/list, resources/list and prompts/list for free and charges only on tools/call.
The same operations exist as REST (POST /api/register, PUT /api/me/tools, GET /api/me/earnings) if you prefer curl:
curl -X POST https://paygate-mcp.rendercriativo.workers.dev/api/register \
-H 'Content-Type: application/json' \
-d '{"name":"Your Service",
"target_server_url":"https://your-mcp-server.example.com/mcp",
"wallet_address":"0xYourWallet"}'Health and diagnostics
GET /health/x402 reports whether the payment rail is actually able to charge:
{
"network": "eip155:8453",
"facilitator": { "url": "...", "reachable": true, "authenticated": true },
"ready_to_charge": true,
"diagnosis": "Pronto para cobrar."
}Configuration
Runtime values live in wrangler.jsonc (vars) and Cloudflare secrets.
Variable | Purpose |
| CAIP-2 network. |
| Facilitator base URL, no |
| Wallet that receives payments. |
| Optional; omitted from the UCP manifest when empty. |
| Coinbase CDP credentials. Required for mainnet — it is the only facilitator that settles on Base. |
| Token forwarded to the developer's MCP server. |
| Optional, for the Stripe path on tools priced ≥ $0.50. |
Base Sepolia needs no credentials: the public facilitator at https://x402.org/facilitator settles testnet USDC for free — the cheapest way to try the whole flow.
Layout
src/
├── index.ts routes, health, discovery documents
├── x402/
│ ├── config.ts network registry (CAIP-2, USDC assets, EIP-712 domains)
│ ├── protocol.ts v2 structures, MCP + HTTP transport bindings
│ └── facilitator.ts /verify and /settle, CDP JWT auth (EdDSA and ES256)
├── api/
│ ├── proxy.ts the paid path: challenge → verify → execute → settle
│ ├── mcp-server.ts PayGate's own MCP server
│ ├── paygate-tools.ts marketplace tools: register, verify, price, earnings
│ ├── llms-txt.ts /llms.txt for AI systems arriving over the web
│ ├── register.ts developer onboarding
│ ├── dev-management.ts profile, pricing, earnings
│ └── discovery.ts server card and UCP manifest
└── db/schema.ts developers, tools, transactions, payment proofsDevelopment
npm install
npx wrangler dev # local
npx wrangler deploy # productionBuilt on Cloudflare Workers, Hono, and D1.
License
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
x402 pay-per-call APIs over MCP, settled in USDC on Base for autonomous agents and developers.
Pay-per-use MCP tools for AI agents. USDC on Base via x402. No API keys.
MCP server for X420's pay-per-call agent services (x402, USDC on Base, paid from your own wallet).
15 paid AI agent primitives via x402 (USDC on Base). Pay-per-call MCP server.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceDrop-in x402 payment middleware for MCP servers. Charge AI agents per tool call using USDC on Base chain — Python and JavaScript SDKs, no payment processor, no KYC.MIT
- AlicenseAqualityBmaintenanceAn MCP server that enables AI agents to access paid AI inference and web tools via HTTP 402 micropayments in USDC on Base, using the agent's wallet as identity.36122 npmMIT
- FlicenseAqualityCmaintenanceMCP server for a live x402 payment gateway on Base (USDC). Lets AI agents discover, preview for free, then pay per call — with prepaid gasless payments, signed receipts, and delta delivery.7-
- AlicenseBqualityDmaintenanceAn MCP server providing 22 pay-per-call utility tools for AI agents (scrape, validate, embed, store, moderate, notify, convert, prevent loops) without accounts or API keys, using USDC payments via the x402 protocol.1753 npm1MIT