x402 Universal Payer vs callx402 MCP server
x402 Universal Payer is an MCP server published by nirholas. Marketplaces we read that list it: 1 (Official MCP Registry). callx402 MCP server is an MCP server published by payload-tools. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  x402 Universal Payer |  callx402 MCP server |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.2 Downloads/month (npm): 167 Downloads/week (npm): 40 Forks (GitHub): 65 Stars (GitHub): 239 Not marked · First seen |
Listed Version: 1.0.5 Downloads/month (npm): 860 Downloads/week (npm): 860 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | x402 Universal Payer | callx402 MCP server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 239 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 65 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-16 |
| Where it runs (differs) | On your machine (@three-ws/mcp-bridge) | On your machine (callx402) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 13, secrets among them: 2 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/nirholas/three.ws | github.com/payloadhq/callx402 |
| Changes in the last 7 days (differs) | 0 | 3 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
x402 Universal Payer
Pay any x402 endpoint on the open web: auto-paying bridge with Bazaar discovery and spend caps.
callx402 MCP server
Read-only x402 payment diagnostics: diagnose, evidence, explain, recover, resolve, status. Zero deps
How to run each
x402 Universal Payer As a local MCP server: npm package
claude mcp add --env "MCP_BRIDGE_EVM_PRIVATE_KEY=<YOUR_MCP_BRIDGE_EVM_PRIVATE_KEY>" --env "MCP_BRIDGE_SVM_PRIVATE_KEY=<YOUR_MCP_BRIDGE_SVM_PRIVATE_KEY>" --transport stdio x402-bridge -- npx -y @three-ws/mcp-bridgeRequires: MCP_BRIDGE_EVM_PRIVATE_KEY (secret), MCP_BRIDGE_SVM_PRIVATE_KEY (secret)
callx402 MCP server As a local MCP server: npm package
claude mcp add --transport stdio callx402 -- npx -y callx402Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of callx402 MCP server publish no settings it asks for, so we do not compare settings.
What it can do: x402 Universal Payer · What it can do: callx402 MCP server · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.