# .env checker: dotenv, Node, Vite, Next.js (oci · ghcr.io/lawatch/dotenv-check)

Real value of each .env variable and the file:line that decides, for dotenv, node, Vite, Next.js

- Trust score: 41/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-22

## Components

- mcpb · `dotenv-check-1.0.0.mcpb`: 38/100, [markdown](https://verifymcp.io/servers/lawatch-dotenv-check/dotenv-check.md), [page](https://verifymcp.io/servers/lawatch-dotenv-check/dotenv-check)
- oci · `ghcr.io/lawatch/dotenv-check`: 41/100 (this document), [markdown](https://verifymcp.io/servers/lawatch-dotenv-check/ghcr-io-lawatch-dotenv-check.md), [page](https://verifymcp.io/servers/lawatch-dotenv-check/ghcr-io-lawatch-dotenv-check)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/lawatch/dotenv-check`
- Version: `1.0.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-22.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1010 tokens (~336/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (33% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the .env checker: dotenv, Node, Vite, Next.js MCP server?

.env checker: dotenv, Node, Vite, Next.js runs locally as a container image, launched with docker run --rm -i ghcr.io/lawatch/dotenv-check:1.0.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add lawatch-dotenv-check -- docker run --rm -i ghcr.io/lawatch/dotenv-check:1.0.0
```

### Cursor

```json
{
  "mcpServers": {
    "lawatch-dotenv-check": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/lawatch/dotenv-check:1.0.0"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "lawatch-dotenv-check": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/lawatch/dotenv-check:1.0.0"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add lawatch-dotenv-check -- docker run --rm -i ghcr.io/lawatch/dotenv-check:1.0.0
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lawatch-dotenv-check": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/lawatch/dotenv-check:1.0.0"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  lawatch-dotenv-check:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/lawatch/dotenv-check:1.0.0"]
```

### Netclaw

```json
{
  "McpServers": {
    "lawatch-dotenv-check": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/lawatch/dotenv-check:1.0.0"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "lawatch-dotenv-check": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/lawatch/dotenv-check:1.0.0"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-22 (score 41, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-20 (score 40, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 39, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 38)

First indexed and scored.

## MCP tools (3)

### `resolve_env` (~620 tokens)

What value does each .env variable really get?

Answers "why is my env variable empty / wrong / undefined?" exactly as the real loader does it. Give the .env files and the loader: "dotenv" (npm dotenv 17, optional dotenv-expand 12 and override), "node" (node --env-file / process.loadEnvFile), "vite" (Vite loadEnv: .env, .env.local, .env.[mode], .env.[mode].local, VITE_ prefix) or "nextjs" (@next/env: .env.[mode].local, .env.local, .env.[mode], .env; NEXT_PUBLIC_). Returns for each variable: the final value, the file:line that decides it, the definitions that lose and why (first file wins vs last file wins, variables already set in the environment win), the raw text before $VAR expansion, whether it reaches browser code, plus the traps found: unquoted "#" cutting a value, an unclosed quote swallowing the next lines, "KEY= " eating the next line under Node and Vite, $VAR left literal or expanded inside single quotes, references to undefined variables, self-references that crash the loader, secrets exposed by VITE_ or NEXT_PUBLIC_, files the loader never reads in this mode. Offline: nothing is sent anywhere.

Input parameters:

- `env_prefix` (string|array): vite only: envPrefix from vite.config (default "VITE_").
- `expand` (boolean): dotenv only: also run dotenv-expand (expands $VAR and ${VAR:-default}). Default false.
- `files` (object, required): The .env files, as { "<file name>": "<content>" }, e.g. { ".env": "PORT=3000", ".env.local": "PORT=4000" }. For vite and nextjs, use the real file names (.env, .env.local, .env.development, .env.prod…
- `keys` (array): Only report these variables (default: all).
- `loader` (string, required): Who loads the files. dotenv = require("dotenv").config(...); node = node --env-file=...; vite = Vite dev/build; nextjs = next dev/build/start.
- `mode` (string): vite: the mode (default "development"; "vite build" uses "production"). nextjs: development (next dev, default), production (next build / next start) or test (NODE_ENV=test).
- `order` (array): dotenv and node only: the files in the order given to config({ path: [...] }) or to the --env-file flags. Default: ".env" alone for dotenv, all files in the given order for node.
- `override` (boolean): dotenv only: config({ override: true }). Default false.
- `process_env` (object): Variables already set in the shell or CI before the loader runs (they usually win over the files). Only names that matter; never needed for a simple check.

Output parameters:

- `files_read_in_order` (array)
- `loader` (string)
- `mode` (string)
- `notes` (array)
- `problems` (array)
- `variables` (object)

### `parse_env_file` (~141 tokens)

Parse one .env file exactly, line by line

Parses one .env file with the real parser of "dotenv" (npm dotenv 16-17; also Next.js, dotenv-cli, Prisma, many CLIs) or "node" (node --env-file, process.loadEnvFile, util.parseEnv; also Vite 8) and returns each value with its line, plus every line that is silently ignored, values cut at "#", unclosed quotes, multi-line values, duplicate keys and other traps. Use it to review or debug a .env / .env.example file.

Input parameters:

- `content` (string, required): Content of the .env file.
- `parser` (string): Default "dotenv".

### `compare_env_parsers` (~111 tokens)

Does this .env read the same with dotenv and with Node / Vite 8?

Parses the same .env content with npm dotenv and with Node's built-in parser (node --env-file, used by Vite 8) and lists every variable whose value differs. Run it before switching from dotenv to node --env-file, or when upgrading Vite: the two parsers disagree on keys with spaces, "KEY= " followed by a new line, backslash escapes, unclosed quotes, inline comments and more.

Input parameters:

- `content` (string, required): Content of the .env file.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/lawatch-dotenv-check/ghcr-io-lawatch-dotenv-check#diagnostics

## Score history

- 2026-11-22: 41
- 2026-11-21: 40
- 2026-11-20: 40
- 2026-11-19: 39
- 2026-11-18: 39
- 2026-11-17: 38

## Common questions

### What is the .env checker: dotenv, Node, Vite, Next.js MCP server?

.env checker: dotenv, Node, Vite, Next.js is an MCP server listed in the public MCP registry as io.github.Lawatch/dotenv-check. Real value of each .env variable and the file:line that decides, for dotenv, node, Vite, Next.js. This page covers its container image (ghcr.io/lawatch/dotenv-check).

### Is the .env checker: dotenv, Node, Vite, Next.js MCP server safe to use?

.env checker: dotenv, Node, Vite, Next.js scores 41 out of 100 on VerifyMCP. 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 .env checker: dotenv, Node, Vite, Next.js MCP server expose?

.env checker: dotenv, Node, Vite, Next.js exposes 3 tools: resolve_env, parse_env_file, compare_env_parsers. Their descriptions and schemas cost roughly 872 tokens of context every time the server is loaded.

### Is the .env checker: dotenv, Node, Vite, Next.js MCP server still maintained?

.env checker: dotenv, Node, Vite, Next.js is still listed as active in the MCP registry. We last reached this channel on 22 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 .env checker: dotenv, Node, Vite, Next.js MCP server under?

.env checker: dotenv, Node, Vite, Next.js 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 .env checker: dotenv, Node, Vite, Next.js MCP server?

VerifyMCP ran 12 checks on .env checker: dotenv, Node, Vite, Next.js, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about .env checker: dotenv, Node, Vite, Next.js: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- GitHub Container Registry: https://ghcr.io/lawatch/dotenv-check
- Repository: https://github.com/Lawatch/10aday
- Changelog RSS feed: https://verifymcp.io/servers/lawatch-dotenv-check/ghcr-io-lawatch-dotenv-check.xml
- Changelog JSON feed: https://verifymcp.io/servers/lawatch-dotenv-check/ghcr-io-lawatch-dotenv-check/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/lawatch-dotenv-check/ghcr-io-lawatch-dotenv-check.json
- HTML version of this page: https://verifymcp.io/servers/lawatch-dotenv-check/ghcr-io-lawatch-dotenv-check
