How to Monetize an MCP Server: Per-Call x402 Payments (With Live Receipts)

ScriptMasterLabs has published a receipt-first implementation of per-call x402 payments for MCP servers, in which each unpaid tool call returns a 402 Payment Required challenge carrying price, asset, network, payTo address and expiry, and the agent's wallet signs an authorization that a facilitator verifies and settles on-chain. The operator documents a live x402 manifest on Base (eip155:8453) settling in USDC via Coinbase's CDP facilitator, an MCP handshake against mcp-x402 v2.1.11, and ERC-8004 agent registry identity 74033, while noting its marketplace paid reads are quarantined and claiming no revenue figures.

There are 20,000+ MCP servers in the wild and fewer than 5% have any monetization. The guides that rank for "how to monetize an MCP server" are vendor pitches, Stripe subscription tutorials, or marketing calculators — none shows a live payment receipt. Here's the receipt-first version. I run ScriptMasterLabs; we bill x402 on our MCP/HTTP tool infra on Base. Per-call x402 billing: your server answers each unpaid tool call with a 402 Payment Required challenge carrying price, asset, network, payTo address, and expiry. The agent's wallet signs the payment authorization, retries the same call, and a facilitator verifies and settles it on-chain. No accounts, no API keys, no checkout pages. Receiving a challenge costs the caller nothing. 1. The x402 payment manifest: curl https://squeezeos-api.onrender.com/.well-known/x402 Returns a live machine-readable contract: operator SCRIPTMASTERLABS , network eip155:8453 Base , asset USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 , payTo 0xc29185fa176357612f3194735753e520e91adc46 , facilitator https://api.cdp.coinbase.com/platform/v2/x402 , challenge header PAYMENT-REQUIRED , MCP endpoint https://squeezeos-api.onrender.com/mcp , identity registered on the ERC-8004 agent registry agent id 74033 . Verified live September 22, 2026. 2. A live MCP handshake: curl -X POST https://mcp-x402.onrender.com/mcp \ -H 'Content-Type: application/json' \ -H 'Accept: application/json, text/event-stream' \ -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"probe","version":"0"}}}' Answers with serverInfo: {"name": "mcp-x402", "version": "2.1.11"} and tool capabilities live. tools/call without a payment credential, return the payment terms — JSON-RPC error data on the MCP transport, or 402 + PAYMENT-REQUIRED header over HTTP. PAYMENT-RESPONSE receipt. The protocol sets no price — each seller does. Verify the fresh 402 challenge before signing anything. Our marketplace paid reads are currently quarantined provider listings only , so I claim zero revenue figures. The manifest, the headers, and the handshake are what I can prove. Canonical version: https://scriptmasterlabs.com/monetize-mcp-server https://scriptmasterlabs.com/monetize-mcp-server