Ext Ops Panel
Open dashboard
Comparison

Coal — Payments for AI agents vs io.github.up2itnow0822/agentpay

Coal — Payments for AI agents is an MCP server published by emmanuel39hanks. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.up2itnow0822/agentpay is an MCP server published by up2itnow0822. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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
MarketplaceCoal — Payments for AI agentsio.github.up2itnow0822/agentpay
Official MCP Registry Listed
Version: 1.3.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 3.1.0
Downloads/month (npm): 1 066
Downloads/week (npm): 445
Forks (GitHub): 4
Stars (GitHub): 8
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

Coal — Payments for AI agents vs io.github.up2itnow0822/agentpay
FactCoal — Payments for AI agentsio.github.up2itnow0822/agentpay
Marketplaces that list it11
Stars (GitHub) (differs)1 (worse)8 (better)
Forks (GitHub) (differs)0 (worse)4 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.usecoal.xyz/api/mcp)On your machine (agentpay-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/emmanuel39hanks/coalgithub.com/up2itnow0822/agentpay-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Not responding since 2026-10-26no 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

Coal — Payments for AI agents

In its own words, on Official MCP Registry:

Payment rails for AI agents. Pay merchants in USDC on Base. Dual-protocol: x402 + OKX APP.

io.github.up2itnow0822/agentpay

In its own words, on Official MCP Registry:

Non-custodial x402 payment MCP server for AI agents. Wallets and payments on 17 chains.

How to run each

Coal — Payments for AI agents As a remote MCP server

Claude Code
claude mcp add --transport http coal https://mcp.usecoal.xyz/api/mcp --header "X-Coal-Agent-Key: <YOUR_X_COAL_AGENT_KEY>" --header "X-Coal-Api-Key: <YOUR_X_COAL_API_KEY>"

Requires: X-Coal-Agent-Key header, X-Coal-Api-Key header

io.github.up2itnow0822/agentpay As a local MCP server: npm package

Claude Code
claude mcp add --env "AGENT_PRIVATE_KEY=<YOUR_AGENT_PRIVATE_KEY>" --transport stdio agentpay -- npx -y agentpay-mcp

Requires: AGENT_PRIVATE_KEY (secret)

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

Only Coal — Payments for AI agents 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 Coal — Payments for AI agents publish no settings it asks for, so we do not compare settings.

What it can do: Coal — Payments for AI agents · What it can do: io.github.up2itnow0822/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