Other · Local MCP server
X402 MCP Server
JMT x402: 35 pay-per-call Base/USDC tools for agents, auto-paid via x402 v2. No API key.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.jmthomasofficial/x402-mcp-server- Version
- 2.0.1
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-07-12
- Updated
- 2026-07-12
- Publisher
- jmthomasofficial (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/jmthomasofficial) · how
- Repository
- github.com/jmthomasofficial/x402-mcp-server.git
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | @jmthomasofficial/x402-mcp-server | 2.0.1 | stdio |
How to connect X402 MCP Server
X402 MCP Server runs locally from a Node.js package published to the npm registry: @jmthomasofficial/x402-mcp-server version 2.0.1. 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 @jmthomasofficial/x402-mcp-server@2.0.1. It reads the environment variable JMT_X402_PRIVATE_KEY; set it 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-mcp-server": {
"command": "npx",
"args": [
"-y",
"@jmthomasofficial/x402-mcp-server@2.0.1"
],
"env": {
"JMT_X402_PRIVATE_KEY": "<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 other servers
| Server | Runs |
|---|---|
| x402 DoctorDiagnose x402 seller endpoints: what is wrong with your 402 challenge, and how to fix it. | Remote · HTTPLive check: ✓ handshake |
| x402 Market Intelligence + Russian Web AccessCheck x402 endpoints before paying: liveness, price history, farm detection. Plus RU web access. | Remote · HTTPLive check: ✓ handshake |
| X402 MCPPay for HTTP APIs and charge for your own: x402 micropayments in USDC on Base. | Remote · HTTPLive check: ✓ handshake |
| X402 MCP ServerPay-per-call x402 tools on Base: web extract/render, burn-once secret vault, chart, GeoTIFF. | Local · stdio |
| X402 MCP ServerMCP server for Hermes Asia x402 CN/JP market intelligence via USDC on Base. 8 endpoints. | Local · stdio |
| X402 Money FarmPay-per-call web extraction: clean text, metadata, links, JSON-LD, change detection. USDC on Base. | Local · stdio |
| X402 Payment SafetyAuthorize x402 payments before signing with request-bound, signed safety decisions. | Remote · HTTPLive check: ✓ handshake |
| x402 PreflightInspect and validate an x402 endpoint before an autonomous agent spends USDC. | Remote · HTTPLive check: ✓ handshake |