io.github.vola-trebla/env-secret-exposure-analyzer-mcp

MCPcommunity
v0.2.0io.github.vola-treblaUnknownUpdated 4mo agonpmGitHub

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

Your AI agent is one debug session away from leaking your secrets. MCP server that scans your project for secret exposure risks — hardcoded API keys, unprotected files, and calls that print credentials at runtime. Before your agent accidentally reads them out loud. You ask your AI agent to debug a config issue. It reads . Inside: The agent now has your database password in its context. It might…

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.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
4mo agoLast update
Package
Authorio.github.vola-trebla
LicenseUnknown
Version0.2.0
Sourcemcp-registry
npmenv-secret-exposure-analyzer-mcp
GitHubvola-trebla/env-secret-exposure-analyzer-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—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)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface5 tools · none privileged
Security scan✓ Cleanv0.2.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

5 tools · none privileged
Statically extracted from the published packagev0.2.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.

scan_for_secretsNo description published

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

check_gitignore_coverageNo description published

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

scan_for_log_leaksNo description published

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

scan_ci_workflowsNo description published

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

scan_git_historyNo description published

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

0 of 5 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

Your AI agent is one debug session away from leaking your secrets. MCP server that scans your project for secret exposure risks — hardcoded API keys, unprotected files, and calls that print credentials at runtime. Before your agent accidentally reads them out loud. You ask your AI agent to debug a config issue. It reads . Inside: The agent now has your database password in its context. It might log it, include it in a summary, or pass it to another tool. And your isn't in , so the next will do…

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

5 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

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