io.github.DinanathDash/envault

MCPattested
v1.12.0io.github.DinanathDashUnknownUpdated 5mo agonpmGitHub

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

This MCP server exposes Envault read + mutation tooling for MCP clients (Claude Desktop, VS Code, etc). The MCP registry is a static phonebook. There is no onboarding UX and no safety net. If you skip this step, the server will start but every tool call will fail with . 1. Sign in to Envault. 2. Open Account Settings → Security. 3. Create a new MCP Token. 4. Copy the full unmasked token value…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
4GitHub stars
2Forks
5mo agoLast update
Package
Authorio.github.DinanathDash
LicenseUnknown
Version1.12.0
Sourcemcp-registry
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 80e0dfc
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface23 tools · 1 privileged
Security scan✓ Cleanv1.12.0 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

23 tools · 1 privileged
Statically extracted from the published packagev1.12.0 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

envault_statusNo description published

This tool published no description. Forge does not invent one.

envault_contextNo description published

This tool published no description. Forge does not invent one.

envault_pullNo description published

This tool published no description. Forge does not invent one.

envault_pushNo description published

This tool published no description. Forge does not invent one.

envault_deployNo description published

This tool published no description. Forge does not invent one.

envault_approveNo description published

This tool published no description. Forge does not invent one.

envault_diffNo description published

This tool published no description. Forge does not invent one.

envault_runNo description published

This tool published no description. Forge does not invent one.

envault_loginNo description published

This tool published no description. Forge does not invent one.

envault_initNo description published

This tool published no description. Forge does not invent one.

envault_generate_hooksNo description published

This tool published no description. Forge does not invent one.

envault_auditNo description published

This tool published no description. Forge does not invent one.

envault_env_mapNo description published

This tool published no description. Forge does not invent one.

envault_env_unmapNo description published

This tool published no description. Forge does not invent one.

envault_env_defaultNo description published

This tool published no description. Forge does not invent one.

envault_mcp_installNo description published

This tool published no description. Forge does not invent one.

envault_mcp_updateNo description published

This tool published no description. Forge does not invent one.

envault_sdk_installNo description published

This tool published no description. Forge does not invent one.

envault_sdk_updateNo description published

This tool published no description. Forge does not invent one.

envault_doctorNo description published

This tool published no description. Forge does not invent one.

envault_versionNo description published

This tool published no description. Forge does not invent one.

envault_set_local_keyNo description published

This tool published no description. Forge does not invent one.

envault_remove_local_keyprivilegedNo description published

This tool published no description. Forge does not invent one.

0 of 23 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

This MCP server exposes Envault read + mutation tooling for MCP clients (Claude Desktop, VS Code, etc). The MCP registry is a static phonebook. There is no onboarding UX and no safety net. If you skip this step, the server will start but every tool call will fail with . 1. Sign in to Envault. 2. Open Account Settings → Security. 3. Create a new MCP Token. 4. Copy the full unmasked token value (you won’t be able to see it again). 5. Use it as in your MCP client config (examples below). Cloud is…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.