mcpbeat Sign in
I

vaultguard MCP Server

by ashishrao-4 Your server? Claim it
local only

vaultguard runs on your own machine — the client starts it, so there is no endpoint to ping. 138 installs a week from npm.

AI agents use your Obsidian secrets by name — values never reach their context.

Installs per day peak 138 · avg 4
a month agotoday
138
Installs / week
npm · @ashishrao-4/vaultguard
Stars
on GitHub
Last commit
0 releases in 90 days
License
language unknown

Nothing serious here today

Today is the operative word: we check vaultguard every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

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.

run in your terminal
claude mcp add vaultguard -- npx -y @ashishrao-4/vaultguard
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "vaultguard": {
      "args": [
        "-y",
        "@ashishrao-4/vaultguard"
      ],
      "command": "npx"
    }
  }
}
~/.codex/config.toml
[mcp_servers.vaultguard]
command = "npx"
args = ["-y", "@ashishrao-4/vaultguard"]
.cursor/mcp.json
{
  "mcpServers": {
    "vaultguard": {
      "args": [
        "-y",
        "@ashishrao-4/vaultguard"
      ],
      "command": "npx"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "vaultguard": {
      "args": [
        "-y",
        "@ashishrao-4/vaultguard"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: VAULTGUARD_PASSPHRASE (Passphrase that decrypts the encrypted secret blocks in your Obsidian vault.), VAULTGUARD_VAULT_PATH (Path to your Obsidian vault (overrides the one in ~/.vaultguard/config.json).), VAULTGUARD_HOME (Config directory (defaults to ~/.vaultguard).), VAULTGUARD_ALLOW_GET_SECRET (Set to 1 to enable get_secret (default: disabled so values never reach the agent).). The author declared them in the registry entry; get the values from the project itself.

Alternatives to vaultguard

same job, measured the same way
keyward
by arturayupov

Local encrypted secret broker for AI agents: request keys by name, approve each use over MCP.

local only
MCP Secret Scrub
by sudo-ai-git

Deterministic no-LLM MCP server that scrubs secrets before they reach an agent. Never leaks values.

91 installs/wk local only
hush
by royashbrook

A secret store for AI agents: the agent never sees the plaintext.

1 tools answering
Wundervault MCP
by wundervault

Zero-knowledge MCP secrets vault for AI agents: secrets injected at runtime, never seen by the model

339 installs/wk local only
Demipass
by dustforge

Credential custody for agents: use secrets blind (ssh/http/smtp/git/db), never in context.

74 installs/wk local only
Keyblind
by aarifmms

Encrypted secrets vault for AI agents — secrets resolved at runtime, never seen by LLMs.

54 installs/wk local only
Enigmagent MCP
by agnuxo1

Local AES-256-GCM vault for AI agents. Secrets stay local, LLMs never see real API keys.

60 installs/wk local only
Leakferret
by leakferrethq

Context-aware secret scanner: lets an AI agent scan, verify, and rewrite secrets before committing.

60 installs/wk local only

vaultguard — questions

Answers built from our own checks of this server.

Why is there no uptime for vaultguard?
vaultguard runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @ashishrao-4/vaultguard was installed 138 times last week.
How do I connect vaultguard?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It runs locally, so the command pulls @ashishrao-4/vaultguard straight from npm; nothing to host, nothing to sign up for.
How many people use vaultguard?
The npm package @ashishrao-4/vaultguard was installed 138 times in the last week. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.