Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.DinanathDash/envault

NPM · @DINANATHDASH/ENVAULT-MCP-SERVER

Secure secret management with a Human-In-The-Loop (HITL) interceptor for agent mutations.

0 this week 83 Trust /100

Last scanned (23 hours ago)

Scores higher than 73% of npm servers

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security92
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Declares code that runs automatically (postinstall) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
  • 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency87
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to DinanathDash/Envault). View diagnostics → Pass
  • Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
  • Actively maintained (last published 213 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability57
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 1151 tokens (~50/item across 23 items; 23 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage68
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 4% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "envault_deploy" implies "deploy" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • License in Provenance & TransparencyLicence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 16 Nov 26 0
    • Stability: 0.97 → pass security
  • 15 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Nov 26 −2
    • Stability: pass → 0.83 functional
  • 29 Oct 26 0
    • Stability: 0.97 → pass security
  • 28 Oct 26 0
    • Stability: pass → 0.97 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/@dinanathdash/envault-mcp-server@1.12.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo DinanathDash/Envault
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/DinanathDash/Envault/.github/workflows/publish-mcp.yml@refs/heads/main
Rekor log index 1354134152
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:dd42955750a956d3b8ca116625d51907f9c576976c0e0f0b3b93d968f654596d3b64e56202566bdf12e61ce8a3782363faa0b15a02d87e2a6f8d86e00

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
postinstall Not reviewed node postinstall.mjs

Background: Why install scripts are a supply-chain risk →

Dependencies 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 23 exposed · ~1,151 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
envault_approve ~50

Approve a pending HITL request by approval ID. Use after envault_push/envault_deploy returns a pending approval. This executes the human approval action.

NameTypeReqDescription
approvalIdstringyes–

No output schema declared.

No examples provided.

envault_audit ~67

Audit local env safety and key parity. Can install pre-commit hook and emit text or JSON output.

NameTypeReqDescription
filestring––
formatstring––
installHookboolean––
strictboolean––
templatestring––

No output schema declared.

No examples provided.

envault_context ~52

Alias of envault_status for explicit context retrieval. Returns auth, project, role, permissions, active environment, and local env mapping.

NameTypeReqDescription
projectIdstring–Optional project ID override for context/status call.

No output schema declared.

No examples provided.

envault_deploy ~80

Alias of envault_push. Same HITL behavior applies: if pending approval is returned, provide approval_url to the user and wait for approval completion before claiming success.

NameTypeReqDescription
dryRunboolean––
environmentstring––
filestring––
forceboolean––
projectIdstring––

No output schema declared.

No examples provided.

envault_diff ~52

Compare local env file against remote secrets and return additions, deletions, and modifications before proposing a push.

NameTypeReqDescription
environmentstring––
filestring––
projectIdstring––

No output schema declared.

No examples provided.

envault_doctor ~25

Run local diagnostics for CLI installation, Homebrew source, and version parity.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

envault_env_default ~26

Set the default environment in envault.json.

NameTypeReqDescription
environmentstringyes–

No output schema declared.

No examples provided.

envault_env_map ~39

Map an environment slug to a local env file path in envault.json.

NameTypeReqDescription
environmentstringyes–
filestringyes–

No output schema declared.

No examples provided.

envault_env_unmap ~29

Remove an environment-to-file mapping from envault.json.

NameTypeReqDescription
environmentstringyes–

No output schema declared.

No examples provided.

envault_generate_hooks ~26

Create or update git post-merge hook that triggers envault pull after merges.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

envault_init ~28

Initialize envault.json and project linkage in the current directory. Use for first-time project setup.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

envault_login ~32

Start CLI device-flow login in the browser and store local CLI access token. Use when auth is missing or expired.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

envault_mcp_install ~38

Install MCP integration config for local workspace and/or global editor clients.

NameTypeReqDescription
globalboolean––
localboolean––

No output schema declared.

No examples provided.

envault_mcp_update ~46

Update MCP package/config for local workspace and/or global editor clients.

NameTypeReqDescription
configOnlyboolean––
globalboolean––
localboolean––

No output schema declared.

No examples provided.

envault_pull ~72

Fetch remote secrets into a local env file. Use before local development runs, diffs, or edits. This updates local files only and does not require HITL approval.

NameTypeReqDescription
environmentstring––
filestring––
forceboolean––
projectIdstring––

No output schema declared.

No examples provided.

envault_push ~127

Submit local secret changes for HITL approval. IMPORTANT: treat this as an approval-request step, not immediate execution. If the response indicates pending approval (for example HTTP 202 Accepted with approval_id/approval_url), you must explicitly show the approval_url to the user, instruct them to open it in a browser and approve/reject, then wait for user confirmation or poll status before assuming changes are applied.

NameTypeReqDescription
dryRunboolean––
environmentstring––
filestring––
forceboolean––
projectIdstring––

No output schema declared.

No examples provided.

envault_remove_local_key ~69

Remove a key from local env file. If autoPush=true, this triggers envault_push and may return pending HITL approval requiring browser approval.

NameTypeReqDescription
autoPushboolean––
environmentstring––
filestring––
keystringyes–

No output schema declared.

No examples provided.

envault_run ~65

Run a local command with Envault secrets injected into process environment. Use when the user asks to run an app/script with managed secrets.

NameTypeReqDescription
argsarray––
commandstringyes–
environmentstring––
projectIdstring––

No output schema declared.

No examples provided.

envault_sdk_install ~40

Install Envault TypeScript SDK either in current project, globally, or both.

NameTypeReqDescription
globalboolean––
localboolean––

No output schema declared.

No examples provided.

envault_sdk_update ~40

Update Envault TypeScript SDK either in current project, globally, or both.

NameTypeReqDescription
globalboolean––
localboolean––

No output schema declared.

No examples provided.

envault_set_local_key ~78

Set/update a key=value in local env file. If autoPush=true, this triggers envault_push and may return pending HITL approval requiring browser approval.

NameTypeReqDescription
autoPushboolean––
environmentstring––
filestring––
keystringyes–
valuestringyes–

No output schema declared.

No examples provided.

envault_status ~54

Read-only context check for auth, project, role, permissions, active environment, and mapped local env file. Use this first when context is unclear.

NameTypeReqDescription
projectIdstring–Optional project ID override for status call.

No output schema declared.

No examples provided.

envault_version ~16

Print installed Envault CLI version.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the io.github.DinanathDash/envault MCP server?

io.github.DinanathDash/envault runs locally as an npm package, launched with npx -y @dinanathdash/envault-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @dinanathdash/envault-mcp-server

# add to Claude Code
claude mcp add dinanathdash-envault -- npx -y @dinanathdash/envault-mcp-server
Common questions

What is the io.github.DinanathDash/envault MCP server?

io.github.DinanathDash/envault is an MCP server listed in the public MCP registry as io.github.DinanathDash/envault. Secure secret management with a Human-In-The-Loop (HITL) interceptor for agent mutations. This page covers its npm package (@dinanathdash/envault-mcp-server).

Is the io.github.DinanathDash/envault MCP server safe to use?

io.github.DinanathDash/envault scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.DinanathDash/envault MCP server expose?

io.github.DinanathDash/envault exposes 23 tools: envault_status, envault_context, envault_pull, envault_push, envault_deploy, and 18 more. Their descriptions and schemas cost roughly 1,151 tokens of context every time the server is loaded.

Is the io.github.DinanathDash/envault MCP server still maintained?

io.github.DinanathDash/envault is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.DinanathDash/envault MCP server?

VerifyMCP ran 15 checks on io.github.DinanathDash/envault, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.DinanathDash/envault: License. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.