Ext Ops Panel
Open dashboard
Comparison

A-Pay Protocol vs io.github.pay-skill/pay-mcp

A-Pay Protocol is an MCP server published by neuralaisofficial-lang. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.pay-skill/pay-mcp is an MCP server published by pay-skill. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-05. 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
MarketplaceA-Pay Protocolio.github.pay-skill/pay-mcp
Official MCP Registry Listed
Version: 0.1.8
Downloads/month (PyPI): 897
Downloads/week (PyPI): 345
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.2.8
Downloads/month (npm): 526
Downloads/week (npm): 175
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

A-Pay Protocol vs io.github.pay-skill/pay-mcp
FactA-Pay Protocolio.github.pay-skill/pay-mcp
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (apay-network.vercel.app/api/mcp)On your machine (@pay-skill/mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)5, secrets among them: 12, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/neuralaisofficial-lang/a_paygithub.com/pay-skill/pay-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 2 h agono 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

A-Pay Protocol

In its own words, on Official MCP Registry:

Universal HTTP 402 Micropayment Protocol & Autonomous Economic Settlement Engine for AI Agents

io.github.pay-skill/pay-mcp

In its own words, on Official MCP Registry:

USDC payments for AI agents on Base — direct, tabs, x402 paywalls, discovery

How to run each

A-Pay Protocol As a remote MCP server

Claude Code
claude mcp add --transport http apay https://apay-network.vercel.app/api/mcp

Requires: APAY_PRIVATE_KEY (secret)

io.github.pay-skill/pay-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "PAYSKILL_SIGNER_KEY=<YOUR_PAYSKILL_SIGNER_KEY>" --transport stdio pay-mcp -- npx -y @pay-skill/mcp

Requires: PAYSKILL_SIGNER_KEY (secret)

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

Only A-Pay Protocol 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 A-Pay Protocol asks for

  • APAY_CURRENCY
  • APAY_DAILY_BUDGET
  • APAY_MAX_PER_CALL
  • APAY_NETWORK
  • APAY_PRIVATE_KEY (secret)

Only io.github.pay-skill/pay-mcp asks for

  • PAYSKILL_SIGNER_KEY (secret)
  • PAY_NETWORK

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

What it can do: A-Pay Protocol · What it can do: io.github.pay-skill/pay-mcp · 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