In-depth architectural comparison of the X402search MCP and X402 Discovery MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
X402search MCP
Aggregators · Local stdio
Quality: 48/100 (Fair) | Auth: other
X402 Discovery MCP
Aggregators · Local stdio
Quality: 53/100 (Good) | Auth: API Key required
Verdict Summary: Choose X402search MCP if you need specialized Aggregators tools running via a local process. Choose X402 Discovery MCP if your workspace requires Aggregators integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose X402search MCP when:
You need dedicated capabilities in the Aggregators domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Paid Service).
You have access to required keys: EVM_PRIVATE_KEY.
Primary tools included: Keyword search across 14,000+ x402-enabled APIs, Network filtering, Maximum-price filtering in USDC.
Search 14,000+ x402-enabled HTTP APIs by keyword. Agents pay $0.01 USDC per search via x402 micropayments on Base mainnet — no API keys required. Larger index than any other x402 discovery layer.
Runtime discovery layer for x402-payable APIs. Agents discover and route to pay-per-call x402 endpoints by capability, get quality-ranked results with trust scores (0-100), and pay per query via x402. Includes MCP server, Python SDK, and CLI (npm install -g x402scout).
Category & Scope
Tools & Capabilities Breakdown
X402search MCP Tools (6)
Keyword search across 14,000+ x402-enabled APIs
Network filtering
Maximum-price filtering in USDC
Configurable result limit up to 50
Structured endpoint, payment, network, and relevance data
Base mainnet x402 micropayments
X402 Discovery MCP Tools (9)
x402_discover
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
X402search MCP is categorized under Aggregators and uses a local stdio subprocess. In contrast, X402 Discovery MCP belongs to Aggregators using local stdio subprocess. Select X402search MCP when you need capabilities focused on aggregators and X402 Discovery MCP when you require tools for aggregators.