Skip to main content
Glama
vola-trebla

env-secret-exposure-analyzer-mcp

by vola-trebla
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to env-secret-exposure-analyzer-mcp

No user-submitted related servers found.

    Related Servers

    • secretscan

      wedo911
      A
      license
      A
      quality
      C
      maintenance
      Scans diffs, files, and snippets for leaked secrets like AWS keys, GitHub tokens, and private keys, returning redacted findings while running fully locally without network calls.
      1
      MIT

    • credential-free

      skutry
      A
      license
      Not graded
      quality
      C
      maintenance
      Scans code for exposed secrets, API keys, tokens, and credentials across 69 patterns covering cloud services, AI platforms, payment providers, authentication services, and databases.
      MIT

    • opzyai

      thfothijn
      A
      license
      Not graded
      quality
      B
      maintenance
      Local-first security check for AI coding agents — finds hardcoded secrets, exposed .env files, git-history leaks and vulnerable dependencies (OSV), entirely on your machine. Ask your agent "is this safe to ship?" and get a Launch Readiness score with a fix for every finding.
      MIT

    • secrets-audit-mcp

      eltociear
      A
      license
      Not graded
      quality
      B
      maintenance
      Detects leaked credentials in source code with tools to scan text, files, and directories for API keys, tokens, and private keys across 30+ providers.
      1
      MIT

    • GuardX

      harshzagade
      A
      license
      Not graded
      quality
      B
      maintenance
      A keyless, defensive code-security auditor that scans codebases for hardcoded secrets, audits dependencies for known CVEs, and checks passwords against breach data using k-anonymity.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinctly different aspect of secret exposure: hardcoded secrets in files, .gitignore coverage, log statement leaks, CI workflow risky patterns, and git history. There is no overlap or ambiguity between them.

    Naming Consistency4/5

    The verbs are mostly consistent (scan_for_* vs scan_* vs check_*), with scan_ as a common prefix. The inconsistent use of 'for' and the odd one out 'check_' create minor deviation, but the pattern is still recognizable.

    Tool Count5/5

    Five tools is well-scoped for a secret exposure analyzer. Each tool covers a relevant and non-redundant aspect, and the number is appropriate for the domain.

    Completeness5/5

    The set covers the primary surface areas for secret exposure: current source code, gitignore protection, runtime log leakage, CI workflow secret handling, and historical git leaks. This provides comprehensive coverage for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources