@mcpx-digital/env-check
Related Servers
Alternatives to @mcpx-digital/env-check
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables agents to diagnose environment-variable issues read-only without exposing values, including .env versus template comparison, undocumented or unused variables across source code, shape validation, secret-exposure checks, git-ignore and history checks, and safe .env.example proposals.6MIT
- AlicenseNot gradedqualityBmaintenanceEnables scanning a repository's source files for actual environment variable reads and diffing those names against .env.example or .env.sample. Returns a deterministic JSON report with the sync verdict, counts, and findings for used-but-undocumented, documented-but-unused, and missing-example vars, without ever reading values.60 npmMIT
- AlicenseAqualityCmaintenanceEnables 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.3MIT
- AlicenseNot gradedqualityBmaintenanceRuns deterministic local environment checks against a repository and returns a JSON pass/fail report covering Node version, git and npm availability, lockfiles, and env-file key completeness without executing repository code or exposing secret values.77 npmMIT
- AlicenseNot gradedqualityBmaintenanceCompares the key names across .env file contents supplied by an agent and reports which keys are missing from which file, supporting auto, manual, and template comparison modes. Only key names are returned, never values, and the server reads no files or network resources of its own.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables comparing local and CI environment descriptors to report differences in Node version, OS, lockfile presence, and environment variable keys—including changed values by key only—without echoing secret values.66 npmMIT
TDQS
Scored across 3 tools
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.
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.
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.
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.