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

io.github.DinanathDash/envault

NPM · @DINANATHDASH/ENVAULT-MCP-SERVER · SCANNED AUG 3

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

+25 this week 67 Trust /100
Trust breakdown (6 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 →

Supply Chain Security80
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
  • Runs a script at install time (postinstall) that we could not recognise. It may be perfectly ordinary, but we do not read the published tarball, so we cannot say what it does. View diagnostics → Partial
  • Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency84
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to DinanathDash/Envault). View diagnostics → Pass
  • License check failed: the license (SEE LICENSE IN LICENSE) isn't a recognized OSI-approved license. See how to fix → Fail
  • Actively maintained (last published 103 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @dinanathdash/envault-mcp-server

# add to Claude Code
claude mcp add dinanathdash-envault -- npx -y @dinanathdash/envault-mcp-server
# add to Codex CLI
codex mcp add dinanathdash-envault -- npx -y @dinanathdash/envault-mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dinanathdash-envault": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@dinanathdash/envault-mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dinanathdash-envault --command npx --arg -y --arg @dinanathdash/envault-mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  dinanathdash-envault:
    command: "npx"
    args: ["-y", "@dinanathdash/envault-mcp-server"]
// mcp.json
{
  "mcpServers": {
    "dinanathdash-envault": {
      "command": "npx",
      "args": [
        "-y",
        "@dinanathdash/envault-mcp-server"
      ]
    }
  }
}
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.

  • 2 Aug 26 +49
    • Provenance: unverified → pass security
    • Install scripts: unverified → partial security
    • Known CVEs: unverified → partial security
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • The scripts that run when this package is installed changed: postinstall security
    • The attested source repository moved: DinanathDash/Envault security
    • License: unverified → fail functional
    • Tool coverage: 100 → unverified functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Schema quality: unverified → good functional
    • Dependency health: unverified → partial functional
    • First check of Schema quality: unverified functional
    • Licence: SEE LICENSE IN LICENSE functional
  • 31 Jul 26 −24
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 42

    First indexed and scored.

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 3 Aug 2026 · Analysed npm/@dinanathdash/[email protected]

Provenance verified

Ecosystem: npm · Outcome: verified

Reason: verified

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:
https://slsa.dev/provenance/v1
Subject digest:
sha512:dd42955750a956d3b8ca116625d51907f9c576976c0e0f0b3b93d968f654596d3b64e56202566bdf12e61ce8a3782363faa0b15a02d87e2a6f8d86e00
Discovery method:
attestation_endpoint
Install scripts 1 script
Hook Tier Command
postinstall unreviewed node postinstall.mjs
Dependencies 94 packages

94 packages in the resolved dependency tree · 94 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

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.

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
projectIdstringOptional 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
projectIdstringOptional 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.