Ext Ops Panel
Open dashboard
Comparison

CRA AGENT vs io.github.up2itnow0822/clawpay

CRA AGENT is an MCP server published by giupy997. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.up2itnow0822/clawpay 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
MarketplaceCRA AGENTio.github.up2itnow0822/clawpay
Official MCP Registry Listed
Version: 0.0.11
Downloads/month (npm): 2 724
Downloads/week (npm): 78
Forks (GitHub): 1
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 3.0.1
Downloads/month (npm): 267
Downloads/week (npm): 122
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

CRA AGENT vs io.github.up2itnow0822/clawpay
FactCRA AGENTio.github.up2itnow0822/clawpay
Marketplaces that list it11
Stars (GitHub) (differs)1 (worse)8 (better)
Forks (GitHub) (differs)1 (worse)4 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@cra-agent/mcp)On your machine (clawpay-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)5, secrets among them: 02, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/giupy997/arcagentx402github.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

CRA AGENT

In its own words, on Official MCP Registry:

Lets an agent pay for x402 APIs in USDC on Arc, under a spending policy it cannot change.

io.github.up2itnow0822/clawpay

In its own words, on Official MCP Registry:

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

How to run each

CRA AGENT As a local MCP server: npm package

Claude Code
claude mcp add --env "CRA_KEY_FILE=<YOUR_CRA_KEY_FILE>" --env "CRA_NETWORK=<YOUR_CRA_NETWORK>" --transport stdio cra-agent -- npx -y @cra-agent/mcp

Requires: CRA_KEY_FILE, CRA_NETWORK

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

Claude Code
claude mcp add --env "AGENT_PRIVATE_KEY=<YOUR_AGENT_PRIVATE_KEY>" --transport stdio clawpay -- npx -y clawpay-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 CRA AGENT asks for

  • CRA_KEY_FILE
  • CRA_NETWORK
  • CRA_POLICY
  • CRA_RPC_URL
  • DATABASE_URL

Only io.github.up2itnow0822/clawpay asks for

  • AGENT_PRIVATE_KEY (secret)
  • BASE_RPC_URL

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

What it can do: CRA AGENT · What it can do: io.github.up2itnow0822/clawpay · 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