VibeDNA Vault vs org.proxykey/proxykey
VibeDNA Vault is an MCP server published by marstudio360. Marketplaces we read that list it: 1 (Official MCP Registry). org.proxykey/proxykey is an MCP server published by proxykey.org. 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 |  VibeDNA Vault |  org.proxykey/proxykey |
|---|---|---|
| Official MCP Registry | Listed Version: 1.1.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.0.0 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 | VibeDNA Vault | org.proxykey/proxykey |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (https://github.com/marstudio360/vibedna-vault-mcp/releases/download/v1.1.1/vibedna-vault-mcp-1.1.1.mcpb) | Remote server (mcp.proxykey.org/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 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/marstudio360/vibedna-vault-mcp | github.com/neostorm112-boop/proxykey-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 days 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
VibeDNA Vault
Encrypted local vault for API keys. Your AI fetches keys on demand and scans code for leaks.
org.proxykey/proxykey
Issue, rotate and revoke scoped API-key passes for 25+ providers — the agent never sees a real key
How to run each
VibeDNA Vault
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: VAULT_MASTER_PASSWORD (secret)
org.proxykey/proxykey As a remote MCP server
claude mcp add --transport http proxykey https://mcp.proxykey.org/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only org.proxykey/proxykey 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 org.proxykey/proxykey publish no settings it asks for, so we do not compare settings.
What it can do: VibeDNA Vault · What it can do: org.proxykey/proxykey · 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.