.env checker: dotenv, Node, Vite, Next.js
MCPB · DOTENV-CHECK-1.0.0.MCPB · 2 COMPONENTS
Real value of each .env variable and the file:line that decides, for dotenv, node, Vite, Next.js
Available components
Last scanned (19 hours ago)
Scores higher than 71% of MCPB 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 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: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
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 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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: 2 categories
Categories scored 0 because we could not verify them: 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.
Checks we ran (11)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (5)
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: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- 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: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
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.
- 17 Nov 26 38
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 21 Nov 2026 · Analysed mcpb/https://github.com/Lawatch/10aday/releases/download/dotenv-check-v1.0.0/dotenv-check-1.0.0.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
compare_env_parsers Does this .env read the same with dotenv and with Node / Vite 8? ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Content of the .env file. |
No output schema declared.
No examples provided.
parse_env_file Parse one .env file exactly, line by line ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Content of the .env file. |
| parser | string | – | Default "dotenv". |
No output schema declared.
No examples provided.
resolve_env What value does each .env variable really get? ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| files_read_in_order | array | – | – |
| loader | string | – | – |
| mode | string | – | – |
| notes | array | – | – |
| problems | array | yes | – |
| variables | object | yes | – |
No examples provided.
How do I install the .env checker: dotenv, Node, Vite, Next.js MCP server?
.env checker: dotenv, Node, Vite, Next.js ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 855457613dd2db02aa41e2d319753cf01eadaa4e4465d33f0bf05733aab796f7; the commands to do that are on this page. If it does not match, do not open it.
mcpb · dotenv-check-1.0.0.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
855457613dd2db02aa41e2d319753cf01eadaa4e4465d33f0bf05733aab796f7
macOS / Linux
echo "855457613dd2db02aa41e2d319753cf01eadaa4e4465d33f0bf05733aab796f7 dotenv-check-1.0.0.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\dotenv-check-1.0.0.mcpb).Hash -eq "855457613dd2db02aa41e2d319753cf01eadaa4e4465d33f0bf05733aab796f7"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
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 MCPB bundle (https://github.com/Lawatch/10aday/releases/download/dotenv-check-v1.0.0/dotenv-check-1.0.0.mcpb).
Is the .env checker: dotenv, Node, Vite, Next.js MCP server safe to use?
.env checker: dotenv, Node, Vite, Next.js scores 38 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.
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 11 checks on .env checker: dotenv, Node, Vite, Next.js, covering Source repository, Provenance, License, Maintenance and 7 more. 5 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, Dependency health and 1 more. 2 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.