
X402 Mcp Server
io.github.jmthomasofficialPublished by GitHub account jmthomasofficialv2.0.1Updated Oct 27, 2026
JMT x402: 35 pay-per-call Base/USDC tools for agents, auto-paid via x402 v2. No API key.
Overview
Exposes pay-per-call research and data APIs as MCP tools, each paid automatically in USDC on Base mainnet via the x402 protocol.
- What you can do
- Search and extract web content, including search answers with citations, URL text extraction and deep research reports
- Summarize and analyze text, plus small utilities such as hashing, JSON-to-CSV conversion and text diffing
- Pull company and market intelligence: company dossiers, SEC filing analysis, competitor matrices, regulatory monitoring and domain trust scores
- Retrieve news briefings and cross-platform social sentiment
- Look up live market data: crypto prices, stock quotes, Base gas snapshots, US Treasury yields, WHOIS and SEC EDGAR records
- When to use it
- Useful when an assistant needs on-demand research, market or company data without signing up for separate API keys, and you are willing to pay a small per-call fee in USDC from a funded Base wallet.
- Requirements
- Runs locally over stdio via npx from the npm package. Needs Node.js, network access to the x402 server and Base mainnet, and an x402 client such as @x402/fetch and @x402/evm. Requires a funded Base-mainnet wallet private key supplied in the JMT_X402_PRIVATE_KEY environment variable.
Installation
In SourceWeft
- Open X402 Mcp Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
JMT x402 MCP Server
25 pay-per-call API tools for AI agents, powered by the x402 protocol on Base mainnet.
What This Does
This MCP server exposes 25 paid API endpoints as MCP tools. When an AI agent (Claude, Cursor, Cline) calls a tool, the request goes to our x402 server. The first request returns HTTP 402 (Payment Required). The agent's x402 client pays in USDC on Base mainnet and retries for the result.
No API keys. No signup. Payment IS the authentication.
Tools
Payment Setup
- Protocol: x402 v1
- Network: Base mainnet (eip155:8453)
- Currency: USDC (Bridged USDC: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913)
- Facilitator: Dexter (x402.dexter.cash) — 0% fee, gas-sponsored for buyers
- Pay-to wallet: 0x624FaF18C78456C8Da5bf156Cd77c1A2033F21c5
To make paid calls, install an x402 client:
Installation
Discovery
- OpenAPI: https://jmt-x402-proxy.jmthomasofficial.workers.dev/openapi.json
- Manifest: https://jmt-x402-proxy.jmthomasofficial.workers.dev/.well-known/x402
- LLMs.txt: https://jmt-x402-proxy.jmthomasofficial.workers.dev/llms.txt
- Pricing: https://jmt-x402-proxy.jmthomasofficial.workers.dev/api/pricing
License
MIT
Source: README.md at commit c728857
Tools
0Version history
1- v2.0.1LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.