# io.github.irrenwill/secret-safe-env (npm · secret-safe-env)

Write secrets into .env without the agent ever seeing the value - Windows masked dialog (繁中 UI)

- Trust score: 68/100 (medium)
- Change this week: +25
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `secret-safe-env`: 68/100 (this document), [markdown](https://verifymcp.io/servers/irrenwill-secret-safe-env/secret-safe-env.md), [page](https://verifymcp.io/servers/irrenwill-secret-safe-env/secret-safe-env)

## Channel facts

- Registry: `npm`
- Package: `secret-safe-env`
- Version: `0.1.2`
- 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-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
- **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 57 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 503 tokens (~251/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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 (50% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add irrenwill-secret-safe-env -- npx -y secret-safe-env
```

### Codex

```bash
codex mcp add irrenwill-secret-safe-env -- npx -y secret-safe-env
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "irrenwill-secret-safe-env": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "secret-safe-env"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add irrenwill-secret-safe-env --command npx --arg -y --arg secret-safe-env
```

### Hermes

```yaml
mcp_servers:
  irrenwill-secret-safe-env:
    command: "npx"
    args: ["-y", "secret-safe-env"]
```

### Other

```json
{
  "mcpServers": {
    "irrenwill-secret-safe-env": {
      "command": "npx",
      "args": [
        "-y",
        "secret-safe-env"
      ]
    }
  }
}
```

## 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-08-03 (score 68, +1)

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

### 2026-08-02 (score 67, +48)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.23
- [functional improvement] License: unverified → pass
- [functional] First check of Schema quality: unverified
- [functional] Licence: MIT

### 2026-07-31 (score 19, −24)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-27 (score 43)

First indexed and scored.

## MCP tools (2)

### `set_env_secret` (~249 tokens)

Set an .env secret (value never seen by the agent)

Use this WHENEVER a task needs a secret/API key/token/password/connection string/credential written to a project .env file - e.g. "add my OpenAI key", "set DATABASE_URL", "configure my .env", "save this API token". You pass ONLY the variable NAME; the user types the value into a local masked dialog and it is written straight to .env - you never see or handle the value. DO NOT ask the user to paste the secret into the chat; DO NOT write the value or a placeholder yourself; DO NOT cat/read .env to verify (use env_key_exists). The value must be single-line (not for multi-line PEM keys / JSON blobs - for those, tell the user to edit .env manually).

Input parameters:

- `env_path` (string): Absolute path to the project .env. Pass the project-root .env path explicitly; if omitted it defaults to <CLAUDE_PROJECT_DIR or cwd>/.env, which may NOT be your workspace when launched via a runner.
- `key` (string, required): The env var NAME in UPPER_SNAKE_CASE, e.g. OPENAI_API_KEY, DATABASE_URL, STRIPE_SECRET_KEY.

### `env_key_exists` (~116 tokens)

Check if a key exists in .env

Check whether an environment variable NAME already exists in a project .env file. Returns ONLY true/false - never the value. Use this to verify set_env_secret worked, INSTEAD of reading/cat-ing .env (which would expose the secret).

Input parameters:

- `env_path` (string): Absolute path to the project .env (same as set_env_secret). Defaults to <CLAUDE_PROJECT_DIR or cwd>/.env.
- `key` (string, required): The env var NAME to check, e.g. OPENAI_API_KEY.

Output parameters:

- `exists` (boolean)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/irrenwill-secret-safe-env/secret-safe-env#diagnostics

## Score history

- 2026-08-03: 68
- 2026-08-02: 67
- 2026-08-01: 19
- 2026-07-31: 19
- 2026-07-30: 43
- 2026-07-28: 43
- 2026-07-27: 43

## Links

- npm package: https://www.npmjs.com/package/secret-safe-env
- Socket report: https://socket.dev/npm/package/secret-safe-env
- Repository: https://github.com/irrenwill/secret-safe-env
- Changelog RSS feed: https://verifymcp.io/servers/irrenwill-secret-safe-env/secret-safe-env/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/irrenwill-secret-safe-env/secret-safe-env/changelog.json
- HTML version of this page: https://verifymcp.io/servers/irrenwill-secret-safe-env/secret-safe-env