envault
io.github.DinanathDash/envault
About envault
envault is an MCP server published by the GitHub account DinanathDash. Secure secret management with a Human-In-The-Loop (HITL) interceptor for agent mutations.
It runs on your own machine: your AI client starts it from the npm package @dinanathdash/envault-mcp-server at version 1.12.0.
It asks for one secret: ENVAULT_TOKEN. Give it a key with the least access that still works.
It also needs ENVAULT_BASE_URL set before it starts.
Version 1.12.0 was published on 21 April 2026, and the source code is public, so you can read it before installing.
Written from the registry entry. 9 automated checks on the registry entry and the package code: 6 pass, 1 warn, 0 fail, 2 info. How we check.
What it asks for
| Variable | Required | Secret | Description |
|---|---|---|---|
ENVAULT_TOKEN | Yes | Yes | Required: Generate via Envault Account Settings -> Security -> MCP Token |
ENVAULT_BASE_URL | Yes | No | Required: https://www.envault.tech |
Checks
| Check | Result | Detail |
|---|---|---|
| Source repository linked | Pass | https://github.com/DinanathDash/Envault |
| Version pinned | Pass | Every package has an explicit version |
| Secrets requested | Info | Asks for 1 secret: ENVAULT_TOKEN |
| Known package registry | Pass | All packages come from npm, PyPI, OCI, NuGet or MCPB |
| Namespace ownership | Info | Name verified via GitHub account DinanathDash |
| Registry text aimed at the AI | Pass | Description and settings contain no hidden characters or instructions to the AI |
| Install scripts | Warn | Runs at install: postinstall: node postinstall.mjs |
| Code red flags | Pass | Read 4 files in @dinanathdash/envault-mcp-server@1.12.0: no obfuscation, encoded execution, credential reads or data-collection endpoints found |
| Text aimed at the AI | Pass | No hidden characters or instructions to the AI in 4 files, including comments and the README |
Popularity & health: 56 / 100
Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.
2 forks, 119 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.
What people say
No Hacker News threads link to its source code.
Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.
Facts
| Registry name | io.github.DinanathDash/envault |
|---|---|
| Publisher | GitHub account DinanathDash |
| How the name is verified | Name verified via GitHub account DinanathDash. The registry ties the name prefix to that account or domain; it does not check the code. |
| Type | Local: runs on your machine from a package |
| Packages | npm @dinanathdash/envault-mcp-server 1.12.0 (stdio) |
| Version | 1.12.0 |
| Published | |
| Last updated | |
| Source repository | https://github.com/DinanathDash/Envault |
| Website | None linked |
| Category | Agent safety & governance (assigned by keyword rule, not by hand) |
Related servers in Agent safety & governance
- IdentArk Gateway3/3Zero-secret MCP gateway for AI agents: risk-scored, audited calls…
- Plures7/7Human in the loop for AI agents: ask ID verified people to check a…
- AgentGate7/7Human-in-the-loop approval gateway for AI agents over MCP: request,…
- aiglare7/7Audit AI/LLM features for governance guardrails: confidence,…
- mcp-debezium7/7Debezium / Kafka Connect CDC connector management for AI agents —…
- chp-mcp7/7Spend approval gate for AI agents: budget caps, HITL thresholds,…