io.github.rog0x/env
NPM · @ROG0X/MCP-ENV-TOOLS · SCANNED AUG 3
Dotenv parser, ports, system info for AI agents
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 133 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 542 tokens (~38/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @rog0x/mcp-env-tools
claude mcp add rog0x-env -- npx -y @rog0x/mcp-env-tools
codex mcp add rog0x-env -- npx -y @rog0x/mcp-env-tools
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rog0x-env": {
"type": "local",
"command": [
"npx",
"-y",
"@rog0x/mcp-env-tools"
],
"enabled": true
}
}
} openclaw mcp add rog0x-env --command npx --arg -y --arg @rog0x/mcp-env-tools
mcp_servers:
rog0x-env:
command: "npx"
args: ["-y", "@rog0x/mcp-env-tools"] {
"mcpServers": {
"rog0x-env": {
"command": "npx",
"args": [
"-y",
"@rog0x/mcp-env-tools"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +4
- Stability: unverified → 0.23 ▲ functional
- 2 Aug 26 +44
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- License: unverified → pass ▲ functional
- Licence: MIT functional
- 31 Jul 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 46
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed npm/@rog0x/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
deps_check_tools ~50
Check if specified tools/commands are installed and get their versions
| Name | Type | Req | Description |
|---|---|---|---|
| tools | array | yes | List of tool/command names to check (e.g. node, npm, python, git, docker) |
No output schema declared.
No examples provided.
deps_check_versions ~30
Check if installed tools meet minimum version requirements
| Name | Type | Req | Description |
|---|---|---|---|
| requirements | array | yes | List of tool version requirements |
No output schema declared.
No examples provided.
deps_verify_path ~20
Analyze the system PATH and check for common tool directories
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
env_compare_files ~55
Compare a .env file against a .env.example to find missing or extra variables
| Name | Type | Req | Description |
|---|---|---|---|
| envPath | string | yes | Path to the .env file |
| examplePath | string | yes | Path to the .env.example file |
No output schema declared.
No examples provided.
env_detect_from_docker_compose ~39
Detect environment variables referenced in a docker-compose YAML file
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | yes | Path to the docker-compose.yml file |
No output schema declared.
No examples provided.
env_detect_from_package_json ~34
Detect environment variables referenced in package.json scripts
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | yes | Path to the package.json file |
No output schema declared.
No examples provided.
env_detect_missing ~51
Check if required environment variables are present and populated in a .env file
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | yes | Path to the .env file |
| requiredKeys | array | yes | List of required variable names |
No output schema declared.
No examples provided.
env_find_duplicates ~33
Find duplicate variable keys in a .env file
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | yes | Path to the .env file |
No output schema declared.
No examples provided.
env_generate_example ~42
Generate .env.example content from an existing .env file, stripping values and adding placeholders
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | yes | Path to the source .env file |
No output schema declared.
No examples provided.
env_list_variables ~37
Parse a .env file and list all variable keys with masked values
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | yes | Path to the .env file |
No output schema declared.
No examples provided.
port_check ~34
Check if a specific port is in use and identify the process using it
| Name | Type | Req | Description |
|---|---|---|---|
| port | integer | yes | Port number to check |
No output schema declared.
No examples provided.
port_find_available ~54
Find available ports within a given range
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | — | Number of available ports to find |
| endPort | integer | yes | End of port range |
| startPort | integer | yes | Start of port range |
No output schema declared.
No examples provided.
port_list_processes ~28
List processes using specific ports
| Name | Type | Req | Description |
|---|---|---|---|
| ports | array | yes | List of ports to check |
No output schema declared.
No examples provided.
system_info ~35
Get system information: OS, CPU, memory, disk, and installed runtime versions (Node, npm, Python, Git, Docker)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.