Ext Ops Panel
Open dashboard
Comparison

Dodo Payments vs AgentPay — trust routing + spend caps for x402 agents

Dodo Payments is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). AgentPay — trust routing + spend caps for x402 agents is an MCP server published by romudille-bit. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-16. 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 PaymentsAgentPay — trust routing + spend caps for x402 agents
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.7.3
Downloads/month (npm): 899
Downloads/week (npm): 130
Forks (GitHub): 1
Stars (GitHub): 4
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 AgentPay — trust routing + spend caps for x402 agents
FactDodo PaymentsAgentPay — trust routing + spend caps for x402 agents
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub4
Forks (GitHub) (differs)No figure on GitHub1
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.dodopayments.com/sse)Remote server or your machine
Transport (differs)SSEStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 13, secrets among them: 1
Parts of the bundle (differs)Not a bundle3
Licence (differs)Apache-2.0MIT
Repository (differs)Not statedgithub.com/romudille-bit/agentpay
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 2 days ago, requires a keynot checked yet

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.

AgentPay — trust routing + spend caps for x402 agents

In its own words, on Official MCP Registry:

Buyer-side trust oracle + capped sessions for x402 agents: verified_route, receipts, 17 free tools.

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)

AgentPay — trust routing + spend caps for x402 agents As a remote MCP server

Claude Code
claude mcp add --transport http agentpay https://agentpay.tools/mcp

Requires: AGENTPAY_BASE_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 AgentPay — trust routing + spend caps for x402 agents asks for

  • AGENTPAY_BASE_KEY (secret)
  • AGENTPAY_ENABLE_PAID
  • AGENTPAY_MAX_SPEND

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

What it can do: Dodo Payments · What it can do: AgentPay — trust routing + spend caps for x402 agents · 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. Data comes from public marketplace files in GitHub repositories of their authors. 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