# API Key Case [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/melavern/api-key-case  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/api-key-case

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

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What the API Key Case MCP server does

API Key Case provides local tools for inspecting a project, registering secret names and values, checking status, and preparing guarded deployment. Its scan operation looks for likely secret-handling risks without reading real `.env` contents, and an agent-report mode produces redacted context for coding agents. The system keeps secret values outside the agent-facing results.

Registered values are stored in the operating system secret store when supported. Human-owned terminal flows use hidden prompts, while Agent-first flows request a separate Human Plane interaction. The agent receives names, statuses, readiness information, and operation results, not the secret itself.

Pro deployment can write registered values to Cloudflare, Vercel, or GitHub by using each provider's official CLI. Deployment is separate from local registration and includes provider, destination, host, and project safety checks.

## How it works

The API Key Case MCP server separates agent actions from sensitive human actions. An agent can scan a project, request status, inspect readiness, and retrieve deployment history. When a value must be registered, the agent requests an interactive save operation and the person enters the value in the Human Plane.

The `agent-init` command can add managed instructions for an existing coding-agent setup. It preserves content outside its managed block, checks for unsafe symlinks or junctions, and does not modify global or MCP configuration. `next --json` returns structured actions and closed status values without commands, secret-derived data, or value lengths.

The scanner currently recognizes `.env.example` and common JavaScript or TypeScript references. A name it misses can still be saved or checked directly when the operator knows the secret name.

## Setup and configuration

Node.js 20 or later is required on Windows, macOS, or Linux. Basic commands can be run with `npx`, for example:

```sh
npx -y api-key-case@latest scan .
npx -y api-key-case@latest scan . --agent-report
npx -y api-key-case@latest save OPENAI_API_KEY
npx -y api-key-case@latest check OPENAI_API_KEY
```

For the Agent-first workflow, the README requires verifying the exact `0.9.2` package before using the corresponding commands. Examples include `agent-init .`, `next --json .`, `save NAME --ask`, and `history --json .`.

Windows high-risk approval, removal, and trust-forgetting require Windows 11 build 22000 or later with Windows Hello configured. macOS has implementation and Keychain evidence, but native approval and real-Mac provider deployment remain unverified. Linux supports local diagnosis, status/history, and human-owned-terminal storage when an OS store is available, but not Agent-first input, approval, executing deployment, or approval-required removal.

## Tools and capabilities

The API Key Case MCP server supports these documented operations and workflows:

- Scan a project for likely secret-handling risks.
- Generate redacted agent context.
- Save a named secret through a hidden or Human Plane prompt.
- Check secret status without returning the value.
- Initialize or verify project-specific agent instructions.
- Report structured next actions and setup readiness.
- Review past deployment results without exposing current values.
- Deploy through Cloudflare, Vercel, or GitHub official CLIs when the plan, host, and project conditions allow it.

## Limitations and notes

The API Key Case MCP server does not guarantee complete secret protection, so generated files should be reviewed before sharing. Never place a real secret in a command argument, issue, chat message, or generated report.

Storage does not have a deployment-environment dimension: one project and secret name cannot hold separate development and production values. The tool also does not automatically ingest, delete, synchronize, or replace an existing `.env` file. Cloudflare deployment can stop when Wrangler-related environment files containing potential values are present, even when local registration remains available.

Provider login, key issuance, license activation, and OS verification remain human prerequisites. Deployment rechecks its boundaries, and purchasing Pro does not resolve an unsupported host.

_Full upstream README: https://allmcps.com/mcp/api-key-case/readme_