Developer · Local MCP server
x402 Micro Tollgate
X402 HTTP 402 + MCP paywall: charge USDC per agent call. Self-host via npx or Docker.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.kevin2003050666-coder/x402-micro-tollgate- Version
- 0.3.3
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-09-03
- Updated
- 2026-09-03
- Publisher
- kevin2003050666-coder (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/kevin2003050666-coder) · how
- Listed under
- Docker MCP servers
- Website
- github.com/kevin2003050666-coder/x402-micro-tollgate
- Repository
- github.com/kevin2003050666-coder/x402-micro-tollgate
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | x402-micro-tollgate | 0.3.3 | stdio |
How to connect x402 Micro Tollgate
x402 Micro Tollgate runs locally from a Node.js package published to the npm registry: x402-micro-tollgate version 0.3.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y x402-micro-tollgate@0.3.3. It reads these environment variables: CDP_API_KEY_ID (secret), CDP_API_KEY_SECRET (secret), X402_PAY_TO, UPSTREAM_URL, PRICE, NETWORK and X402_ENVIRONMENT; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"x402-micro-tollgate": {
"command": "npx",
"args": [
"-y",
"x402-micro-tollgate@0.3.3"
],
"env": {
"CDP_API_KEY_ID": "<secret>",
"CDP_API_KEY_SECRET": "<secret>",
"X402_PAY_TO": "<value>",
"UPSTREAM_URL": "<value>",
"PRICE": "<value>",
"NETWORK": "<value>",
"X402_ENVIRONMENT": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Writing Style CheckerProse linter + AI-slop detector: weasel words, passive voice, hedging, and research-cited AI tells. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Wsjtx MCPOperate WSJT-X (FT8/FT4/WSPR) from MCP clients over its UDP message protocol. | Local · stdio |
| wydLocal runtime provenance for coding agents. Inspect sessions and explain which one owns a process. | Local · stdio |
| X402 GitBuy private git repos and agent skills with USDC over x402. Read the manifest free, then pay. | Remote · HTTPLive check: ✗ no handshake |
| X402 Receipt VerifierAudits NEXUS's own x402 payment logs against its own delivery logs and issues a signed proof-of-deli. | Remote · HTTPLive check: sign-in required |
| X402 Repohealth MCPFree MCP server: compute a GitHub repo maintenance/abandonment health score from live data. | Local · stdio |
| X402engine MCP50+ pay-per-call APIs for AI agents - images, LLM, code, crypto, travel & more via x402. | Local · stdio |
| x402nanoMachine-payable prediction-market briefs and probability-change monitoring for AI agents. | Remote · HTTPLive check: ✗ no handshake |