io.github.Dempty-glitch/z-zero-mcp vs io.github.Evozim/m2mcent
io.github.Dempty-glitch/z-zero-mcp is an MCP server published by Dempty-glitch. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.Evozim/m2mcent is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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 |  io.github.Dempty-glitch/z-zero-mcp |  io.github.Evozim/m2mcent |
|---|---|---|
| Official MCP Registry | Listed Version: 1.10.4 Downloads/month (npm): 608 Downloads/week (npm): 38 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 1.0.5 Downloads/month (npm): 112 Downloads/week (npm): 10 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
| Fact | io.github.Dempty-glitch/z-zero-mcp | io.github.Evozim/m2mcent |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-23 | Not published |
| Where it runs (differs) | On your machine (z-zero-mcp-server) | On your machine (m2mcent-sdk) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 3, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/dempty-glitch/z-zero-mcp | github.com/evozim/m2mcent-sdk |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen | 2026-10-11 | 2026-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.Dempty-glitch/z-zero-mcp
Payments for AI agents: gasless USDC on Base + JIT single-use virtual cards, PAN never in context.
io.github.Evozim/m2mcent
x402 payment wrapper for AI Agents and MCP Servers. USDC settlements on Base L2.
How to run each
io.github.Dempty-glitch/z-zero-mcp As a local MCP server: npm package
claude mcp add --env "Z_ZERO_API_KEY=<YOUR_Z_ZERO_API_KEY>" --transport stdio z-zero-mcp -- npx -y z-zero-mcp-serverRequires: Z_ZERO_API_KEY (secret)
io.github.Evozim/m2mcent As a local MCP server: npm package
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-sdkRequires: BASE_RPC_URL, RELAYER_PRIVATE_KEY (secret), TREASURY_ADDRESS
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.Dempty-glitch/z-zero-mcp asks for
Z_ZERO_API_KEY (secret)
Only io.github.Evozim/m2mcent asks for
BASE_RPC_URLRELAYER_PRIVATE_KEY (secret)TREASURY_ADDRESS
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.Dempty-glitch/z-zero-mcp · What it can do: io.github.Evozim/m2mcent · 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.