io.github.irrenwill/secret-safe-env
NPM · SECRET-SAFE-ENV · SCANNED OCT 1
Write secrets into .env without the agent ever seeing the value - Windows masked dialog (繁中 UI)
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
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 116 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 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 (50% 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
How do I install the io.github.irrenwill/secret-safe-env MCP server?
io.github.irrenwill/secret-safe-env runs locally as an npm package, launched with npx -y secret-safe-env. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · secret-safe-env
claude mcp add irrenwill-secret-safe-env -- npx -y secret-safe-env
{
"mcpServers": {
"irrenwill-secret-safe-env": {
"command": "npx",
"args": [
"-y",
"secret-safe-env"
]
}
}
} {
"servers": {
"irrenwill-secret-safe-env": {
"command": "npx",
"args": [
"-y",
"secret-safe-env"
]
}
}
} codex mcp add irrenwill-secret-safe-env -- npx -y secret-safe-env
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"irrenwill-secret-safe-env": {
"type": "local",
"command": [
"npx",
"-y",
"secret-safe-env"
],
"enabled": true
}
}
} openclaw mcp add irrenwill-secret-safe-env --command npx --arg -y --arg secret-safe-env
mcp_servers:
irrenwill-secret-safe-env:
command: "npx"
args: ["-y", "secret-safe-env"] {
"McpServers": {
"irrenwill-secret-safe-env": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"secret-safe-env"
]
}
}
} assistant mcp add irrenwill-secret-safe-env -t stdio -c npx -a -y secret-safe-env
{
"mcpServers": {
"irrenwill-secret-safe-env": {
"command": "npx",
"args": [
"-y",
"secret-safe-env"
]
}
}
} 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.
- 30 Sept 26 −3
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.80 functional
- 29 Sept 26 +1
- Stability: 0.97 → pass security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 22 Sept 26 −3
- Stability: pass → 0.77 functional
- 21 Sept 26 +1
- Stability: 0.97 → pass security
- 20 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
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 1 Oct 2026 · Analysed npm/secret-safe-env@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
env_key_exists Check if a key exists in .env ~116
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).
| Name | Type | Req | Description |
|---|---|---|---|
| env_path | string | – | Absolute path to the project .env (same as set_env_secret). Defaults to <CLAUDE_PROJECT_DIR or cwd>/.env. |
| key | string | yes | The env var NAME to check, e.g. OPENAI_API_KEY. |
| Name | Type | Req | Description |
|---|---|---|---|
| exists | boolean | yes | – |
No examples provided.
set_env_secret Set an .env secret (value never seen by the agent) ~249
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The env var NAME in UPPER_SNAKE_CASE, e.g. OPENAI_API_KEY, DATABASE_URL, STRIPE_SECRET_KEY. |
No output schema declared.
No examples provided.
What is the io.github.irrenwill/secret-safe-env MCP server?
io.github.irrenwill/secret-safe-env is an MCP server listed in the public MCP registry as io.github.irrenwill/secret-safe-env. Write secrets into .env without the agent ever seeing the value - Windows masked dialog (繁中 UI). This page covers its npm package (secret-safe-env).
Is the io.github.irrenwill/secret-safe-env MCP server safe to use?
io.github.irrenwill/secret-safe-env scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 1 October 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 io.github.irrenwill/secret-safe-env MCP server expose?
io.github.irrenwill/secret-safe-env exposes 2 tools: set_env_secret, env_key_exists. Their descriptions and schemas cost roughly 365 tokens of context every time the server is loaded.
Is the io.github.irrenwill/secret-safe-env MCP server still maintained?
io.github.irrenwill/secret-safe-env is still listed as active in the MCP registry. We last reached this channel on 1 October 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 io.github.irrenwill/secret-safe-env MCP server under?
io.github.irrenwill/secret-safe-env declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.