Dodo Payments vs Keyban Agent Wallet
Dodo Payments is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Keyban Agent Wallet is an MCP server published by mcp.keyban.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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 | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.2 Downloads/month (npm): 1 121 Downloads/week (npm): 392 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 | Dodo Payments | Keyban Agent Wallet |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release (differs) | Not published | 2026-11-06 |
| Where it runs (differs) | Remote server (mcp.dodopayments.com/sse) | On your machine (@keyban/cli) |
| Transport (differs) | SSE | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 10, secrets among them: 3 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository | Not stated | Not stated |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen (differs) | 2026-10-11 | 2026-10-15 |
| Endpoint at the last check (differs) | Answered with HTTP 404 (20 h ago) | no remote endpoint we check |
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
Dodo Payments
Tools for cross-border payments, taxes, and compliance.
Keyban Agent Wallet
Give an AI agent its own blockchain wallet: balances, USDC transfers, x402 payments under policy.
How to run each
Dodo Payments As a remote MCP server
claude mcp add --transport sse dodo-payments https://mcp.dodopayments.com/sse
Requires: DODO_PAYMENTS_API_KEY (secret)
Keyban Agent Wallet As a local MCP server: npm package
claude mcp add --env "KEYBAN_API_KEY=<YOUR_KEYBAN_API_KEY>" --env "KEYBAN_APP_ID=<YOUR_KEYBAN_APP_ID>" --env "KEYBAN_DKG_BLOB=<YOUR_KEYBAN_DKG_BLOB>" --env "KEYBAN_INVITE_KEY=<YOUR_KEYBAN_INVITE_KEY>" --env "KEYBAN_NETWORK=<YOUR_KEYBAN_NETWORK>" --transport stdio agent-wallet -- npx -y @keyban/cli mcp
Requires: KEYBAN_API_KEY (secret), KEYBAN_APP_ID, KEYBAN_DKG_BLOB (secret), KEYBAN_INVITE_KEY (secret), KEYBAN_NETWORK
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Dodo Payments has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only Dodo Payments asks for
DODO_PAYMENTS_API_KEY (secret)
Only Keyban Agent Wallet asks for
KEYBAN_API_KEY (secret)KEYBAN_APP_IDKEYBAN_BASE_URLKEYBAN_DKG_BLOB (secret)KEYBAN_FUNDINGKEYBAN_INVITE_KEY (secret)KEYBAN_NETWORKKEYBAN_WALLET_ADDRESSMCP_LOG_FILEMCP_LOG_LEVEL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Dodo Payments · What it can do: Keyban Agent Wallet · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.