API Key Case
NPM · API-KEY-CASE
Local MCP tools for secret status and guarded deployment. Values never reach the agent.
Available components
Last scanned (19 hours ago)
Scores higher than 65% of npm servers
Category Security
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 Security89
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known medium-severity CVE affects smol-toml 1.8.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 108 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency87
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to melavern/api-key-case). View diagnostics → Pass
- License check failed: the license (Elastic-2.0) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 22 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 351 tokens (~50/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "deploy_secret" implies "deploy" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 7 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
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 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +6
- Stability: unverified → 0.43 ▲ functional
- 11 Oct 26 −3
- GHSA-r4xh-jqrq-34v2 affects this package: medium ▼ security
- Known CVEs: pass → fail ▼ security
- 1 Oct 26 +15
- Malware scan: unverified → pass ▲ security
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 Oct 2026 · Analysed npm/api-key-case@0.9.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | melavern/api-key-case |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/melavern/api-key-case/.github/workflows/publish.yml@refs/tags/v0.9.2 |
| Rekor log index | 3010712375 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:b4338a73b20edbe07b5c76b161f9a911bd943d35186466701403f374e99095197e66704546e5fb8d105cdd072e7ab57afb821ab37598d3fc67f854dd1 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-r4xh-jqrq-34v2 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 108 packages
| Packages resolved | 108 |
|---|---|
| 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 →
check_gitignore ~30
Report whether .env and its variants are covered by .gitignore.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | – |
No output schema declared.
No examples provided.
check_secret ~52
Report whether a named secret is registered in the OS secret store. Returns registered/missing only, never the value.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| path | string | – | – |
| scope | string | – | – |
No output schema declared.
No examples provided.
deploy_secret ~103
Send a registered secret to a deploy target via its official CLI. Production (and github, always CI-reachable) never completes here — returns an action_required response for a human to run the CLI and use its separate Human Plane. Terminal input cannot approve it.
| Name | Type | Req | Description |
|---|---|---|---|
| dryRun | boolean | – | – |
| env | string | – | – |
| name | string | yes | – |
| path | string | – | – |
| scope | string | – | – |
| target | string | yes | – |
No output schema declared.
No examples provided.
generate_env_example ~39
Write or refresh .env.example with empty-valued keys for every required secret.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | – |
| path | string | – | – |
No output schema declared.
No examples provided.
list_required_secrets ~38
List the environment variable names this project needs, from .env.example and source usage. Never returns values.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | – |
No output schema declared.
No examples provided.
save_secret ~49
Never accepts or stores a value. Returns an action_required response for the Agent-independent `api-key-case save --ask` Human Plane.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| scope | string | – | – |
No output schema declared.
No examples provided.
scan_secret_leaks ~40
Scan the project for possible leaked secret values outside ignored env files. Findings are redacted, never the raw value.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | – |
No output schema declared.
No examples provided.
How do I install the API Key Case MCP server?
API Key Case runs locally as an npm package, launched with npx -y api-key-case. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · api-key-case
claude mcp add melavern-api-key-case -- npx -y api-key-case
What is the API Key Case MCP server?
API Key Case is an MCP server listed in the public MCP registry as io.github.melavern/api-key-case. Local MCP tools for secret status and guarded deployment. Values never reach the agent. This page covers its npm package (api-key-case).
Is the API Key Case MCP server safe to use?
API Key Case scores 81 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 22 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 API Key Case MCP server expose?
API Key Case exposes 7 tools: list_required_secrets, check_secret, save_secret, deploy_secret, generate_env_example, and 2 more. Their descriptions and schemas cost roughly 351 tokens of context every time the server is loaded.
Is the API Key Case MCP server still maintained?
API Key Case is still listed as active in the MCP registry. We last reached this channel on 22 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 API Key Case MCP server under?
API Key Case declares the Elastic-2.0 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.