Skip to main content
Glama
TheoryofShadows

@mcpx-digital/env-check

Related Servers

Alternatives to @mcpx-digital/env-check

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables comparing local JSON/YAML locale files to find missing or extra keys against a base locale, detect empty, null, or whitespace translations, and list flattened dot-path keys for a single file. Works entirely on local files with no network calls or translation APIs.
      3
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Resolves configuration and environment-variable precedence across .env files, Docker Compose, and Kubernetes, showing what a variable actually evaluates to at runtime and why.
      5
      42 npm
      MIT
    • 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
    • A
      license
      A
      quality
      A
      maintenance
      Checks your local development environment for common issues like wrong Node version, missing Docker, missing git config, missing .env keys, and busy ports, and provides fixes.
      6
      14 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Scans files, directories, and environment configurations for exposed secrets, API keys, and credentials, redacting matches and providing allowlist support. Enables natural-language secret detection in projects and CI/CD integration via CLI.
      871 npm
      MIT

    TDQS

    A3.8/5.0

    Scored across 3 tools

    Disambiguation3/5

    compare_env_files and detect_empty_required overlap in identifying missing/empty required keys, though the former is example-based diffing and the latter supports explicit requiredKeys. redact_env_report is clearly distinct.

    Naming Consistency5/5

    All three tools use a consistent snake_case verb_noun pattern (compare_env_files, detect_empty_required, redact_env_report). This makes the tool surface predictable and easy to navigate.

    Tool Count5/5

    Three tools is within the ideal scope for a focused env-check utility, and each tool serves a distinct operation. There is no sense of bloat or a too-thin surface.

    Completeness5/5

    The set covers the core env-check lifecycle: comparing env files, validating required variables, and producing redacted output. For the stated local .env-focused purpose, there are no obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues