# @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)

```bash
npx -y @mcpx-digital/env-check
```

> Prepared for npm as `@mcpx-digital/env-check`. Until published, run from a local clone.

## Cursor `mcp.json` example

```json
{
  "mcpServers": {
    "env-check": {
      "command": "npx",
      "args": ["-y", "@mcpx-digital/env-check"]
    }
  }
}
```

Local clone:

```json
{
  "mcpServers": {
    "env-check": {
      "command": "node",
      "args": ["/absolute/path/to/env-check-mcp/index.js"]
    }
  }
}
```

## Tools

| Tool | What it does |
|------|----------------|
| `compare_env_files` | Missing / extra / empty keys vs `.env.example` |
| `detect_empty_required` | Empty or missing required vars (values redacted) |
| `redact_env_report` | 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

```bash
git clone https://github.com/TheoryofShadows/env-check-mcp.git
cd env-check-mcp
npm install
npm test
node index.js
```

## Sell / list on MCPX

Suggested listing price: **$6**.

Install command: `npx -y @mcpx-digital/env-check`

## License

MIT © TheoryofShadows