Ext Ops Panel
Open dashboard
Comparison

io.github.Evozim/m2mcent vs io.github.up2itnow0822/agentpay

io.github.Evozim/m2mcent is an MCP server published by Evozim. 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-23. 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.Evozim/m2mcentio.github.up2itnow0822/agentpay
Official MCP Registry Listed
Version: 1.0.5
Downloads/month (npm): 112
Downloads/week (npm): 10
Forks (GitHub): 0
Stars (GitHub): 0
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

io.github.Evozim/m2mcent vs io.github.up2itnow0822/agentpay
Factio.github.Evozim/m2mcentio.github.up2itnow0822/agentpay
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)8 (better)
Forks (GitHub) (differs)0 (worse)4 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (m2mcent-sdk)On your machine (agentpay-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)3, secrets among them: 12, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/evozim/m2mcent-sdkgithub.com/up2itnow0822/agentpay-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.Evozim/m2mcent

In its own words, on Official MCP Registry:

x402 payment wrapper for AI Agents and MCP Servers. USDC settlements on Base L2.

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

io.github.Evozim/m2mcent As a local MCP server: npm package

Claude Code
claude mcp add --env "BASE_RPC_URL=<YOUR_BASE_RPC_URL>" --env "RELAYER_PRIVATE_KEY=<YOUR_RELAYER_PRIVATE_KEY>" --env "TREASURY_ADDRESS=<YOUR_TREASURY_ADDRESS>" --transport stdio m2mcent -- npx -y m2mcent-sdk

Requires: BASE_RPC_URL, RELAYER_PRIVATE_KEY (secret), TREASURY_ADDRESS

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.

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.Evozim/m2mcent asks for

  • RELAYER_PRIVATE_KEY (secret)
  • TREASURY_ADDRESS

Only io.github.up2itnow0822/agentpay asks for

  • AGENT_PRIVATE_KEY (secret)

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

What it can do: io.github.Evozim/m2mcent · 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