CRA AGENT vs AgentPay — trust routing + spend caps for x402 agents
CRA AGENT is an MCP server published by giupy997. Marketplaces we read that list it: 1 (Official MCP Registry). AgentPay — trust routing + spend caps for x402 agents is an MCP server published by romudille-bit. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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
| Marketplace |  CRA AGENT |  AgentPay — trust routing + spend caps for x402 agents |
|---|---|---|
| Official MCP Registry | Listed Version: 0.0.11 Downloads/month (npm): 3 866 Downloads/week (npm): 324 Forks (GitHub): 1 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 2.7.3 Downloads/month (npm): 894 Downloads/week (npm): 133 Forks (GitHub): 1 Stars (GitHub): 4 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
| Fact | CRA AGENT | AgentPay — trust routing + spend caps for x402 agents |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (worse) | 4 (better) |
| Forks (GitHub) | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@cra-agent/mcp) | Remote server (agentpay.tools/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 5, secrets among them: 0 | 3, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/giupy997/arcagentx402 | github.com/romudille-bit/agentpay |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 14 h ago |
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
Lets an agent pay for x402 APIs in USDC on Arc, under a spending policy it cannot change.
AgentPay — trust routing + spend caps for x402 agents
Buyer-side trust oracle + capped sessions for x402 agents: verified_route, receipts, 17 free tools.
How to run each
CRA AGENT As a local MCP server: npm package
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/mcpRequires: CRA_KEY_FILE, CRA_NETWORK
AgentPay — trust routing + spend caps for x402 agents As a remote MCP server
claude mcp add --transport http agentpay https://agentpay.tools/mcpRequires: AGENTPAY_BASE_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only AgentPay — trust routing + spend caps for x402 agents 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 CRA AGENT asks for
CRA_KEY_FILECRA_NETWORKCRA_POLICYCRA_RPC_URLDATABASE_URL
Only AgentPay — trust routing + spend caps for x402 agents asks for
AGENTPAY_BASE_KEY (secret)AGENTPAY_ENABLE_PAIDAGENTPAY_MAX_SPEND
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: CRA AGENT · What it can do: AgentPay — trust routing + spend caps for x402 agents · 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.