
JMT x402 Agent Tools
io.github.jmthomasofficialPublished by GitHub account jmthomasofficialv1.0.0Updated Oct 24, 2026
25 x402 paid API tools for AI agents on Base mainnet.
Overview
A local MCP server exposing 25 pay-per-call x402 API tools on Base mainnet, paid in USDC per request with no API keys or signup.
- What you can do
- Run paid research and analysis calls: AI answers, deep research, summaries, text analysis and competitor comparisons, each billed per call in USDC on Base mainnet after an HTTP 402 payment challenge and retry. Retrieve market and finance data: stock quotes, crypto prices, crypto research, macro dashboard, market pulse, treasury yields and Base gas snapshots. Pull filings and company information: SEC 10-K/10-Q analysis, EDGAR lookups, company intelligence dossiers and regulatory monitoring. Gather web and domain data: web search, URL text extraction, WHOIS/RDAP lookups, domain trust scores, news briefings and social sentiment. Run small utility operations: hashing, JSON-to-CSV conversion and,
- When to use it
- Use it when an assistant needs on-demand research, market, filing or web-lookup results and you are willing to pay small per-call USDC fees on Base mainnet instead of managing API keys or accounts.
- Requirements
- Runs as a local Node.js process installed from the npm package and started locally. An x402 client (the @x402/fetch and @x402/evm packages) is needed to make paid calls. A funded wallet holding USDC on Base mainnet is required, since payment replaces authentication. Network access to the provider's x402 server is needed.
Installation
In SourceWeft
- Open JMT x402 Agent Tools 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- v1.0.0LatestSep 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.