Ext Ops Panel
Open dashboard
Comparison

AgentPays vs io.github.kar69-96/agentpay

AgentPays is an MCP server published by agentpays.dev. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.kar69-96/agentpay is an MCP server published by kar69-96. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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
MarketplaceAgentPaysio.github.kar69-96/agentpay
Official MCP Registry Listed, marked deprecated
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 0.1.8
Downloads/month (npm): 72
Downloads/week (npm): 12
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

AgentPays vs io.github.kar69-96/agentpay
FactAgentPaysio.github.kar69-96/agentpay
Marketplaces that list it11
Last releaseNot publishedNot published
Where it runs (differs)Remote server (agentpays.dev/api/mcp)On your machine (@useagentpay/mcp-server)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 2
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/kar69-96/useagentpay
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Answered with HTTP 308 (19 h ago)no 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

AgentPays

In its own words, on Official MCP Registry:

Payment infrastructure for AI agents: spending rules, approval flows, single-use virtual cards.

io.github.kar69-96/agentpay

In its own words, on Official MCP Registry:

AI agent payments with human approval. Local-first, encrypted credentials, budget controls.

How to run each

AgentPays As a remote MCP server

Claude Code
claude mcp add --transport http agentpays https://agentpays.dev/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

io.github.kar69-96/agentpay As a local MCP server: npm package

Claude Code
claude mcp add --env "AGENTPAY_PASSPHRASE=<YOUR_AGENTPAY_PASSPHRASE>" --env "ANTHROPIC_API_KEY=<YOUR_ANTHROPIC_API_KEY>" --transport stdio agentpay -- npx -y @useagentpay/mcp-server

Requires: AGENTPAY_PASSPHRASE (secret), ANTHROPIC_API_KEY (secret)

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

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

What it can do: AgentPays · What it can do: io.github.kar69-96/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