io.github.DinanathDash/envault

MCPattested
v1.12.0io.github.DinanathDashUnknownUpdated 3mo 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…

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.
3mo agoLast update
Package
Authorio.github.DinanathDash
LicenseUnknown
Version1.12.0
Sourcemcp-registry
npm@dinanathdash/envault-mcp-server
GitHubDinanathDash/Envault
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 · 2mo ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

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