# API Key Case (npm · api-key-case)

Local MCP tools for secret status and guarded deployment. Values never reach the agent.

- Trust score: 81/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-22

## Components

- npm · `api-key-case`: 81/100 (this document), [markdown](https://verifymcp.io/servers/melavern-api-key-case/api-key-case.md), [page](https://verifymcp.io/servers/melavern-api-key-case/api-key-case)

## Channel facts

- Registry: `npm`
- Package: `api-key-case`
- Version: `0.9.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-10-22.

- **Supply Chain Security**: 89/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known medium-severity CVE affects smol-toml 1.8.0, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 31 of 108 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 87/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to melavern/api-key-case).
  - License check failed: the license (Elastic-2.0) isn't a recognized OSI-approved license.
  - Actively maintained (last published 22 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 351 tokens (~50/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 7 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 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.

### Claude

```bash
claude mcp add melavern-api-key-case -- npx -y api-key-case
```

### Cursor

```json
{
  "mcpServers": {
    "melavern-api-key-case": {
      "command": "npx",
      "args": [
        "-y",
        "api-key-case"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "melavern-api-key-case": {
      "command": "npx",
      "args": [
        "-y",
        "api-key-case"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add melavern-api-key-case -- npx -y api-key-case
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "melavern-api-key-case": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "api-key-case"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add melavern-api-key-case --command npx --arg -y --arg api-key-case
```

### Hermes

```yaml
mcp_servers:
  melavern-api-key-case:
    command: "npx"
    args: ["-y", "api-key-case"]
```

### Netclaw

```json
{
  "McpServers": {
    "melavern-api-key-case": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "api-key-case"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add melavern-api-key-case -t stdio -c npx -a -y api-key-case
```

### Other

```json
{
  "mcpServers": {
    "melavern-api-key-case": {
      "command": "npx",
      "args": [
        "-y",
        "api-key-case"
      ]
    }
  }
}
```

## 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-10-22 (score 81, +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.

### 2026-10-20 (score 80, +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.

### 2026-10-18 (score 79, +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.

### 2026-10-16 (score 78, +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.

### 2026-10-14 (score 77, +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.

### 2026-10-13 (score 76, +6)

- [functional improvement] Stability: unverified → 0.43

### 2026-10-11 (score 70, −3)

- [security regression] GHSA-r4xh-jqrq-34v2 affects this package: medium
- [security regression] Known CVEs: pass → fail

### 2026-10-01 (score 73, +15)

- [security improvement] Malware scan: unverified → pass

## MCP tools (7)

### `list_required_secrets` (~38 tokens)

List the environment variable names this project needs, from .env.example and source usage. Never returns values.

Input parameters:

- `path` (string)

### `check_secret` (~52 tokens)

Report whether a named secret is registered in the OS secret store. Returns registered/missing only, never the value.

Input parameters:

- `name` (string, required)
- `path` (string)
- `scope` (string)

### `save_secret` (~49 tokens)

Never accepts or stores a value. Returns an action_required response for the Agent-independent `api-key-case save --ask` Human Plane.

Input parameters:

- `name` (string, required)
- `scope` (string)

### `deploy_secret` (~103 tokens)

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.

Input parameters:

- `dryRun` (boolean)
- `env` (string)
- `name` (string, required)
- `path` (string)
- `scope` (string)
- `target` (string, required)

### `generate_env_example` (~39 tokens)

Write or refresh .env.example with empty-valued keys for every required secret.

Input parameters:

- `force` (boolean)
- `path` (string)

### `scan_secret_leaks` (~40 tokens)

Scan the project for possible leaked secret values outside ignored env files. Findings are redacted, never the raw value.

Input parameters:

- `path` (string)

### `check_gitignore` (~30 tokens)

Report whether .env and its variants are covered by .gitignore.

Input parameters:

- `path` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/melavern-api-key-case/api-key-case#diagnostics

## Score history

- 2026-10-22: 81
- 2026-10-21: 80
- 2026-10-20: 80
- 2026-10-19: 79
- 2026-10-18: 79
- 2026-10-17: 78
- 2026-10-16: 78
- 2026-10-15: 77
- 2026-10-14: 77
- 2026-10-13: 76
- 2026-10-12: 70
- 2026-10-11: 70
- 2026-10-04: 73
- 2026-10-03: 73
- 2026-10-02: 73
- 2026-10-01: 73
- 2026-09-30: 58

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/api-key-case
- Socket report: https://socket.dev/npm/package/api-key-case
- Repository: https://github.com/melavern/api-key-case
- Website: https://apikeycase.melavern.com/
- Changelog RSS feed: https://verifymcp.io/servers/melavern-api-key-case/api-key-case.xml
- Changelog JSON feed: https://verifymcp.io/servers/melavern-api-key-case/api-key-case.json
- HTML version of this page: https://verifymcp.io/servers/melavern-api-key-case/api-key-case