Skip to content

io.github.lazymac2x/env-blueprint-validator

by lazymac2x · remote · no sign-in to list tools · v1.0.0 · published by GitHub user lazymac2x

Cloudflare Workers MCP server: env-blueprint-validator

Changes · 24 high findings
CompareRegistry entry

3 tools: 2 change things and 1 only read.

Scanned Oct 21, 2026

4 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http env-blueprint-validator https://api.lazy-mac.com/env-blueprint-validator/mcp

Findings

Matches of fixed checks, with the text they matched.

4 high
  • Highenv_validate

    The input schema at properties.env_content.description refers to ".env".

    Matched text

    inputSchema.properties.env_content.description: "Raw .env file content (KEY=VALUE pairs, one per..."

    What this check looks for
  • Highdrift_detect

    The description refers to ".env" and ".env.example".

    Matched text

    description: "Detect differences between .env and .env.example files. Identifies adde..."

    What this check looks for
  • Highdrift_detect

    The input schema at properties.env_content.description refers to ".env".

    Matched text

    inputSchema.properties.env_content.description: "Content of .env file"

    What this check looks for
  • Highdrift_detect

    The input schema at properties.example_content.description refers to ".env.example".

    Matched text

    inputSchema.properties.example_content.description: "Content of .env.example file"

    What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

3 tools

Changes things 2Claude Code: ask
  • drift_detectDetect differences between .env and .env.example files.3 findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • High

      The description refers to ".env" and ".env.example".

      Matched text

      description: "Detect differences between .env and .env.example files. Identifies adde..."

      What this check looks for
    • High

      The input schema at properties.env_content.description refers to ".env".

      Matched text

      inputSchema.properties.env_content.description: "Content of .env file"

      What this check looks for
    • High

      The input schema at properties.example_content.description refers to ".env.example".

      Matched text

      inputSchema.properties.example_content.description: "Content of .env.example file"

      What this check looks for
    Description, as the server wrote it
    Detect differences between .env and .env.example files. Identifies added, removed, and modified variables.
  • schema_defineDefine and validate an environment variable schema.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Define and validate an environment variable schema. Ensures schema structure is correct before using it for validation.
Only reads 1Claude Code: allow
  • env_validateValidate environment variables against a schema.1 finding

    Why it is in this group

    • The name "env_validate" says "validate": a word for reading.

    Findings

    • High

      The input schema at properties.env_content.description refers to ".env".

      Matched text

      inputSchema.properties.env_content.description: "Raw .env file content (KEY=VALUE pairs, one per..."

      What this check looks for
    Description, as the server wrote it
    Validate environment variables against a schema. Checks for required fields, type correctness, pattern matching, and enum constraints.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http env-blueprint-validator https://api.lazy-mac.com/env-blueprint-validator/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__env-blueprint-validator__env_validate"
    ],
    "ask": [
      "mcp__env-blueprint-validator__schema_define",
      "mcp__env-blueprint-validator__drift_detect"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as env-blueprint-validator. Review it before you use it.