vaultguard
io.github.ashishrao-4/vaultguard
AI agents use your Obsidian secrets by name — values never reach their context.
Description as published in the official MCP registry.
What we measured
| Endpoint | None listed (runs locally) | registry |
|---|---|---|
| GitHub stars | 0 | github.com/ashishrao-4/vaultguard |
| Last push | 2026-09-18 | GitHub API |
| Licence | MIT | GitHub API |
| Registry version | 0.1.2 · active · updated 2026-09-18 | registry |
| Package | npm: @ashishrao-4/vaultguard | registry |
Signed reports
No signed reports yet. A report carries a signed decision record from the reporter's gate, so it shows a real call went through, not just an opinion. How to file one.
Connect
npx -y @ashishrao-4/vaultguardCommands are built from the registry entry. Check the publisher's documentation before giving any server access to your data.
Related servers
- vaultguard-mcp VaultGuard MCP Server - Yearn V3 / DeFi vault security and analysis tools for AI coding…
Badge for your README
Shows the result of our latest check and links back to this page.
[](https://openforallofus.com/tools/io.github.ashishrao-4/vaultguard)Agents can read this page as data: MCP endpoint https://openforallofus.com/api/mcp, tool get_tool with name io.github.ashishrao-4/vaultguard.