Ext Ops Panel
Open dashboard
Comparison

Dodo Payments vs mnemopay

Dodo Payments is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). mnemopay is a plugin bundle for AI coding tools published by mnemopay. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-25. 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

Where each is published
MarketplaceDodo Paymentsmnemopay
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 1.2.0
Forks (GitHub): 4
Stars (GitHub): 8
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

Dodo Payments vs mnemopay
FactDodo Paymentsmnemopay
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub8
Forks (GitHub) (differs)No figure on GitHub4
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.dodopayments.com/sse)On your machine (@mnemopay/sdk)
Transport (differs)SSENot stated
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 11, secrets among them: 0
Parts of the bundle (differs)Not a bundle9
LicenceApache-2.0Apache-2.0
Repository (differs)Not statedgithub.com/mnemopay/mnemopay-sdk
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 5 days ago, requires a keyno 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

In its own words, on Docker MCP Catalog:

Tools for cross-border payments, taxes, and compliance.

mnemopay

In its own words, on Claude Code: claude-plugins-community:

Payment infrastructure for AI agents. Agent Credit Score (300-850), real payment rails (Stripe/Paystack/Lightning), autonomous shopping with escrow, hash-chained ledger, and behavioral finance. Charge for tool usage, track spending, shop autonomously, and build agent creditworthiness all from Claude Code.

How to run each

Dodo Payments As a remote MCP server

Claude Code
claude mcp add --transport sse dodo-payments https://mcp.dodopayments.com/sse

Requires: DODO_PAYMENTS_API_KEY (secret)

mnemopay As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install mnemopay@claude-community

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 mnemopay asks for

  • MNEMOPAY_PERSIST_DIR

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Dodo Payments · What it can do: mnemopay · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built