Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

.env checker: dotenv, Node, Vite, Next.js

OCI · GHCR.IO/LAWATCH/DOTENV-CHECK · 2 COMPONENTS

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

41 Trust /100

Last scanned (14 minutes ago)

Scores higher than 37% of OCI servers

Category Developer Tools

Trust breakdown (7 categories)

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 Security0
  • 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.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
Schema Quality & AI Usability62
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 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
  • Structured output schemas are declared (33% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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

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.

What we tested

Checks we ran (12)

  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (4)

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.

  • Malware scan in Supply Chain Security (scores 0 for this)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 in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  • Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
  • Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.

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 →

Changelog

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.

  • 22 Nov 26 +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.

  • 20 Nov 26 +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.

  • 18 Nov 26 +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.

  • 17 Nov 26 38

    First indexed and scored.

Diagnostics

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 22 Nov 2026 · Analysed oci/ghcr.io/lawatch/dotenv-check@1.0.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 3 exposed · ~872 tokens

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 →

Tool Tokens
compare_env_parsers ~111

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.

NameTypeReqDescription
contentstringyesContent of the .env file.

No output schema declared.

No examples provided.

parse_env_file ~141

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.

NameTypeReqDescription
contentstringyesContent of the .env file.
parserstring–Default "dotenv".

No output schema declared.

No examples provided.

resolve_env ~620

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.

NameTypeReqDescription
env_prefixstring|array–vite only: envPrefix from vite.config (default "VITE_").
expandboolean–dotenv only: also run dotenv-expand (expands $VAR and ${VAR:-default}). Default false.
filesobjectyesThe .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…
keysarray–Only report these variables (default: all).
loaderstringyesWho loads the files. dotenv = require("dotenv").config(...); node = node --env-file=...; vite = Vite dev/build; nextjs = next dev/build/start.
modestring–vite: the mode (default "development"; "vite build" uses "production"). nextjs: development (next dev, default), production (next build / next start) or test (NODE_ENV=test).
orderarray–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.
overrideboolean–dotenv only: config({ override: true }). Default false.
process_envobject–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.
NameTypeReqDescription
files_read_in_orderarray––
loaderstring––
modestring––
notesarray––
problemsarrayyes–
variablesobjectyes–

No examples provided.

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.

oci · ghcr.io/lawatch/dotenv-check

# add to Claude Code
claude mcp add lawatch-dotenv-check -- docker run --rm -i ghcr.io/lawatch/dotenv-check:1.0.0
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.