remit vs MnemoPay
remit is a plugin bundle for AI coding tools published by tonone-ai. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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)). As of our marketplace pass on 2026-11-09. 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 | |
|---|---|---|
| Community marketplace tonone-ai/tonone | Listed Version: 1.19.0 No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.15.2 Downloads/month (npm): 1 976 Downloads/week (npm): 317 Forks (GitHub): 4 Stars (GitHub): 8 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 1.2.0 Forks (GitHub): 4 Stars (GitHub): 8 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.15.2 Downloads/month (npm): 1 976 Downloads/week (npm): 317 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
| Fact | remit | MnemoPay |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 8 |
| Forks (GitHub) (differs) | No figure on GitHub | 4 |
| Last release (differs) | Not published | 2026-11-03 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@mnemopay/sdk) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Parts of the bundle (differs) | 4 | 9 |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/tonone-ai/tonone | github.com/mnemopay/mnemopay-sdk |
| Changes in the last 7 days (differs) | 2 | 5 |
| First seen (differs) | 2026-11-09 | 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
remit
Accounts payable and procure-to-pay — vendor onboarding, three-way match, payment runs, approvals, duplicate and fraud controls
MnemoPay
Governance and audit layer for AI agents: policy, approvals, tamper-evident audit chains.
How to run each
remit As a Claude Code plugin
/plugin marketplace add tonone-ai/tonone
/plugin install remit@tonone-aiMnemoPay 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)
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
The marketplaces of remit publish no settings it asks for, so we do not compare settings.
What it can do: remit · What it can do: MnemoPay · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.