Cinderwright API vs X402 Discovery MCP
A side-by-side look at the Cinderwright API and X402 Discovery MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Cinderwright API for aggregators work as a local process; choose X402 Discovery MCP for aggregators as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Cinderwright API when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
CW_KEY.
Choose X402 Discovery MCP when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You want tools like
x402_discover, x402_health, x402_register.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aggregators | Aggregators |
| Quality signal | 44/100 · Fair | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | Freemium | Freemium |
| Required env vars | CW_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4 | 4 |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 9 |
| Full listing | View Cinderwright API | View X402 Discovery MCP |
Tools & capabilities
Cinderwright API tools
No tool names declared yet. Check the project README from the listing page.
X402 Discovery MCP tools 9
x402_discoverSemantic search across the live catalog by keyword, category, max pricex402_healthReal-time uptime + latency check for any registered servicex402_registerRegister a new x402 service (HTTPS-only, rate-limited)x402_attestERC-8004 trust score and reputation signals for a servicex402_scanFull x402 compliance scan: live config, trust score, mismatch detectionscout_routeDiscover best service for an intent + execute x402 paymentscout_discoverQuery discovery catalog without executingscout_executeExecute x402 payment to a known service URLscout_auditView agent spend log and budget status
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Cinderwright API
{
"mcpServers": {
"cinderwright-ai-cinderwright-api": {
"command": "npx",
"args": [
"-y",
"cinderwright"
],
"env": {
"CW_KEY": "YOUR_CW_KEY_HERE"
}
}
}
}
X402 Discovery MCP
{
"mcpServers": {
"rplryan-x402-discovery-mcp": {
"command": "uvx",
"args": [
"x402-payment-harness"
]
}
}
}
Frequently asked questions
Cinderwright API is categorized under Aggregators and uses a local stdio subprocess. X402 Discovery MCP belongs to Aggregators and uses a local stdio subprocess. Pick Cinderwright API for aggregators work and X402 Discovery MCP for aggregators.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Cinderwright API is listed as freemium — a free tier with paid plans. Auth: api key required. X402 Discovery MCP is listed as freemium — a free tier with paid plans. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add cinderwright-ai-cinderwright-api and rplryan-x402-discovery-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Cinderwright API has a quality signal of 44/100 (Fair) with 2 views, 0 installs and 4 GitHub stars. X402 Discovery MCP has 53/100 (Good) with 2 views, 0 installs and 4 GitHub stars.