Env Variable Config Validator

Env Variable Config Validator MCP Connector for Claude

A+

Validate .env files for structural integrity, type accuracy, and security hygiene.

3 tools Official Updated Oct 1, 2026 Official Vinkius Partner

Ensure your application starts reliably by validating environment configurations. This MCP server acts as a specialized auditing engine for .env files, detecting missing required keys, type mismatches (e.g., non-numeric values where integers are expected), and duplicate definitions. Use validate_env_structure to check for completeness, verify_data_integrity to enforce type constraints and whitelists, and audit_config_health to identify security risks like secret exposure or unused variables that clutter your configuration.

envdotenvvalidationsecuritydevopsconfig

3 tools expose this connector's capabilities to your AI agent.

audit_config_health

Audits .env for security risks and unused variables

validate_env_structure

Validates the structural integrity of .env files

verify_data_integrity

Verifies that .env values match expected types

See how to talk to your AI agent using Env Variable Config Validator.

Check if my .env file is missing any required keys: PORT=3000 DB_URL=postgres://localhost:5432

The structural check is complete. All required keys (PORT, DB_URL) are present in the provided content.

Are there any security risks or unused variables in this config? API_KEY=sk_test_4eC39HqLyjWDarjtT1zdp7cu DEBUG=true OLD_VAR=something

The health audit identified a potential 'secret_exposure' for API_KEY and an 'unused_variable' for OLD_VAR.

Verify that my PORT variable is a number in this content: PORT=abc

Integrity check failed: The value for 'PORT' is not a valid number.

You can use the `validate_env_structure` tool by providing your `.env` content and a list of the keys that must be present.

Related Connectors