Ext Ops Panel
Open dashboard
Comparison

io.github.alefnt/agentpay vs Obolus

io.github.alefnt/agentpay is an MCP server published by alefnt. Marketplaces we read that list it: 1 (Official MCP Registry). Obolus is an MCP server published by inviti8. 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
Marketplaceio.github.alefnt/agentpayObolus
Official MCP Registry Listed
Version: 0.1.1
Downloads/month (npm): 138
Downloads/week (npm): 30
Forks (GitHub): 1
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.2.3
Downloads/month (PyPI): 116
Downloads/week (PyPI): 32
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.alefnt/agentpay vs Obolus
Factio.github.alefnt/agentpayObolus
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@agentpay-dev/mcp-server)On your machine (obolus)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 02, secrets among them: 0
Licence (differs)Not statedApache-2.0
Repository (differs)github.com/alefnt/agentpaygithub.com/inviti8/obolus
Changes in the last 7 days (differs)04
First seen2026-10-112026-10-11

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.alefnt/agentpay

In its own words, on Official MCP Registry:

AI Agent payment protocol on CKB Fiber Network. Zero-gas micropayments with Hold Invoice escrow.

Obolus

In its own words, on Official MCP Registry:

Disposable Algorand wallet for AI agents. Pay x402 resources in USDC, no human provisioning.

How to run each

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

Claude Code
claude mcp add --env "FIBER_RPC_URL=<YOUR_FIBER_RPC_URL>" --transport stdio agentpay -- npx -y @agentpay-dev/mcp-server

Requires: FIBER_RPC_URL

Obolus As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio obolus -- uvx obolus mcp

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only io.github.alefnt/agentpay asks for

  • FIBER_RPC_URL

Only Obolus asks for

  • OBOLUS_DATA_DIR
  • OBOLUS_NETWORK

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

What it can do: io.github.alefnt/agentpay · What it can do: Obolus · Compare two other plugins

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