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.vola-trebla/env-secret-exposure-analyzer-mcp

NPM · ENV-SECRET-EXPOSURE-ANALYZER-MCP · SCANNED AUG 3

Scans projects for secret exposure: leaked API keys, unprotected .env files, and secrets in logs.

+20 this week 66 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 Security86
  • 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
  • No install/post-install scripts declared.Pass
  • 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 & Transparency45
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 547 tokens (~109/item across 5 items; 5 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 Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
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 · env-secret-exposure-analyzer-mcp

# add to Claude Code
claude mcp add vola-trebla-env-secret-exposure-analyzer-mcp -- npx -y env-secret-exposure-analyzer-mcp
# add to Codex CLI
codex mcp add vola-trebla-env-secret-exposure-analyzer-mcp -- npx -y env-secret-exposure-analyzer-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vola-trebla-env-secret-exposure-analyzer-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "env-secret-exposure-analyzer-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add vola-trebla-env-secret-exposure-analyzer-mcp --command npx --arg -y --arg env-secret-exposure-analyzer-mcp
# ~/.hermes/config.yaml
mcp_servers:
  vola-trebla-env-secret-exposure-analyzer-mcp:
    command: "npx"
    args: ["-y", "env-secret-exposure-analyzer-mcp"]
// mcp.json
{
  "mcpServers": {
    "vola-trebla-env-secret-exposure-analyzer-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "env-secret-exposure-analyzer-mcp"
      ]
    }
  }
}
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 +45
    • Provenance: unverified → fail security
    • Known CVEs: unverified → partial security
    • Install scripts: unverified → pass security
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Maintenance: unverified → pass functional
    • Dependency health: unverified → partial functional
    • License: unverified → pass functional
    • Schema quality: unverified → excellent functional
    • MCP protocol: unverified → pass functional
    • Licence: MIT functional
  • 31 Jul 26 −7
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 +4
    • Malware scan: pass → unverified security
    • Security disclosure: unverified → fail functional
    • Tool coverage: unverified → 100 functional
  • 28 Jul 26 −22
    • Tool coverage: 100 → unverified functional
    • Security disclosure: fail → unverified functional
    • First check of Schema quality: unverified functional
  • 27 Jul 26 46

    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/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

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 — 5 exposed · ~547 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
check_gitignore_coverage ~63

Check whether sensitive files (.env, .env.local, secrets.json, etc.) are properly covered by .gitignore rules. Flags files that contain secrets but could be accidentally committed.

NameTypeReqDescription
projectPathstringyesAbsolute path to the project root to check

No output schema declared.

No examples provided.

scan_ci_workflows ~141

Scans GitHub Actions (.github/workflows/*.yml), CircleCI (.circleci/config.yml), and GitLab CI (.gitlab-ci.yml) workflow files for dangerous secret interpolation patterns. Detects ${{ secrets.* }} and ${{ github.token }} used directly in run: steps (log_leak risk — GitHub Actions logs the expanded plaintext) and ${{ github.event.pull_request.* }} / issue / commit content interpolated in shell commands (injection risk — attacker-controlled input). Returns file, job, step, pattern_found, risk, and recommendation.

NameTypeReqDescription
repo_pathstringyesAbsolute path to the repository root to scan

No output schema declared.

No examples provided.

scan_for_log_leaks ~70

Scan source files for console.log / logger calls that may print environment variables or secrets at runtime. Catches patterns like console.log(process.env.SECRET) or logger.info({ apiKey }) before they reach production logs.

NameTypeReqDescription
projectPathstringyesAbsolute path to the project root to scan

No output schema declared.

No examples provided.

scan_for_secrets ~115

Scan a project directory for hardcoded secrets, API keys, tokens, and passwords. Detects patterns like AWS keys, GitHub tokens, Stripe keys, private keys, and generic high-entropy strings. Returns file path, line number, severity, and a masked preview.

NameTypeReqDescription
extensionsarrayFile extensions to scan, e.g. [".ts",".js",".env"]. Defaults to common source files.
projectPathstringyesAbsolute path to the project root to scan, e.g. /project

No output schema declared.

No examples provided.

scan_git_history ~158

Scan the git commit history of a repository for secrets that were ever committed, even if later deleted. Detects hardcoded API keys, tokens, passwords, and other credentials added in diff hunks across recent commits. Returns each finding with its commit hash, file, line, severity, a masked preview, entropy score, whether the secret is still present in the working tree, and whether rotation is required. Respects .gitleaksignore.

NameTypeReqDescription
last_n_commitsintegerMaximum number of recent commits to scan (default: 50)
repo_pathstringyesAbsolute path to the git repository root to scan
since_daysintegerOnly scan commits from the last N days (default: 30)

No output schema declared.

No examples provided.