Ext Ops Panel
Open dashboard
Comparison

vault-ask vs 1Claw Vault

vault-ask is an MCP server published by erseni.com. Marketplaces we read that list it: 1 (Official MCP Registry). 1Claw Vault is an MCP server published by 1clawAI. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-30. 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

Where each is published
Marketplacevault-ask1Claw Vault
Official MCP Registry Listed
Version: 0.2.1
Downloads/month (npm): 130
Downloads/week (npm): 130
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.56.3
Downloads/month (npm): 5 537
Downloads/week (npm): 427
Forks (GitHub): 3
Stars (GitHub): 3
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.64.1
Downloads/month (npm): 5 537
Downloads/week (npm): 427
Forks (GitHub): 3
Stars (GitHub): 3
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

vault-ask vs 1Claw Vault
Factvault-ask1Claw Vault
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)3 (better)
Forks (GitHub) (differs)0 (worse)3 (better)
Last release (differs)2026-10-20 (worse)2026-10-24 (better)
Where it runs (differs)On your machine (@erseni/vault-ask)On your machine (@1claw/mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 15, secrets among them: 1
Licence (differs)Not statedMIT
Repository (differs)github.com/erseni/secrets-componentgithub.com/1clawai/1claw-mcp
Changes in the last 7 days (differs)01
First seen (differs)2026-10-192026-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

vault-ask

In its own words, on Official MCP Registry:

Request and send secrets for AI agents, end-to-end encrypted and never shown in the chat.

1Claw Vault

In its own words, on Official MCP Registry:

HSM-backed vault secrets for AI agents (JIT fetch) plus prompt-injection and threat scanning.

How to run each

vault-ask As a local MCP server: npm package

Claude Code
claude mcp add --env "VAULT_ASK_API_KEY=<YOUR_VAULT_ASK_API_KEY>" --transport stdio vault-ask -- npx -y @erseni/vault-ask mcp

Requires: VAULT_ASK_API_KEY (secret)

1Claw Vault As a local MCP server: npm package

Claude Code
claude mcp add --env "ONECLAW_AGENT_API_KEY=<YOUR_ONECLAW_AGENT_API_KEY>" --transport stdio 1claw-mcp -- npx -y @1claw/mcp

Requires: ONECLAW_AGENT_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 vault-ask asks for

  • VAULT_ASK_API_KEY (secret)
  • VAULT_ASK_SERVER

Only 1Claw Vault asks for

  • ONECLAW_AGENT_API_KEY (secret)
  • ONECLAW_AGENT_ID
  • ONECLAW_BASE_URL
  • ONECLAW_LOCAL_ONLY
  • ONECLAW_VAULT_ID

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: vault-ask · What it can do: 1Claw Vault · 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.

Where the data comes from: how the catalog is built