Ext Ops Panel
Open dashboard
Comparison

Dodo Payments vs Jupiter Invoice

Dodo Payments is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Jupiter Invoice is an MCP server published by jupiterinvoice.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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 PaymentsJupiter Invoice
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
No figure published
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 Jupiter Invoice
FactDodo PaymentsJupiter Invoice
Marketplaces that list it11
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.dodopayments.com/sse)Remote server (jupiterinvoice.com/mcp)
Transport (differs)SSEStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/middlefieldgs/jupiterinvoice
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 35 h ago, requires a keyResponded 47 h ago

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.

Jupiter Invoice

In its own words, on Official MCP Registry:

Create and manage invoices and customers on Jupiter Invoice (MCP, API-key auth).

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)

Jupiter Invoice As a remote MCP server

Claude Code
claude mcp add --transport http jupiter-invoice https://jupiterinvoice.com/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Both endpoints responded at the last daily 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

The marketplaces of Jupiter Invoice publish no settings it asks for, so we do not compare settings.

What it can do: Dodo Payments · What it can do: Jupiter Invoice · 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