About true402
true402 is an MCP server for agents that need pay-per-call access to AI inference, web, SEO, and on-chain analysis tools. It discovers tools from a live catalog and settles payments in USDC on Base through x402.
Key features
- 01Auto-discovers the live tool catalog
- 02Calls LLM inference and web tools
- 03Checks token safety and on-chain activity
- 04Analyzes SEO and search results
- 05Pays in USDC through x402
- 06Sets a per-call payment cap
Use cases
- 01Assess Base token and address risk
- 02Preflight a Base transaction before signing
- 03Extract web content and audit SEO
- 04Call LLM inference on demand
MCP support
The MCP server exposes marketplace tools for AI, web, SEO, markets, and on-chain analysis. Paid calls use x402 USDC settlement; a configured wallet can pay automatically, or tools can return payment requirements without one.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @true402.dev/mcp-serverWALLET_PRIVATE_KEYSecretFunded Base wallet private key for x402 payment signing (optional; without it, paid tools return the 402 requirements).SERVER_URLtrue402 API base (default https://true402.dev/api). Must be https (or localhost) — the signer refuses to send a payment over cleartext.MAX_PAYMENT_USDCClient-side per-call spend ceiling in USDC (default 0.10). The signer refuses to auto-pay a 402 whose amount exceeds this — protects the wallet from a hostile endpoint.Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
11Saved tool list · updated 3d ago
This tool takes no parameters.
Details
From the project README@true402.dev/mcp-server
MCP server for the true402 machine-native marketplace — give your agent pay-per-call access to AI inference and web tools over x402 (HTTP 402 micropayments in USDC on Base).
No accounts, no API keys. The agent's wallet is its identity: each paid tool returns an HTTP 402 challenge, the server signs an EIP-3009 USDC authorization, and the call settles on-chain. Configure a funded wallet to auto-pay, or run without one and the paid tools will surface the exact payment requirements instead of failing.
Tools
Tools are auto-discovered from the live catalog at startup, so a new marketplace stall appears without an update to this package. The catalog currently yields:
| Group | Tools | Price |
|---|---|---|
| Token safety (Base) | token_report (composite avoid/caution/ok verdict — the pre-trade gate), token_safety, honeypot, address_safety, address_risk, deployer_check | $0.005–0.008 |
| Base history & flow | liquidity_history (every observed liquidity removal + co-drained tokens), liquidity_pulls, new_pairs, whale_swaps | $0.003–0.005 |
| Before you sign | tx_preflight — an unsigned Base transaction: does it revert, does it grant an unlimited approval, has the counterparty drained liquidity. Takes no key and no signature | $0.008 |
| Full dossier | token_dossier — verdict + reasons over deployer and liquidity history, and what could not be established | $0.10 |
| Other chains | token safety, token report and address safety on Ethereum and BSC (plus deployer check on Ethereum); token safety on Solana | $0.005–0.008 |
| Web | web_extract, link_preview, screenshot, robots_check (AI-crawler policy + llms.txt), headers_check | $0.003–0.005 |
| SEO & search | seo_audit (SEO + GEO audit, per page), serp, backlinks, keyword_volume (up to 200 keywords per call), ranked_keywords, keyword_ideas | $0.02–0.15 |
| Markets & finance | prediction_markets, defi_yields, quant | $0.003–0.005 |
| LLM | chat (OpenAI-compatible, per-token + 3%), list_models (free) | — |
Prices are indicative; the live 402 challenge is authoritative, and the server refuses to sign above
its per-call cap. Call list_models or read https://true402.dev/api/openapi.json for the exact set.
Install
Requires Node.js ≥ 20. Runs over stdio — point any MCP client at it via npx.
Claude Desktop / Claude Code
Add to your MCP config (claude_desktop_config.json, or .mcp.json for Claude Code):
{
"mcpServers": {
"true402": {
"command": "npx",
"args": ["-y", "@true402.dev/mcp-server"],
"env": {
"WALLET_PRIVATE_KEY": "0xYOUR_FUNDED_BASE_WALLET_KEY"
}
}
}
}
Cursor / Cline / other MCP clients
Same idea — command npx, args ["-y", "@true402.dev/mcp-server"], and the WALLET_PRIVATE_KEY env var.
Configuration
| Env var | Default | Description |
|---|---|---|
SERVER_URL | https://true402.dev/api | true402 API base. Override to point at a self-hosted instance. |
WALLET_PRIVATE_KEY | (none) | A funded Base wallet private key used to sign x402 payments. Needs USDC (gas is sponsored by the facilitator — no ETH required). Without it, paid tools return the 402 requirements instead of paying. |
MAX_PAYMENT_USDC | 0.25 | Hard per-call spend ceiling in USDC. This server auto-discovers every paid stall the marketplace advertises (it walks the live OpenAPI spec, not a fixed list), so a new or repriced stall can appear above the default at any time — a call over the ceiling is refused (not paid, not crashed), and the refusal names the price and the ceiling. Raise it if a discovered tool's description shows a price close to or over your configured value; one stall (seo_audit) is priced per page and can itself exceed a typical ceiling on a large page. |
X402_ALLOW_NETWORKS | (none) | Payments are signed for Base mainnet (eip155:8453) only; a 402 naming any other chain is refused. To also pay on Base Sepolia or Ethereum mainnet, list them as comma-separated CAIP-2 ids, e.g. eip155:84532,eip155:1. Unsupported entries are ignored. |
Security: the key is read only from the environment and is never logged, echoed, or returned. Use a dedicated low-balance wallet — fund it with only what you intend to spend.
How payment works
- The tool calls the true402 endpoint with no payment.
- The server replies
402with accepted payment options (USDC on Base). - This MCP server signs an EIP-3009
transferWithAuthorizationwith your wallet. - It retries with the signed payment in the
PAYMENT-SIGNATUREheader (x402 v2); the service verifies and responds. - Settlement happens on-chain. Your wallet pays only USDC — the facilitator sponsors gas.
When a newer release of this server exists, the first tool result of the session carries one extra line saying so, with the install command. Nothing is blocked; it is shown once per process.
Links
- Marketplace: https://true402.dev
- Free Telegram rug-check bot (no wallet): https://t.me/True402bot
- Live tool catalog: https://true402.dev/api/v1/services
- x402 protocol: https://x402.org
Guides
- The x402 protocol, explained
- x402 facilitators: what they do and which to use
- Fund a Base wallet for x402 (USDC only, no ETH)
Also available for
MCP (Claude Code / Desktop, Cursor, Hermes) · Hermes Agent · OpenClaw · ElizaOS · LangChain · CrewAI · Vercel AI SDK · Coinbase AgentKit · Virtuals GAME · CLI — same on-chain checks, one install command each: true402.dev/integrations
Paying, exactly
The rules below are the service's, not this package's — they bite whatever client you use, and they are the ones that surprise people writing their own payer.
- Pay the EXACT amount quoted in the 402. Underpaying is rejected. Overpaying is refused with 402 and never credited — settlement submits the signed value and there is no refund path, so a surplus would simply be swept. Equality is also what binds an authorization to the resource it was quoted for.
- One authorization buys exactly one response. A replay is refused, not double-charged.
- You are charged on success only. Settlement is submitted only when the endpoint returns 2xx; if it errors or times out, your signed authorization is never submitted, so there is nothing to refund.
- Some endpoints serve a few free calls per day per client IP, with no wallet. The per-operation description in the OpenAPI spec says which.
Full rules: true402.dev/terms · what is logged and kept: true402.dev/privacy
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.