Ext Ops Panel
Open dashboard
Comparison

Dodo Payments vs io.github.Openfinanceorg/openfinance

Dodo Payments is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.Openfinanceorg/openfinance is an MCP server published by Openfinanceorg. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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 Paymentsio.github.Openfinanceorg/openfinance
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.0
Downloads/month (npm): 130
Downloads/week (npm): 27
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 io.github.Openfinanceorg/openfinance
FactDodo Paymentsio.github.Openfinanceorg/openfinance
Marketplaces that list it11
Last release (differs)Not published2026-10-12
Where it runs (differs)Remote server (mcp.dodopayments.com/sse)On your machine (@openfinance-sh/mcp)
Transport (differs)SSEstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 12, secrets among them: 1
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/openfinanceorg/openfinance-app
Changes in the last 7 days (differs)01
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 15 h 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.

io.github.Openfinanceorg/openfinance

In its own words, on Official MCP Registry:

Connect your financial accounts to view balances, search transactions, and get spending insights.

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)

io.github.Openfinanceorg/openfinance As a local MCP server: npm package

Claude Code
claude mcp add --env "OPENFINANCE_API_KEY=<YOUR_OPENFINANCE_API_KEY>" --transport stdio openfinance -- npx -y @openfinance-sh/mcp

Requires: OPENFINANCE_API_KEY (secret)

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 io.github.Openfinanceorg/openfinance asks for

  • OPENFINANCE_API_KEY (secret)
  • OPENFINANCE_URL

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

What it can do: Dodo Payments · What it can do: io.github.Openfinanceorg/openfinance · 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.

Where the data comes from: how the catalog is built