MCP Server

What true402/mcp-server MCP server does

The true402/mcp-server MCP server connects MCP clients to the true402 machine-native marketplace. It exposes tools for LLM inference, web and SEO analysis, deterministic finance calculations, prediction markets, DeFi yields, and blockchain safety checks. The catalog includes both free discovery functions and paid operations whose prices are returned through x402 payment challenges.

Blockchain coverage includes Base, Ethereum, and selected BNB Smart Chain token checks. Depending on the tool, an agent can inspect ERC-20 behavior, liquidity, ownership, mint capability, honeypot behavior, deployer reputation, liquidity removals, whale swaps, or the safety of an unsigned transaction. Web tools can extract page text, preview links, render screenshots, inspect robots and llms policies, and score HTTP security headers.

How it works

The true402/mcp-server MCP server sends a tool request to the true402 API. For a paid operation, the API returns HTTP 402 with the exact payment terms. When a wallet is configured, the server signs an EIP-3009 USDC authorization on Base, retries with the payment header, and settlement occurs on-chain. The facilitator sponsors gas, so the configured wallet needs USDC but does not need ETH for gas.

Each authorization buys one response. Payment is submitted only after a successful 2xx response, and calls that error or time out are not settled. The server enforces MAX_PAYMENT_USDC as a per-call ceiling; requests above that limit are refused before payment. Tool prices can change, and the live 402 response is authoritative.

Setup and configuration

The package runs over stdio and requires Node.js 20 or newer. A typical MCP client configuration uses npx -y @true402.dev/mcp-server. Claude Desktop, Claude Code, Cursor, Cline, and other MCP clients can use the same command pattern.

Environment settings include:

• WALLET_PRIVATE_KEY: a funded Base wallet key for automatic x402 payments. The key is read from the environment and is not logged or returned.
• SERVER_URL: API base URL, defaulting to https://true402.dev/api; it can point to a self-hosted instance.
• MAX_PAYMENT_USDC: maximum amount allowed for one call, defaulting to 0.25.

A wallet is not needed to start the process. Without one, paid tools return their payment requirements rather than completing the payment. The documentation recommends using a dedicated, low-balance wallet.

Tools and capabilities

The true402/mcp-server MCP server includes list_models for live model IDs and token prices, and chat for paid LLM completions across several providers. Other capabilities include:

• SEO/GEO audits, keyword volume and ideas, ranked keywords, and backlink reports.
• Web extraction, Open Graph link previews, screenshots, robots and llms checks, and security-header analysis.
• Black-Scholes, volatility, Sharpe, Sortino, Kelly, drawdown, VaR, CVaR, and CAGR calculations.
• Prediction-market search and DeFi pool filtering with APY, TVL, stablecoin, and risk fields.
• Token reports, address and deployer checks, new-pair discovery, liquidity alerts and history, whale swaps, and unsigned transaction preflight.

Tools are auto-discovered from the live catalog, so the available set may change without a package update.

Limitations and notes

Most operations are paid in USDC on Base, although some have a small per-IP daily free allowance. list_models is free. seo_audit is priced per page and can exceed a normal per-call ceiling when auditing multiple pages, so the ceiling may need adjustment. deployer_check requires an explorer key on the service side and can return 503 when that configuration is absent.

On-chain safety results are assessments, not guarantees. For example, tx_preflight checks simulation, decoded intent, and archived counterparty liquidity activity but never labels a transaction safe. Historical liquidity coverage is limited to the indexed block range, and a clean result means only that the reported checks found no issue.