In-depth architectural comparison of the Cinderwright Api 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
Cinderwright Api
Aggregators · Local stdio
Quality: 35/100 (Fair) | Auth: API Key required
X402 Discovery Mcp
Aggregators · Local stdio
Quality: 44/100 (Fair) | Auth: API Key required
Verdict Summary: Choose Cinderwright Api 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 Cinderwright Api when:
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).
x402 Discovery Hub. Search engine for the agent economy with 1450+ services indexed. Pay with USDC on Base via x402.
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
Cinderwright Api Tools (6)
Unified API endpoint for multiple payment protocols
Automatic protocol detection and payment routing
Supports USDC on Base (x402) and Bitcoin Lightning (L402)
Service discovery with 2,800+ indexed services
Free developer tools for testing, diagnostics, and budgeting
MCP server compatible with Claude Desktop
X402 Discovery Mcp Tools (6)
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).
Cinderwright Api is categorized under Aggregators and uses a local stdio subprocess. In contrast, X402 Discovery Mcp belongs to Aggregators using local stdio subprocess. Select Cinderwright Api when you need capabilities focused on aggregators and X402 Discovery Mcp when you require tools for aggregators.
Primary tools included: Real-time quality and trust scoring (0-100) for x402 APIs, Autonomous payment routing and execution with retries, Facilitator compatibility and placement bid support.