# EnvSync-LE (npm · envsync-le-mcp)

Compare dotenv files and report which keys are missing or extra, by name only.

- Trust score: 83/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-22

## Components

- npm · `envsync-le-mcp`: 83/100 (this document), [markdown](https://verifymcp.io/servers/nolindnaidoo-envsync-le/envsync-le-mcp.md), [page](https://verifymcp.io/servers/nolindnaidoo-envsync-le/envsync-le-mcp)

## Channel facts

- Registry: `npm`
- Package: `envsync-le-mcp`
- Version: `2.2.5`
- 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-09-22.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **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 38 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 196 tokens (~196/item across 1 items; 1 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 83/100
  - Stability observed for 25 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 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.

## Install

### How do I install the EnvSync-LE MCP server?

EnvSync-LE runs locally as an npm package, launched with npx -y envsync-le-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add nolindnaidoo-envsync-le -- npx -y envsync-le-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "nolindnaidoo-envsync-le": {
      "command": "npx",
      "args": [
        "-y",
        "envsync-le-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "nolindnaidoo-envsync-le": {
      "command": "npx",
      "args": [
        "-y",
        "envsync-le-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add nolindnaidoo-envsync-le -- npx -y envsync-le-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nolindnaidoo-envsync-le": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "envsync-le-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add nolindnaidoo-envsync-le --command npx --arg -y --arg envsync-le-mcp
```

### Hermes

```yaml
mcp_servers:
  nolindnaidoo-envsync-le:
    command: "npx"
    args: ["-y", "envsync-le-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "nolindnaidoo-envsync-le": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "envsync-le-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add nolindnaidoo-envsync-le -t stdio -c npx -a -y envsync-le-mcp
```

### Other

```json
{
  "mcpServers": {
    "nolindnaidoo-envsync-le": {
      "command": "npx",
      "args": [
        "-y",
        "envsync-le-mcp"
      ]
    }
  }
}
```

## 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-09-21 (score 83, −2)

- [functional] Stability: pass → 0.80

### 2026-09-20 (score 85, 0)

- [security] Stability: 0.97 → pass

### 2026-09-19 (score 85, +1)

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

### 2026-09-16 (score 84, +1)

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

### 2026-09-14 (score 83, −2)

- [functional] Stability: pass → 0.80

### 2026-09-13 (score 85, 0)

- [security] Stability: 0.97 → pass

### 2026-09-12 (score 85, +1)

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

### 2026-09-09 (score 84, +1)

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

## MCP tools (1)

### `compare_env_files` (~196 tokens)

Compare dotenv files and report which keys are missing from which file, and which are extra relative to a template. Takes file contents directly. Only key NAMES are returned — never values — because a dotenv file is where credentials live and the answer does not need them. In "auto" mode the reference is the union of all keys, so nothing can be extra; "template" mode compares every file against one named template.

Input parameters:

- `caseSensitive` (boolean): Whether key names are compared case-sensitively.
- `files` (array, required): The dotenv files to compare.
- `maxResults` (integer): Cap on returned key mismatches (default 500). meta.truncated reports whether any were dropped.
- `mode` (string): "auto" compares against the union of all keys; "template" compares against one file.
- `templatePath` (string): Which file is the template. Required when mode is "template".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/nolindnaidoo-envsync-le/envsync-le-mcp#diagnostics

## Score history

- 2026-09-22: 83
- 2026-09-21: 83
- 2026-09-20: 85
- 2026-09-19: 85
- 2026-09-18: 84
- 2026-09-17: 84
- 2026-09-16: 84
- 2026-09-15: 83
- 2026-09-14: 83
- 2026-09-13: 85
- 2026-09-12: 85
- 2026-09-11: 84
- 2026-09-10: 84
- 2026-09-09: 84
- 2026-09-08: 83
- 2026-09-07: 85
- 2026-09-06: 85
- 2026-09-05: 85
- 2026-09-04: 85
- 2026-09-03: 84
- 2026-09-02: 84
- 2026-09-01: 84
- 2026-08-31: 83
- 2026-08-30: 83
- 2026-08-29: 82
- 2026-08-28: 82
- 2026-08-27: 81
- 2026-08-26: 81
- 2026-08-25: 79
- 2026-08-24: 79

## Common questions

### What is the EnvSync-LE MCP server?

EnvSync-LE is an MCP server listed in the public MCP registry as io.github.nolindnaidoo/envsync-le. Compare dotenv files and report which keys are missing or extra, by name only. This page covers its npm package (envsync-le-mcp).

### Is the EnvSync-LE MCP server safe to use?

EnvSync-LE scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 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 EnvSync-LE MCP server expose?

EnvSync-LE exposes 1 tool: compare_env_files. Their descriptions and schemas cost roughly 196 tokens of context every time the server is loaded.

### Is the EnvSync-LE MCP server still maintained?

EnvSync-LE is still listed as active in the MCP registry. We last reached this channel on 22 September 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 EnvSync-LE MCP server under?

EnvSync-LE declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/envsync-le-mcp
- Socket report: https://socket.dev/npm/package/envsync-le-mcp
- Repository: https://github.com/nolindnaidoo/envsync-le
- Website: https://letools.dev/tools/envsync-le
- Changelog RSS feed: https://verifymcp.io/servers/nolindnaidoo-envsync-le/envsync-le-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/nolindnaidoo-envsync-le/envsync-le-mcp.json
- HTML version of this page: https://verifymcp.io/servers/nolindnaidoo-envsync-le/envsync-le-mcp