# keyblind

Blind AI to your keys — encrypted secrets vault with MCP for AI agents

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 0.8.8
- **Author:** Keyblind
- **License:** MIT
- **npm:** keyblind
- **Source:** https://github.com/aarifmms/keyblind
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-22T01:28:11.275Z
- **Version scanned:** 0.8.8
- **CVEs:** none found by OSV at scan time

## Tools

27 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `resolve_secret` — Resolve a secret by name using the configured backend (local vault, 1Password, Bitwarden, or env vars). Returns the decrypted value at runtime. The secret value
- `store_secret` — Store a secret in the encrypted vault. The value is encrypted with AES-256-GCM before storage. The secret value is never visible in the LLM conversation transcr
- `list_secrets` — List all stored secret names (names only — values are never revealed in this listing).
- `sandbox_env` — Replace real values in your .env file with deterministic fake values. Real values are encrypted and backed up to the vault. AI agents reading .env files will on
- `unsandbox_env` — Restore real .env values from the vault. Reverses the sandbox operation.
- `delete_secret` — Delete a secret from the vault.
- `audit_log` — View the audit log of secret resolutions, stores, and deletes. Shows who accessed which secret and when.
- `totp_code` — Generate a TOTP 2FA code for a stored secret. Returns the current 6 or 8 digit code and seconds remaining until rotation.
- `totp_store` — Store a TOTP configuration from an otpauth:// URI (from QR code scan or manual entry).
- `totp_list` — List all stored TOTP configurations.
- `totp_delete` — Delete a stored TOTP configuration.
- `create_share_link` — Create an encrypted, expiring share link for a secret. The secret is encrypted into the URL fragment and never sent to any server.
- `receive_share` — Receive and decrypt a shared secret from a share URL fragment.
- `deadman_status` — Check dead man's switch status — days until vault access is released to designated contacts.
- `deadman_checkin` — Check in to reset the dead man's switch timer.
- `team_init` — Create a new shared team vault (encrypted SQLite). Requires a passphrase.
- `team_push` — Push a local secret to the shared team vault.
- `team_pull` — Import all secrets from the team vault into your local vault.
- `team_list` — List all secret names in the team vault.
- `team_resolve` — Resolve (decrypt) a single secret from the team vault.
- `team_delete` — Delete a secret from the team vault.
- `sso_status` — Check SSO/OIDC authentication status for team vault access.
- `register_agent` — Register an AI agent in the Know Your Agent registry, bound to a human sponsor. Returns the agent identity and its Ed25519 private key, which the agent holds to
- `record_action` — Append a signed action to the tamper-proof agent ledger. Each entry is hash-chained and Ed25519-signed, so any later edit or reorder is detectable.
- `verify_ledger` — Verify the integrity of the agent action ledger by re-walking the hash chain and signatures. Returns the first sequence that fails if the ledger was tampered wi
- `list_agents` — List all agents in the Know Your Agent registry.
- `export_compliance` — Export the agent action ledger as a compliance report (JSON or CSV) with human-sponsor attribution.

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"keyblind\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"keyblind\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Extensive to critical — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: deletes data; runs on your machine.
- Floor 38, ceiling 62 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/keyblind
- Install plan: https://forgeregistry.com/api/v1/packages/keyblind/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/keyblind
- HTML page: https://forgeregistry.com/registry/keyblind
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.