MnemoPay vs com.vevang/agents
MnemoPay is an MCP server published by mnemopay.com. Marketplaces we read that list it: 3 (Official MCP Registry, Claude Code: claude-plugins-community, npm registry (MCP servers)). com.vevang/agents is an MCP server published by vevang.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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 |  MnemoPay |  com.vevang/agents |
|---|---|---|
| Official MCP Registry | Listed Version: 1.15.2 Downloads/month (npm): 1 931 Downloads/week (npm): 596 Forks (GitHub): 4 Stars (GitHub): 9 Not marked · First seen |
Listed Version: 1.0.0 No figure published Not marked · First seen |
| Claude Code: claude-plugins-community | Listed Version: 1.2.0 Forks (GitHub): 4 Stars (GitHub): 9 Not marked · First seen |
Not listed |
| npm registry (MCP servers) | Listed Version: 1.16.0 Downloads/month (npm): 1 931 Downloads/week (npm): 596 Forks (GitHub): 4 Stars (GitHub): 9 Not marked · First seen |
Not listed |
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 | MnemoPay | com.vevang/agents |
|---|---|---|
| Marketplaces that list it (differs) | 3 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 9 | No figure on GitHub |
| Forks (GitHub) (differs) | 4 | No figure on GitHub |
| Last release (differs) | 2026-11-10 | Not published |
| Where it runs (differs) | On your machine (@mnemopay/sdk) | Remote server (mcp.vevang.com/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | 9 | Not a bundle |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/mnemopay/mnemopay-sdk | Not stated |
| Changes in the last 7 days (differs) | 1 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 46 h ago returned HTTP 406 |
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
MnemoPay
Governance and audit layer for AI agents: policy, approvals, tamper-evident audit chains.
com.vevang/agents
Hire Vevang's AI agents, pay-per-call in USDC on Base via x402: video, visibility, verify, extract
How to run each
MnemoPay As a local MCP server: npm package
claude mcp add --env "MNEMOPAY_API_KEY=<YOUR_MNEMOPAY_API_KEY>" --transport stdio sdk -- npx -y mnemopay-mcp @mnemopay/sdkRequires: MNEMOPAY_API_KEY (secret)
com.vevang/agents As a remote MCP server
claude mcp add --transport http agents https://mcp.vevang.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only com.vevang/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
The marketplaces of com.vevang/agents publish no settings it asks for, so we do not compare settings.
What it can do: MnemoPay · What it can do: com.vevang/agents · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.