mcp server
Vault MCP
MCP server for credential isolation — bots use passwords and API keys without seeing them
Description as published by the maintainer. Source
- version 0.2.1
- slowing
slowing — Most recent push to the repository was 2026-02-28.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 1 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-02-28 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 7 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 0.2.1 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-03-01 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | MIT | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-03-01 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub |
Where to get it
Related, by what their authors tagged them
-
io.github.Agnuxo1/enigmagent-mcp
— last commit 2026-04-26, shares credentials, encryption, security
Local AES-256-GCM vault for AI agents. Secrets stay local, LLMs never see real API keys.
-
keyward
— last commit 2026-07-19, shares credentials, security, vault
Local encrypted secret broker for AI agents: request keys by name, approve each use over MCP.
-
io.github.bch1212/agentvault
— last commit 2026-06-06, shares credentials, vault
Credential vault for AI agents — Fernet-encrypted keys, per-agent budgets, audit logs.
-
io.github.bitatlas-group/bitatlas
— last commit 2026-08-06, shares encryption, vault
Zero-knowledge encrypted storage for humans and AI agents. Client-side AES-256-GCM, EU-hosted.
-
hush
— last commit 2026-08-04, shares credentials, security
A secret store for AI agents: the agent never sees the plaintext.
-
io.github.AInoAKARI/keymaster-mcp
— last commit 2026-08-03, shares security, vault
Read-only runtime secret retrieval from HashiCorp Vault via Keymaster for autonomous AI agents.
-
Phantom Secrets
— last commit 2026-07-22, shares encryption, security
Stop AI coding agents from leaking API keys. Local proxy swaps real secrets for phm_ tokens.
-
io.github.bitterdev/veracrypt-mcp
— last commit 2026-07-27, shares encryption, security
MCP server to mount and unmount VeraCrypt containers with secure stdin password handling.
-
Citadel
— last commit 2026-08-06, shares encryption
Encrypted-first embedded database with vector search and agent memory, exposed as MCP tools
-
FastMCP server for bidirectional sync between personal and team Obsidian vaults
— last commit 2026-08-06, shares vault
FastMCP server for bidirectional sync between personal and team Obsidian vaults.
These share tags the maintainers applied themselves, such as credentials, encryption, security, vault. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: ai-agent, claude, credentials, encryption, llm, mcp, mcp-server, model-context-protocol, security, vault.
Bring your own setup
We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.
Join ZBS AI Practice Lab