Other · Local MCP server
vaultguard
AI agents use your Obsidian secrets by name - values never reach their context.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.ashishrao-4/vaultguard- Version
- 0.1.2
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-09-18
- Updated
- 2026-09-18
- Publisher
- ashishrao-4 (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/ashishrao-4) · how
- Listed under
- Obsidian MCP servers
- Website
- github.com/ashishrao-4/vaultguard
- Repository
- github.com/ashishrao-4/vaultguard
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | @ashishrao-4/vaultguard | 0.1.2 | stdio |
How to connect vaultguard
vaultguard runs locally from a Node.js package published to the npm registry: @ashishrao-4/vaultguard version 0.1.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @ashishrao-4/vaultguard@0.1.2. It reads these environment variables: VAULTGUARD_PASSPHRASE (required, secret), VAULTGUARD_VAULT_PATH, VAULTGUARD_HOME and VAULTGUARD_ALLOW_GET_SECRET; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"vaultguard": {
"command": "npx",
"args": [
"-y",
"@ashishrao-4/vaultguard@0.1.2"
],
"env": {
"VAULTGUARD_PASSPHRASE": "<secret>",
"VAULTGUARD_VAULT_PATH": "<value>",
"VAULTGUARD_HOME": "<value>",
"VAULTGUARD_ALLOW_GET_SECRET": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Vault Health MCPObsidian vault structural health: broken links, orphans, missing frontmatter, safe auto-repair. | Local · stdio |
| Vault MCPMCP server for credential isolation - bots use passwords and API keys without seeing them. | Local · stdio |
| VaultCrux PlatformVaultCrux Platform - 60 tools: retrieval, proof, intel, economy, watch, org. | Remote · HTTPLive check: sign-in required |
| vaultgateSelf-hosted remote MCP server for Bitwarden and Vaultwarden with OAuth 2.1; agents hold tokens only. | Remote · HTTP |
| Vcp MCPValue Context Protocol tools: VCP/I tokens, CSM1 codes, VCP-Lite, and context encoding. | Local · stdio |
| VDatum MCP ServerMCP server for vertical datum conversions using coastalmodeling-vdatum. | Local · stdio |
| VdbCheck packages for CVEs, slopsquatting, and CISA KEV before your AI agent installs them. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Vectelos DutyUS import duty from the live HTS: Section 301/232 stacking, MPF, HMF. Refuses what it cannot price. | Remote · HTTPLive check: sign-in required |