Env Linter

Developer REST API MCP

Lint a dotenv file for duplicate keys, unquoted spaces, export prefixes, secret-looking values (masked), and drift against an optional .env.example. Returns issues and a masked key table. Does not execute the file.

This page documents the HTTP endpoint POST /api/tools/env-linter/execute. See the MCP reference →

Call it over REST

POST https://api.findutils.com/api/tools/env-linter/execute · no API keys · 60 requests/min per IP

Execute — verified arguments

curl -X POST https://api.findutils.com/api/tools/env-linter/execute \
  -H "Content-Type: application/json" \
  -d '{
    "env": "FOO=1\nFOO=2\n",
    "example": "FOO=\nBAR=\n"
  }'

Parameter schema for this endpoint

curl https://api.findutils.com/api/tools/env-linter

Interactive docs · OpenAPI 3.1 spec · All REST tools

Input schema

Argument Type Required Description
env string yes Contents of a .env file.
example string no Optional .env.example contents for key drift checks.

Example arguments (verified)

{
  "env": "FOO=1\nFOO=2\n",
  "example": "FOO=\nBAR=\n"
}

Also an MCP tool

Claude, Cursor, and any MCP client can call this tool as findutils:env_linter after one connect command.

Connect once

claude mcp add findutils --transport http https://mcp.findutils.com/
Open the MCP reference for Env Linter →

More Developer tools