Ext Ops Panel
Open dashboard
Comparison

io.github.joepangallo/agent-pay vs AgentPay

io.github.joepangallo/agent-pay is an MCP server published by joepangallo. Marketplaces we read that list it: 1 (Official MCP Registry). AgentPay is an MCP server published by zapnikita95. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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
Marketplaceio.github.joepangallo/agent-payAgentPay
Official MCP Registry Listed
Version: 1.1.2
Downloads/month (npm): 211
Downloads/week (npm): 30
Not marked · First seen
Listed
Version: 0.2.5
Forks (GitHub): 0
Stars (GitHub): 0
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

io.github.joepangallo/agent-pay vs AgentPay
Factio.github.joepangallo/agent-payAgentPay
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp-server-agentpay)Remote server (agentpay.shop/ap/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)3, secrets among them: 2Not published
LicenceNot statedNot stated
Repository (differs)github.com/joepangallo/agent-paygithub.com/zapnikita95/agentpay-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 404 (3 days 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

io.github.joepangallo/agent-pay

In its own words, on Official MCP Registry:

Payment gateway for AI agents with tool discovery, provisioning, metering, and reliability tools.

AgentPay

In its own words, on Official MCP Registry:

RU merchant catalog for AI agents: live price, stock, choices and controlled checkout. Not x402.

How to run each

io.github.joepangallo/agent-pay As a local MCP server: npm package

Claude Code
claude mcp add --env "AGENTPAY_ADMIN_KEY=<YOUR_AGENTPAY_ADMIN_KEY>" --env "AGENTPAY_GATEWAY_KEY=<YOUR_AGENTPAY_GATEWAY_KEY>" --transport stdio agent-pay -- npx -y mcp-server-agentpay

Requires: AGENTPAY_ADMIN_KEY (secret), AGENTPAY_GATEWAY_KEY (secret)

AgentPay As a remote MCP server

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

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

Only AgentPay 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

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

What it can do: io.github.joepangallo/agent-pay · What it can do: AgentPay · Compare two other plugins

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