Env Blueprint Validator
Have your agent validate environment blueprints and env templates before deploy so missing vars and unsafe patterns do not reach production.
Overview
io.github.lazymac2x/env-blueprint-validator is a Ship-phase MCP server that helps your agent validate environment blueprints before you deploy.
What is this MCP server?
- env-blueprint-validator MCP at https://api.lazy-mac.com/env-blueprint-validator/mcp
- Remote streamable-http MCP on Cloudflare Workers
- Version 1.0.0; source at env-blueprint-validator-api on GitHub
- Agent-friendly checks for env blueprint structure before launch
- Supports ship workflows alongside CI and deployment prep
- MCP manifest version 1.0.0
- 1 streamable-http remote endpoint in server.json
- Cloudflare Workers MCP server per catalog description
What problem does it solve?
You discover missing or inconsistent environment variables only when production boot fails after a rushed ship.
Who is it for?
Solo builders shipping to Cloudflare, Vercel, Fly, or Docker who maintain env example files and want agent-driven validation.
Skip if: Organizations that need full secret scanning in git history or SOC2-grade controls without additional dedicated security tools.
What do I get? / Deliverables
Registering the MCP lets your agent flag env blueprint issues during deploy prep so launches fail less often on config gaps.
- Agent-triggered env blueprint validation via MCP
- Fewer production failures from incomplete environment config
- Traceability to env-blueprint-validator-api on GitHub
Recommended MCP Servers
Journey fit
How it compares
Env blueprint validation MCP, not a generic .env linter skill or cloud provisioning marketplace.
Common Questions / FAQ
Who is io.github.lazymac2x/env-blueprint-validator for?
Indie developers and small teams using MCP agents who want structured checks on environment templates before shipping.
When should I use io.github.lazymac2x/env-blueprint-validator?
Use it during ship prep when you finalize .env.example, deployment manifests, or secret mappings and before you promote to production.
How do I add io.github.lazymac2x/env-blueprint-validator to my agent?
Add the remote MCP URL https://api.lazy-mac.com/env-blueprint-validator/mcp with streamable-http transport in Claude Code or Cursor, reload MCP, and run validation from deploy-related prompts.