Keyblind vs Wundervault MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Keyblind vs Wundervault MCP
In-depth architectural comparison of the Keyblind and Wundervault MCP 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
Keyblind
Other Tools and Integrations · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Wundervault MCP
Other Tools and Integrations · Local stdio
Quality: 63/100 (Good) | Auth: API Key required
Verdict Summary: Choose Keyblind if you need specialized Other Tools and Integrations tools running via a local process. Choose Wundervault MCP if your workspace requires Other Tools and Integrations integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Keyblind when:
You need dedicated capabilities in the Other Tools and Integrations domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Encrypted secrets vault with MCP for AI agents. Secrets resolved at runtime, never leaked to LLM conversations.
Zero-knowledge secret vault for AI agents: use API keys, passwords, and SSH keys to run real commands (exec/rsync) with the secret injected into a single command — never returned to the model or shown in chat. Client-side AES-256-GCM, per-agent scoping, append-only audit log.
Category & Scope
Tools & Capabilities Breakdown
Keyblind Tools (16)
resolve_secret
Resolve a secret at runtime (value hidden from transcript)
store_secret
Encrypt and store a secret
list_secrets
List secret names (values never revealed)
delete_secret
Delete a secret
sandbox_env
Replace `.env` values with deterministic fakes
unsandbox_env
Restore real `.env` values from vault
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Keyblind is categorized under Other Tools and Integrations and uses a local stdio subprocess. In contrast, Wundervault MCP belongs to Other Tools and Integrations using local stdio subprocess. Select Keyblind when you need capabilities focused on other tools and integrations and Wundervault MCP when you require tools for other tools and integrations.
Create encrypted, expiring share link for a secret
+4 more tools listed on main page
Wundervault MCP Tools (6)
vault_entries_list
List all vault entries available to this agent. Returns entry IDs and secret names — no values.
vault_entry_get
Retrieve and decrypt a vault secret. Optionally execute a command with it.
vault_exec
Execute a shell command with a vault secret injected as an env var — locally or on a remote host over SSH. The secret is injected into the subprocess and the buffer is zeroed immediately after spawn; escape patterns are rejected before decryption.
vault_entry_inject_env
Write a vault secret directly into a config file (`~/.npmrc`, `~/.netrc`, `~/.docker/config.json`, or a project `.env`) without the plaintext passing through the agent.
vault_rsync
Sync a local directory to a remote host using rsync over SSH, with the SSH key fetched from the vault (temp keyfile deleted immediately after transfer).