Back to MCP Trust Indexm8ven
D
Caution
44/100
2 months ago

DinanathDash/Envault

MCP server for Envault CLI operations

→ DinanathDash/Envault· npm: @dinanathdash/envault-mcp-server· listed on npm

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

DinanathDash

Source: npm

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

npm

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: SUPABASE_SERVICE_ROLE_KEY. We can’t prove the destination matches the brand the credential belongs to.
⚠️
Known vulnerabilities in dependencies: 8 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 8 credentials: BREVO_API_KEY, CRON_SECRET, ENCRYPTION_KEY, ENVAULT_AGENT_SECRET, ENVAULT_GITHUB_WEBHOOK_SECRET, ENVAULT_SESSION_KEY_SECRET, ENVAULT_TOKEN, GOOGLE_GENERATIVE_AI_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies8 high4 medium8 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

highnext@16.1.6GHSA-267c-6grr-h53f

Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes

highnext@16.1.6GHSA-26hh-7cqf-hhc6

Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes - Incomplete Fix Follow-Up

highnext@16.1.6GHSA-36qx-fr4f-26g5

Next.js has a Middleware / Proxy bypass in Pages Router applications using i18n

highnext@16.1.6GHSA-492v-c6pp-mqqv

Next.js has a Middleware / Proxy bypass through dynamic route parameter injection

highnext@16.1.6GHSA-8h8q-6873-q5fj

Next.js Vulnerable to Denial of Service with Server Components

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretBREVO_API_KEY
🔐 secretCRON_SECRET
configEMAIL_DOMAIN
🔐 secretENCRYPTION_KEYyour-64-char-hex-key
configENVAULT_AGENT_ID
configENVAULT_AGENT_MODEL
🔐 secretENVAULT_AGENT_SECRET
configENVAULT_BASE_URLFor one-command envault run local app startup, prefer hosted API fetch-first behavior by not setting ENVAULT_CLI_URL/.
configENVAULT_GITHUB_APP_CLIENT_ID
🔐 secretENVAULT_GITHUB_WEBHOOK_SECRET
configENVAULT_SDK_MIN_SUPPORTED_VERSION
🔐 secretENVAULT_SESSION_KEY_SECRET
configENVAULT_TEST_AGENT_ID
configENVAULT_TEST_APPROVAL_URL
configENVAULT_TEST_ENVIRONMENT
configENVAULT_TEST_PLATFORM
configENVAULT_TEST_PROJECT_ID
🔐 secretENVAULT_TOKEN
🔐 secretGOOGLE_GENERATIVE_AI_API_KEY
configINIT_CWD
configRELEASE_TARGET
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployEMAIL_PUBLIC_APP_URL
deployNEXT_PUBLIC_API_SIGNATURE_SALT
deployNEXT_PUBLIC_APP_URL
deployNEXT_PUBLIC_GITHUB_APP_NAME
deployNEXT_PUBLIC_SUPABASE_ANON_KEY
deployNEXT_PUBLIC_SUPABASE_URL
deploySUPABASE_SERVICE_ROLE_KEY
// quality suggestions

Dependencies

81 dependencies, 1 flagged: playwright

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

23/23 tools missing one or more hints — envault_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); envault_context (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); envault_pull (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +20 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

Only 1/23 tools referenced in tests (4%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

3 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Secrets stay with their owner

1 secret/sensitive value flow into network calls (SUPABASE_SERVICE_ROLE_KEY → dynamic)

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Production dependencies are patched

0 critical, 8 high severity in production deps — next@16.1.6 (high), next@16.1.6 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dependency freshness

2/68 production deps stale: node-notifier@2023-02-11 (3.3y), tailwindcss-animate@2023-08-28 (2.8y)

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/dinanathdash-envault-mcp-server-a1tnyx?variant=verified)](https://m8ven.ai/mcp/dinanathdash-envault-mcp-server-a1tnyx)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 4450183066243ec8b29978abcc36b5205e75670f
code hash: 67e38c99e03dbdc1b4d244c1a508c54c5bd39dba633a589b10faef880bf33522
verified: 6/16/2026, 12:41:51 PM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client