local402
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@local402guard my local API on port 3000 with a paywall"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
🔒 local402
One-command local paywall for AI agents
Turn any local server into a payable resource in seconds. Perfect for testing agents that need to pay before they can access your API or MCP tool.
npx local402 --target http://localhost:3000 --price 0.001
What is this?
local402 drops an x402-style HTTP 402 Payment Required paywall in front of any local HTTP server or MCP tool — with a single command, zero config, and no blockchain.
Requests without payment get a clean 402. Requests that "pay" get proxied straight through to your real server. That's it.
It runs in fully simulated mode by default: no wallets, no gas, no external services, no waiting. Just instant, deterministic 402s you can build and test against locally.
agent ──▶ local402 (402 paywall) ──▶ your server
│
└── no payment? → 402 Payment Required
paid? → proxied response ✅Related MCP server: 402-mcp
💸 Why local402?
Agents are learning to pay for things — API calls, tool invocations, data, compute. The x402 protocol makes HTTP-native payments real. But there's a gap:
How do you test a paying agent without spending real money, standing up a wallet, or wiring a whole payment stack — every single time?
You don't want to deploy a facilitator and fund a testnet wallet just to check that your agent notices a 402 and retries with payment. You want a paywall you can throw up in one command and tear down just as fast.
That's local402.
Without local402 | With local402 |
Stand up a facilitator + wallet + testnet funds |
|
Real transactions on every test run | Instant, free, deterministic |
Blockchain latency in your test loop | 0ms — it's all local |
Payment logic tangled into your app | One reverse proxy in front of it |
Hard to reproduce the "unpaid" path | Guaranteed |
Use it to:
✅ Test that your AI agent handles
402and retries with anx-paymentheader✅ Demo a "pay-per-call" API or MCP tool without touching a chain
✅ Develop x402 client logic offline, on a plane, in CI
✅ Prototype pricing before committing to real settlement
⚡ Quick Start
You don't even need to install it.
# 1. Have any local server running (your API, MCP tool, whatever)
# e.g. something on http://localhost:3000
# 2. Put a paywall in front of it
npx local402 --target http://localhost:3000 --price 0.001local402 is now listening on http://localhost:4020 and guarding your server.
# ❌ No payment → 402 Payment Required
curl -i http://localhost:4020/
# ✅ "Pay" → request is proxied to your real server
curl -i http://localhost:4020/ -H "x-payment: simulated"Point your agent at http://localhost:4020 instead of your real server, and watch it learn to pay. 🎉
🛠 Usage
local402 --target <url> [options]Flag | Alias | Default | Description |
|
| (required) | The server to protect, e.g. |
|
|
| Port local402 listens on |
|
| Price advertised in the | |
|
| Currency / asset label for the price | |
|
| Simulated mode — no blockchain, instant (default) | |
| Reserved for real x402 settlement (coming soon) | ||
| Disable colored console output |
The rule
No
x-paymentheader →402 Payment Required(with a helpful JSON body + headers).Has
x-payment: simulated(orpaid) → request is proxied to--target, and the real response comes back untouched.
In simulated mode, any non-empty x-payment value is accepted — simulated and paid are just the canonical ones.
Examples
# Guard an MCP tool on a custom port, charge 0.01
local402 --target http://localhost:8787 --port 9000 --price 0.01
# Free status check — always open, never paywalled
curl http://localhost:4020/__local402🔍 How it works
local402 is a tiny reverse proxy with one opinion: pay first, then pass through.
┌──────────────────────────────┐
│ local402 │
│ :4020 (paywall) │
┌─────────┐ │ │ ┌──────────────┐
│ agent │ ───────▶ │ x-payment header present? │ │ your server │
│ / curl │ │ │ │ :3000 │
└─────────┘ │ NO ─▶ 402 Payment Required │ └──────────────┘
▲ │ │ ▲
│ │ YES ─▶ proxy the request ──┼─────────────────┘
│ │ return real response │ │
└───────────────┤◀──────────────────────────────┼─────────────────┘
402 or proxied response │
└──────────────────────────────┘The unpaid response (HTTP 402):
{
"x402Version": 1,
"error": "Payment Required",
"message": "This resource costs 0.001 USD. Retry with header 'x-payment: simulated'.",
"accepts": [
{
"scheme": "simulated",
"network": "local",
"maxAmountRequired": "0.001",
"asset": "USD",
"payTo": "local402-simulated",
"resource": "/",
"description": "local402 simulated paywall",
"mimeType": "application/json"
}
],
"hint": "x-payment: simulated"
}Response headers on a 402:
HTTP/1.1 402 Payment Required
x-payment-required: true
x-payment-amount: 0.001
x-payment-asset: USD
x-payment-network: local
accept-payment: x-payment: simulatedOn a paid request, local402 attaches a simulated settlement receipt so your client can verify the flow end-to-end:
x-payment-response: <base64 JSON receipt with a sim txHash>🗺 Roadmap
local402 starts simple on purpose. The plan:
v0.1 — Simulated mode. Instant, local, blockchain-free
402paywall. (you are here)v0.2 — Real x402 settlement. Verify actual
X-PAYMENTpayloads via a pluggable facilitator.v0.3 — MCP-native mode. First-class paywalling for MCP tools/resources, not just HTTP.
v0.4 — Per-route pricing. Different prices for different paths and methods.
v0.5 — Usage dashboard. Live TUI of requests, payments, and revenue.
Want to shape it? Open an issue.
🤝 Contributing
Contributions, ideas, and bug reports are all welcome — this is meant to be a friendly little tool.
git clone https://github.com/wushu75/local402.git
cd local402
npm install
npm run dev -- --target http://localhost:3000 # run from source
npm run build # compile to dist/Fork it 🍴
Create a branch (
git checkout -b feat/amazing-thing)Commit your changes (
git commit -m 'feat: amazing thing')Push and open a PR
No contribution is too small — even a typo fix helps.
📄 License
MIT © the local402 contributors. Do whatever you want with it.
⭐ Star the repo if this is useful
If local402 saved you from standing up a payment stack just to test an agent,
drop a star — it genuinely helps other people find it.
Built for the agents that pay their way. 🔒
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityDmaintenanceAg402 is the payment layer for Coinbase's x402 protocol. Wrap any API or MCP server with a paywall in one command (ag402 serve), or let your AI agent auto-pay for paid APIs (ag402 run). Zero code changes for both buyers and sellers. Solana USDC, ~0.5s settlement, non-custodial, 648+ tests, MIT licensed. Works with Claude Code, Cursor, OpenClaw, LangChain, AutoGen, CrewAI out of the box.9MIT
- Alicense-qualityAmaintenanceL402 + x402 client MCP. AI agents discover, pay for, and consume any payment-gated API autonomously. Supports Lightning (NWC), Cashu ecash, stablecoins, and human-in-the-loop payments.371MIT
- Alicense-qualityBmaintenanceHTTP 402 paywall middleware for MCP servers. XRPL/RLUSD native settlement, Phase 3 compliance receipts, zero API keys required.1MIT
- Alicense-qualityDmaintenanceA local MCP proxy that connects to remote MCP servers and automatically handles x402 payments, signing USDC on-chain when a tool returns HTTP 402.71MIT
Related MCP Connectors
Monetize any MCP server: x402 paywall, pay-per-call billing in USDC on Base, agent marketplace.
Pay for HTTP APIs and charge for your own: x402 micropayments in USDC on Base.
Agent x402 Paywall MCP — Coinbase HTTP 402 protocol + on-chain settlement. Agents pay per-call
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/wushu75/local402'
If you have feedback or need assistance with the MCP directory API, please join our Discord server