encrypted-vault-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@encrypted-vault-mcpstore my-openai-key as sk-abc123def456"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
encrypted-vault-mcp
MCP server providing a local-first encrypted key-value vault. Store API keys, secrets, notes, or any string data under a PIN. AES-GCM 256-bit cipher, PBKDF2 (600k iterations, SHA-256) derived key. Zero cloud. Zero telemetry. Zero network.
Why
Storing secrets in plain text in chat history is bad. Pasting API keys into prompts is worse. This MCP gives the agent a vault: it can store a value once under a name, then later fetch it by name without you re-typing the secret.
AI agent can hold long-lived secrets safely between chats
You unlock once per session with a PIN
All data stays on the machine as encrypted bytes
Wrong PIN = wrong key = nothing decrypts (AES-GCM auth tag fails)
Related MCP server: mcp-keyward
Install
npm install -g encrypted-vault-mcpOr npx:
npx encrypted-vault-mcpUse with Claude Desktop
Add to claude_desktop_config.json (Windows: %APPDATA%\Claude\claude_desktop_config.json):
{
"mcpServers": {
"vault": {
"command": "npx",
"args": ["-y", "encrypted-vault-mcp"]
}
}
}Restart Claude Desktop. First time:
"Use vault to init with pin 1234"
Then any time:
"Unlock vault with pin 1234, then store my-openai-key as sk-..."
"Fetch my-openai-key"
"List vault keys"
Tools
Tool | Args | Description |
|
| Create a new vault file with this PIN. Fails if one already exists. |
|
| Derive key from PIN. Required before store/fetch/list/remove. |
| — | Clear key from memory. |
|
| Encrypt + save under name. |
|
| Decrypt + return value. |
| — | List all key names. Values stay encrypted on disk. |
|
| Delete an item. |
|
| Rotate PIN. Re-encrypts everything with new key. |
| — | Show whether vault exists / is unlocked / path / item count. |
Crypto
Cipher: AES-256-GCM (authenticated encryption — wrong PIN = decryption fails cleanly)
Key derivation: PBKDF2-HMAC-SHA256, 600,000 iterations (OWASP 2023), 16-byte salt
IV: 96-bit random per encryption (NIST SP 800-38D)
PIN verification: separate PBKDF2 hash with its own salt; the PIN itself is never persisted
File permissions: vault file is written with mode
0o600(owner read/write only)
Storage location
Default: ~/.encrypted-vault-mcp/vault.json
Override:
{
"mcpServers": {
"vault": {
"command": "npx",
"args": ["-y", "encrypted-vault-mcp"],
"env": { "VAULT_PATH": "/secure/drive/my-vault.json" }
}
}
}Threat model
Threat | Protected? |
Disk read by attacker without PIN | ✅ items unrecoverable without PIN |
Wrong PIN | ✅ AES-GCM auth fails, no data leaked |
PIN brute-force | ⚠️ 600k PBKDF2 iterations slow it; use a real password for high-value secrets |
Process memory dump while unlocked | ❌ key sits in memory between unlock and lock — lock when done |
Malicious MCP client | ❌ if the agent itself is hostile, it can call fetch on whatever it wants — only run trusted agents |
Local development
git clone https://github.com/KhushalB25/encrypted-vault-mcp.git
cd encrypted-vault-mcp
npm install
npm run build
npm startInspect:
npx @modelcontextprotocol/inspector node dist/index.jsAuthor
License
MIT
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/KhushalB25/encrypted-vault-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server