Vaultshell vs 1Claw Vault — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Vaultshell vs 1Claw Vault
In-depth architectural comparison of the Vaultshell and 1Claw Vault MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Vaultshell
Security · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
1Claw Vault
Security · Local stdio
Quality: 56/100 (Good) | Auth: API Key required
Verdict Summary: Choose Vaultshell if you need specialized Security tools running via a local process. Choose 1Claw Vault if your workspace requires Security integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
V
Choose Vaultshell when:
You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: ONECLAW_AGENT_API_KEY, ONECLAW_AGENT_TOKEN, ONECLAW_VAULT_ID, ONECLAW_LOCAL_ONLY, ONECLAW_LOCAL_VAULT, ONECLAW_DAEMON_SOCKET, MCP_TRANSPORT, PORT.
Vaultshell is categorized under Security and uses a local stdio subprocess. In contrast, 1Claw Vault belongs to Security using local stdio subprocess. Select Vaultshell when you need capabilities focused on security and 1Claw Vault when you require tools for security.
Start a credential-injecting reverse proxy on 127.0.0.1
shell_proxy_stop
Stop a proxy
shell_proxy_list
List running proxies
secret_list
List names + metadata (backend ref, resolvable)
secret_set
Write to backend; persisted, never echoed
secret_delete
Delete and unregister
+4 more tools listed on main page
1Claw Vault Tools (37)
list_secrets
List all secrets (metadata only — never values)
get_secret
Fetch the decrypted value of a secret by path. Accepts optional `client_share` for MPC vaults.
put_secret
Create or update a secret (creates a new version). Response includes `client_share` when the vault has MPC enabled.
delete_secret
Soft-delete a secret at a path
describe_secret
Get metadata without fetching the value
rotate_and_store
Store a new value for an existing secret and return the version
rotate_generate
Server-side secret rotation with generated value (length, charset configurable)
list_versions
List all versions of a secret (version numbers, dates, disabled status)
get_env_bundle
Fetch an env_bundle secret and parse it as KEY=VALUE JSON
list_child_agents
Child agents under a parent (own key/memory/policy, subset of the parent's access; vault ≥ 0.61.30)
resolve_env
Resolve environment variables for a vault and environment (returns the final KEY=VALUE set with precedence applied). When the agent has `env_auto_resolve: true`, omit `environment` and the server uses the agent's tagged environment from the JWT.
create_vault
Create a new vault (auto-shared with the agent's human creator)