Plugged.in Proxy vs com.mnemopay/sdk
Plugged.in Proxy is an MCP server published by VeriTeknik. Marketplaces we read that list it: 1 (Docker MCP Catalog). com.mnemopay/sdk is an MCP server published by mnemopay.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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 |  Plugged.in Proxy |  com.mnemopay/sdk |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:b7c32590b270 Forks (GitHub): 30 Pulls (Docker Hub): 36 146 Stars (Docker Hub): 3 Stars (GitHub): 138 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.14.2 Downloads/month (npm): 908 Downloads/week (npm): 119 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 | Plugged.in Proxy | com.mnemopay/sdk |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 138 (better) | 8 (worse) |
| Pulls (Docker Hub) (differs) | 36 146 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 30 (better) | 4 (worse) |
| Last release (differs) | Not published | 2026-10-24 |
| Where it runs (differs) | On your machine (mcp/pluggedin-mcp-proxy) | On your machine (@mnemopay/sdk) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 6 | Not published |
| Environment variables it asks for | 2, secrets among them: 1 | 2, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/veriteknik/pluggedin-mcp-proxy | github.com/mnemopay/mnemopay-sdk |
| Changes in the last 7 days (differs) | 0 | 3 |
| 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
Plugged.in Proxy
A unified MCP proxy that aggregates multiple MCP servers into one interface, enabling seamless tool discovery and management across all your AI interactions. Manage all your MCP servers from a single connection point with RAG capabilities and real-time notifications.
com.mnemopay/sdk
Trust OS for AI agents: governed memory, payments, reputation, approvals, and audit evidence.
How to run each
Plugged.in Proxy As a local MCP server: Docker image
claude mcp add --env "PLUGGEDIN_API_KEY=<YOUR_PLUGGEDIN_API_KEY>" --transport stdio pluggedin-mcp-proxy -- docker run -i --rm -e PLUGGEDIN_API_KEY mcp/pluggedin-mcp-proxyRequires: PLUGGEDIN_API_KEY (secret)
com.mnemopay/sdk 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
The marketplaces of com.mnemopay/sdk publish no list of tools, so we do not compare tools.
Settings each asks for
Only Plugged.in Proxy asks for
PLUGGEDIN_API_BASE_URLPLUGGEDIN_API_KEY (secret)
Only com.mnemopay/sdk asks for
MNEMOPAY_API_KEY (secret)MNEMOPAY_PERSIST_DIR
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Plugged.in Proxy · What it can do: com.mnemopay/sdk · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.