kdbx runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 14 Oct 2026.
Read-only access to secrets in a local KeePassXC vault. Runs commands with them injected.
Nothing serious here today
Today is the operative word: we check kdbx every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Alternatives to kdbx
same job, measured the same wayLet AI agents use secrets without seeing them: inject into a command, redact the output.
Send and read one-time encrypted secrets with local encryption.
Agent-safe secrets from self-hosted Vaultwarden/Bitwarden: injected into commands, masked in output
Local read-only OpenAPI and Swagger inspection with secret-safe schema summaries. Tools include...
Secrets vault for Claude Code with audit logs, access rules, and AES-256 encryption.
Read-only MCP access to The Agent Commons: shared security findings for AI agents and their tools.
Injects secrets into shell commands at exec time; plaintext never reaches the LLM context
Use API keys from your Keyfold vault in commands and .env files. No tool returns a secret value.
kdbx — questions
Answers built from our own checks of this server.