@mcpx-digital/env-check
Provides tools for comparing .env.example against .env files, detecting missing, extra, or empty environment variables, and generating redacted reports without exposing secret values.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@mcpx-digital/env-check Compare .env.example to .env and list the missing keys"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@mcpx-digital/env-check
MCP server that compares .env.example vs .env, finds missing/extra/empty keys, and produces redacted reports.
Never echoes secrets. All value reports are redacted (
***redacted***/***present***). Local files only — no uploading env files anywhere.
Install (MCPX / npx)
npx -y @mcpx-digital/env-checkPrepared for npm as
@mcpx-digital/env-check. Until published, run from a local clone.
Related MCP server: envdoc
Cursor mcp.json example
{
"mcpServers": {
"env-check": {
"command": "npx",
"args": ["-y", "@mcpx-digital/env-check"]
}
}
}Local clone:
{
"mcpServers": {
"env-check": {
"command": "node",
"args": ["/absolute/path/to/env-check-mcp/index.js"]
}
}
}Tools
Tool | What it does |
| Missing / extra / empty keys vs |
| Empty or missing required vars (values redacted) |
| Paste-safe key inventory with all values redacted |
Disclaimer
Use only on env files you own. Do not commit real .env files. This tool helps catch misconfiguration; it does not replace a secrets manager.
Example prompts
“Compare .env.example to .env and list missing keys”
“Which required env vars are empty? (redacted)”
“Give me a redacted inventory of .env for a ticket”
Development
git clone https://github.com/TheoryofShadows/env-check-mcp.git
cd env-check-mcp
npm install
npm test
node index.jsSell / list on MCPX
Suggested listing price: $6.
Install command: npx -y @mcpx-digital/env-check
License
MIT © TheoryofShadows
Available Tools
3 toolscompare_env_filesA
Compare .env.example vs .env for missing and extra keys; list empty required keys. Local .env files only. Reports redact values and never echo secrets.
Inputs: envPath, examplePath, includeCommentedExample.
detect_empty_requiredB
Detect missing or empty required vars (from example or explicit requiredKeys). Values redacted. Local .env files only. Reports redact values and never echo secrets.
Inputs: envPath, examplePath, requiredKeys, includeCommentedExample.
redact_env_reportA
Produce a paste-safe inventory of keys in an env file with all values redacted. Local .env files only. Reports redact values and never echo secrets.
Inputs: envPath.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Related MCP Connectors
Scan configs, files, or text for leaked secrets and obvious misconfigurations. Nothing stored.
A vault for .env files and project credentials: one encryption key per project, a second factor before protected values open, an audit row for every reveal, and scoped MCP access for coding agents.
Compare two JSON files deeply without worrying about key or array order. Detect missing, extra, an…
Scan text and git diffs for committed credentials using real vendor key formats plus entropy.
Related MCP Servers
- 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 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
- 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 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