Enigmagent MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 60 installs a week from npm. Last commit 26 Apr 2026.
Local AES-256-GCM vault for AI agents. Secrets stay local, LLMs never see real API keys.
Today is the operative word: we check Enigmagent MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
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 enigmagent-mcp -- npx -y enigmagent-mcp
{
"mcpServers": {
"enigmagent-mcp": {
"args": [
"-y",
"enigmagent-mcp"
],
"command": "npx"
}
}
}
[mcp_servers.enigmagent-mcp]
command = "npx"
args = ["-y", "enigmagent-mcp"]
{
"mcpServers": {
"enigmagent-mcp": {
"args": [
"-y",
"enigmagent-mcp"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"enigmagent-mcp": {
"args": [
"-y",
"enigmagent-mcp"
],
"command": "npx"
}
}
}
This one needs environment variables set before it will start:
VAULT_PASSWORD (Master password used to decrypt the local EnigmAgent vault (AES-256-GCM + Argon2id).), VAULT_PATH (Path to the vault.json file (default: ./vault.json).).
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.
Secure secrets proxy for AI agents — manages API keys so agents never see raw credentials.
Stop AI coding agents from leaking API keys. Local proxy swaps real secrets for phm_ tokens.
Encrypted secrets for Next.js. AES-256-GCM with no vault needed.
Post-quantum secrets manager for AI agents. ML-KEM-768 + X25519 + AES-256-GCM.
Zero-knowledge MCP secrets vault for AI agents: secrets injected at runtime, never seen by the model
Local encrypted secret broker for AI agents: request keys by name, approve each use over MCP.
A secret store for AI agents: the agent never sees the plaintext.
Answers built from our own checks of this server.