@mcpx-digital/env-check
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| compare_env_filesA | Compare .env.example vs .env for missing and extra keys; list empty required keys. Local .env files only. Reports redact values and never echo secrets. |
| detect_empty_requiredB | Detect missing or empty required vars (from example or explicit requiredKeys). Values redacted. Local .env files only. Reports redact values and never echo secrets. |
| redact_env_reportA | Produce a paste-safe inventory of keys in an env file with all values redacted. Local .env files only. Reports redact values and never echo secrets. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
compare_env_files and detect_empty_required overlap in identifying missing/empty required keys, though the former is example-based diffing and the latter supports explicit requiredKeys. redact_env_report is clearly distinct.
All three tools use a consistent snake_case verb_noun pattern (compare_env_files, detect_empty_required, redact_env_report). This makes the tool surface predictable and easy to navigate.
Three tools is within the ideal scope for a focused env-check utility, and each tool serves a distinct operation. There is no sense of bloat or a too-thin surface.
The set covers the core env-check lifecycle: comparing env files, validating required variables, and producing redacted output. For the stated local .env-focused purpose, there are no obvious dead ends.