io.github.rog0x/env
NPM · @ROG0X/MCP-ENV-TOOLS
Dotenv parser, ports, system info for AI agents
Available components
Last scanned (6 hours ago)
Scores higher than 75% of npm servers
Category Developer Tools
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 → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. 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 228 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability69
- 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 +1
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −2
- Stability: pass → 0.90 functional
- 2 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 31 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 21 Oct 26 +1
- Stability: 0.97 → pass security
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 6 Nov 2026 · Analysed npm/@rog0x/mcp-env-tools@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
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.
How do I install the io.github.rog0x/env MCP server?
io.github.rog0x/env runs locally as an npm package, launched with npx -y @rog0x/mcp-env-tools. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @rog0x/mcp-env-tools
claude mcp add rog0x-env -- npx -y @rog0x/mcp-env-tools
What is the io.github.rog0x/env MCP server?
io.github.rog0x/env is an MCP server listed in the public MCP registry as io.github.rog0x/env. Dotenv parser, ports, system info for AI agents. This page covers its npm package (@rog0x/mcp-env-tools).
Is the io.github.rog0x/env MCP server safe to use?
io.github.rog0x/env scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.rog0x/env MCP server expose?
io.github.rog0x/env exposes 14 tools: env_list_variables, env_detect_missing, env_compare_files, env_find_duplicates, env_generate_example, and 9 more. Their descriptions and schemas cost roughly 542 tokens of context every time the server is loaded.
Is the io.github.rog0x/env MCP server still maintained?
io.github.rog0x/env is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.rog0x/env MCP server under?
io.github.rog0x/env declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.rog0x/env MCP server?
VerifyMCP ran 15 checks on io.github.rog0x/env, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.rog0x/env: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.