Ext Ops Panel
Open dashboard
Comparison

Dodo Payments vs tres-finance-plugin

Dodo Payments is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). tres-finance-plugin is a plugin bundle for AI coding tools published by Nadav Gilliam. 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 Paymentstres-finance-plugin
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.12.1
Forks (GitHub): 343
Stars (GitHub): 4 759
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 tres-finance-plugin
FactDodo Paymentstres-finance-plugin
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub4 759
Forks (GitHub) (differs)No figure on GitHub343
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.dodopayments.com/sse)Remote server (ai.tres.finance/mcp)
Transport (differs)SSEStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle23
Licence (differs)Apache-2.0MIT
Repository (differs)Not statedgithub.com/anthropics/claude-plugins-community
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-12
Endpoint at the last check (differs)Responded 5 days ago, requires a keyResponded 3 days ago, requires a key

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.

tres-finance-plugin

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

The first official TRES Finance plugin for Claude Code — blockchain accounting workflows, ledger management, and transaction analysis. Connects to the hosted TRES Finance MCP server; collects no usage telemetry. Privacy: https://tres.finance/privacy-policy/

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)

tres-finance-plugin As a Claude Code plugin

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

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 tres-finance-plugin publish no settings it asks for, so we do not compare settings.

What it can do: Dodo Payments · What it can do: tres-finance-plugin · 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