Ext Ops Panel
Open dashboard
Comparison

io.github.codespar/mcp-circle vs io.github.stevemilton/payagent-mcp

io.github.codespar/mcp-circle is an MCP server published by codespar. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.stevemilton/payagent-mcp is an MCP server published by stevemilton. 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.codespar/mcp-circleio.github.stevemilton/payagent-mcp
Official MCP Registry Listed
Version: 0.2.2
Downloads/month (npm): 100
Downloads/week (npm): 26
Forks (GitHub): 51
Stars (GitHub): 273
Not marked · First seen
Listed
Version: 4.0.0
Downloads/month (npm): 722
Downloads/week (npm): 142
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.codespar/mcp-circle vs io.github.stevemilton/payagent-mcp
Factio.github.codespar/mcp-circleio.github.stevemilton/payagent-mcp
Marketplaces that list it11
Stars (GitHub) (differs)273 (better)0 (worse)
Forks (GitHub) (differs)51 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@codespar/mcp-circle)On your machine (@arispay/payagent-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 12, secrets among them: 2
LicenceNot statedNot stated
Repository (differs)github.com/codespar/mcp-dev-latamgithub.com/arispay-inc/payagent-mcp
Changes in the last 7 days00
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.codespar/mcp-circle

In its own words, on Official MCP Registry:

MCP server for Circle — USDC payments, wallets, payouts, transfers

io.github.stevemilton/payagent-mcp

In its own words, on Official MCP Registry:

Pay x402 APIs in USDC on Base, Solana, and BNB Chain with spend mandates, receipts, idempotency.

How to run each

io.github.codespar/mcp-circle As a local MCP server: npm package

Claude Code
claude mcp add --env "CIRCLE_API_KEY=<YOUR_CIRCLE_API_KEY>" --transport stdio mcp-circle -- npx -y @codespar/mcp-circle

Requires: CIRCLE_API_KEY (secret)

io.github.stevemilton/payagent-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "ARISPAY_API_KEY=<YOUR_ARISPAY_API_KEY>" --env "PAYAGENT_PRIVATE_KEY=<YOUR_PAYAGENT_PRIVATE_KEY>" --transport stdio payagent-mcp -- npx -y @arispay/payagent-mcp

Requires: ARISPAY_API_KEY (secret), PAYAGENT_PRIVATE_KEY (secret)

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.codespar/mcp-circle asks for

  • CIRCLE_API_KEY (secret)

Only io.github.stevemilton/payagent-mcp asks for

  • ARISPAY_API_KEY (secret)
  • PAYAGENT_PRIVATE_KEY (secret)

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

What it can do: io.github.codespar/mcp-circle · What it can do: io.github.stevemilton/payagent-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