Listed from the MCP registry; nobody on Odel publishes it.

MCP server: One MCP server.

Env Contract

@mrfentmenMCP server · External

Local value-free environment contract and configuration drift inspection. Tools include inspect...

Code searchv1.0.1TypeScript
Freeno charge per call

Runs on your machine from its package; the steps are below.

What it does

  1. Reads
  2. Writes
  3. High impact

At most: only reads or looks up information.

What it costs

Free

Odel charges nothing per call. The publisher may charge for its own service.

Runs locally over stdio

This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).

npmenv-contract-mcpv1.0.1

Run

npx -y env-contract-mcp

MCP client config

{
  "mcpServers": {
    "env-contract": {
      "command": "npx",
      "args": [
        "-y",
        "env-contract-mcp"
      ]
    }
  }
}
README1 min read

env-contract-mcp

Env Contract is a local MCP tool for finding configuration drift before a project fails at runtime. It compares variable names declared in .env.example and dotenv files with likely environment references in source and config files.

Tool

  • inspect_contract: report declared names, referenced names, missing names, unused names, and the files where they occur.

Safety

  • Reads local project files only; it never fetches URLs.
  • Never reads or emits environment values. Only names and bounded file paths are returned.
  • Ignores node_modules, build output, coverage, and Git internals.
  • Caps file count, file size, recursion depth, and output.
  • Matching is heuristic and is not a replacement for a build, deployment check, or secret scanner.

Set ENV_CONTRACT_ROOT to bound analysis to a workspace root. It defaults to the parent of the MCP package when launched normally.

Run

bash
npm install
npm run build
node dist/index.js

Similar modules

Browse Code search