Wundervault MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 339 installs a week from npm. Last commit 14 Sep 2026.
Zero-knowledge MCP secrets vault for AI agents: secrets injected at runtime, never seen by the model
We read the source, 10 min ago · rules 3dff92dd89df
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
postinstall: chmod +x dist/agent.js dist/index.js 2>/dev/null || true
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
subprocess.check_call([sys.executable, "-m", "pip", "install", "cryptography", "--quiet"])
const result = spawnSync(command, {
ssh_key: { type: 'string', description: 'Path to SSH private key on disk (e.g. ~/.ssh/id_ed25519). Prefer ssh_key_entry_id.' },
Object.entries(process.env)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Wundervault MCP and you get told the day something new turns up.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add wundervault-mcp -- npx -y @wundervault/mcp-server
{
"mcpServers": {
"wundervault-mcp": {
"args": [
"-y",
"@wundervault/mcp-server"
],
"command": "npx"
}
}
}
[mcp_servers.wundervault-mcp]
command = "npx"
args = ["-y", "@wundervault/mcp-server"]
{
"mcpServers": {
"wundervault-mcp": {
"args": [
"-y",
"@wundervault/mcp-server"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"wundervault-mcp": {
"args": [
"-y",
"@wundervault/mcp-server"
],
"command": "npx"
}
}
}
This one needs environment variables set before it will start:
WUNDERVAULT_AGENT_NAME (Agent name registered with the local wundervault-agent daemon (run onboard.py to register).), WUNDERVAULT_AGENT_TOKEN (Optional daemon auth token. Defaults to ~/.wundervault/agents/<agentName>.token.).
The author declared them in the registry entry; get the values from the project itself.
Encrypted secrets vault for AI agents — secrets resolved at runtime, never seen by LLMs.
Credential isolation for AI agents. Inject secrets at the network boundary.
Zero-knowledge secrets manager — local crypto-plane MCP server: decrypts and injects secrets.
Local AES-256-GCM vault for AI agents. Secrets stay local, LLMs never see real API keys.
A secret store for AI agents: the agent never sees the plaintext.
HSM-backed vault secrets for AI agents (JIT fetch) plus prompt-injection and threat scanning.
Zero-install security baseline for AI coding agents — OWASP/CWE-cited rules over MCP.
Veridion Nexus MCP server - GDPR Art. 44-49 runtime compliance for AI agents
Answers built from our own checks of this server.