In-depth architectural comparison of the X402search MCP and Cinderwright API 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
Cinderwright API
Aggregators · Local stdio
Quality: 45/100 (Fair) | Auth: API Key required
Verdict Summary: Choose X402search MCP if you need specialized Aggregators tools running via a local process. Choose Cinderwright API 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.
You need dedicated capabilities in the Aggregators domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
You have access to required keys: CW_KEY.
Primary tools included: Unified API endpoint for multiple payment protocols, Automatic protocol detection and payment routing, Supports USDC on Base (x402) and Bitcoin Lightning (L402).
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.
x402 Discovery Hub. Search engine for the agent economy with 1450+ services indexed. Pay with USDC on Base via x402.
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
Cinderwright API Tools (6)
Unified API endpoint for multiple payment protocols
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, Cinderwright API belongs to Aggregators using local stdio subprocess. Select X402search MCP when you need capabilities focused on aggregators and Cinderwright API when you require tools for aggregators.