1Claw Vault vs io.github.stephenballot-ai/legacy-shield
1Claw Vault is an MCP server published by 1clawAI. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). io.github.stephenballot-ai/legacy-shield is an MCP server published by stephenballot-ai. 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 |  1Claw Vault |   io.github.stephenballot-ai/legacy-shield |
|---|---|---|
| Official MCP Registry | Listed Version: 0.56.3 Downloads/month (npm): 3 784 Downloads/week (npm): 443 Forks (GitHub): 3 Stars (GitHub): 4 Not marked · First seen |
Listed Version: 1.0.3 Downloads/month (npm): 157 Downloads/week (npm): 50 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 0.64.1 Downloads/month (npm): 3 784 Downloads/week (npm): 443 Forks (GitHub): 3 Stars (GitHub): 4 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 | 1Claw Vault | io.github.stephenballot-ai/legacy-shield |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 4 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 3 (better) | 0 (worse) |
| Last release (differs) | 2026-10-24 | Not published |
| Where it runs (differs) | On your machine (@1claw/mcp) | On your machine (@legacy-shield/mcp-server) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 5, secrets among them: 1 | 2, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/1clawai/1claw-mcp | github.com/stephenballot-ai/legacy-shield |
| Changes in the last 7 days | 0 | 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
1Claw Vault
HSM-backed vault secrets for AI agents (JIT fetch) plus prompt-injection and threat scanning.
io.github.stephenballot-ai/legacy-shield
Zero-knowledge encrypted vault for AI agents. EU-hosted persistent storage.
How to run each
1Claw Vault As a local MCP server: npm package
claude mcp add --env "ONECLAW_AGENT_API_KEY=<YOUR_ONECLAW_AGENT_API_KEY>" --transport stdio 1claw-mcp -- npx -y @1claw/mcpRequires: ONECLAW_AGENT_API_KEY (secret)
io.github.stephenballot-ai/legacy-shield As a local MCP server: npm package
claude mcp add --env "LEGACY_SHIELD_API_KEY=<YOUR_LEGACY_SHIELD_API_KEY>" --transport stdio legacy-shield -- npx -y @legacy-shield/mcp-serverRequires: LEGACY_SHIELD_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
Only 1Claw Vault asks for
ONECLAW_AGENT_API_KEY (secret)ONECLAW_AGENT_IDONECLAW_BASE_URLONECLAW_LOCAL_ONLYONECLAW_VAULT_ID
Only io.github.stephenballot-ai/legacy-shield asks for
LEGACY_SHIELD_API_KEY (secret)LEGACY_SHIELD_API_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: 1Claw Vault · What it can do: io.github.stephenballot-ai/legacy-shield · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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.