io.github.vola-trebla/env-secret-exposure-analyzer-mcp
NPM · ENV-SECRET-EXPOSURE-ANALYZER-MCP · SCANNED SEP 21
Scans projects for secret exposure: leaked API keys, unprotected .env files, and secrets in logs.
Available components
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 → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 123 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- 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 Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.vola-trebla/env-secret-exposure-analyzer-mcp server?
io.github.vola-trebla/env-secret-exposure-analyzer-mcp runs locally as an npm package, launched with npx -y env-secret-exposure-analyzer-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · env-secret-exposure-analyzer-mcp
claude mcp add vola-trebla-env-secret-exposure-analyzer-mcp -- npx -y env-secret-exposure-analyzer-mcp
{
"mcpServers": {
"vola-trebla-env-secret-exposure-analyzer-mcp": {
"command": "npx",
"args": [
"-y",
"env-secret-exposure-analyzer-mcp"
]
}
}
} {
"servers": {
"vola-trebla-env-secret-exposure-analyzer-mcp": {
"command": "npx",
"args": [
"-y",
"env-secret-exposure-analyzer-mcp"
]
}
}
} codex mcp add vola-trebla-env-secret-exposure-analyzer-mcp -- npx -y env-secret-exposure-analyzer-mcp
{
"$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
}
}
} openclaw mcp add vola-trebla-env-secret-exposure-analyzer-mcp --command npx --arg -y --arg env-secret-exposure-analyzer-mcp
mcp_servers:
vola-trebla-env-secret-exposure-analyzer-mcp:
command: "npx"
args: ["-y", "env-secret-exposure-analyzer-mcp"] {
"McpServers": {
"vola-trebla-env-secret-exposure-analyzer-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"env-secret-exposure-analyzer-mcp"
]
}
}
} assistant mcp add vola-trebla-env-secret-exposure-analyzer-mcp -t stdio -c npx -a -y env-secret-exposure-analyzer-mcp
{
"mcpServers": {
"vola-trebla-env-secret-exposure-analyzer-mcp": {
"command": "npx",
"args": [
"-y",
"env-secret-exposure-analyzer-mcp"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −2
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −2
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.80 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 21 Sept 2026 · Analysed npm/env-secret-exposure-analyzer-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| projectPath | string | yes | Absolute 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.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_path | string | yes | Absolute 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.
| Name | Type | Req | Description |
|---|---|---|---|
| projectPath | string | yes | Absolute 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.
| Name | Type | Req | Description |
|---|---|---|---|
| extensions | array | – | File extensions to scan, e.g. [".ts",".js",".env"]. Defaults to common source files. |
| projectPath | string | yes | Absolute 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.
| Name | Type | Req | Description |
|---|---|---|---|
| last_n_commits | integer | – | Maximum number of recent commits to scan (default: 50) |
| repo_path | string | yes | Absolute path to the git repository root to scan |
| since_days | integer | – | Only scan commits from the last N days (default: 30) |
No output schema declared.
No examples provided.
What is the io.github.vola-trebla/env-secret-exposure-analyzer-mcp server?
io.github.vola-trebla/env-secret-exposure-analyzer-mcp is listed in the public MCP registry as io.github.vola-trebla/env-secret-exposure-analyzer-mcp. Scans projects for secret exposure: leaked API keys, unprotected .env files, and secrets in logs. This page covers its npm package (env-secret-exposure-analyzer-mcp).
Is the io.github.vola-trebla/env-secret-exposure-analyzer-mcp server safe to use?
io.github.vola-trebla/env-secret-exposure-analyzer-mcp scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.vola-trebla/env-secret-exposure-analyzer-mcp server expose?
io.github.vola-trebla/env-secret-exposure-analyzer-mcp exposes 5 tools: scan_for_secrets, check_gitignore_coverage, scan_for_log_leaks, scan_ci_workflows, scan_git_history. Their descriptions and schemas cost roughly 547 tokens of context every time the server is loaded.
Is the io.github.vola-trebla/env-secret-exposure-analyzer-mcp server still maintained?
io.github.vola-trebla/env-secret-exposure-analyzer-mcp is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.vola-trebla/env-secret-exposure-analyzer-mcp server under?
io.github.vola-trebla/env-secret-exposure-analyzer-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.