encrypted-vault-mcp
Related Servers
Alternatives to encrypted-vault-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceLocal AES-256-GCM encrypted vault for AI agents. Resolve {{PLACEHOLDER}} secrets in prompts at runtime — LLMs never see real API keys. Argon2id key derivation, zero cloud.257 npm6MIT
- AlicenseNot gradedqualityCmaintenanceLocal, encrypted password vault with AES-256-GCM and PBKDF2, exposing MCP tools for secure credential management, password generation, and search.MIT
- FlicenseNot gradedqualityDmaintenanceLocal encrypted vault for API keys. LLMs never see your real keys — the server injects them transparently into HTTP requests.-
- FlicenseNot gradedqualityDmaintenanceAES-256-GCM encrypted local secret storage exposed as MCP tools, with secrets captured via native OS dialogs and never passing through the LLM API.-
- AlicenseCqualityCmaintenanceEnables AI agents to securely store and manage encrypted secrets locally while using them indirectly through environment-variable injection or file writes, so plaintext values never enter the agent's context.8MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to fetch API keys and tokens on demand from an encrypted local vault instead of pasting them into chats, and to scan project folders for plaintext secrets. It also manages credential entries with templates, rotation tracking, usage logs, backups, and .env export.MIT
TDQS
Scored across 9 tools
Each tool addresses a unique action: init, unlock/lock for session management, store/fetch/remove for CRUD, list for key enumeration, status for vault info, and change_pin for rotation. No two tools overlap in purpose.
All tool names use consistent lowercase snake_case with a verb_noun pattern (e.g., change_pin, list, store). No mixing of conventions or vague verbs like 'process' or 'do'.
9 tools is ideal for an encrypted vault: covering initialization, authentication, CRUD, listing, status, and PIN rotation. No unnecessary tools and no critical gaps.
The tool surface covers the complete vault lifecycle: init (create), unlock/lock (session), store/fetch/remove (data management), list (inventory), status (health), and change_pin (maintenance). Missing a 'delete vault' tool but that's a rare operation.