keyblind
- ✓Open-source license (MIT)
- ✓Actively maintained (<30d)
- ✓Documented (README)
git clone https://github.com/aarifmms/keyblind{
"mcpServers": {
"keyblind": {
"command": "node",
"args": ["/path/to/keyblind/dist/index.js"]
}
}
}Resumen de MCP Servers
# Keyblind — Blind AI to Your Keys
**Encrypted secrets vault with MCP for AI agents. One command configures every editor. Secrets resolved at runtime, never leaked to LLM conversations.**
[](https://www.npmjs.com/package/keyblind)
[](LICENSE)
## Why
Developers regularly leak API keys, passwords, and tokens to AI coding tools. 100,000+ LLM conversations with exposed secrets were found indexed by search engines in 2025.
AI agents read your `.env` files. They copy-paste secrets into conversations. They commit them accidentally. Keyblind stops this by keeping secrets encrypted at rest and resolving them _at runtime_ — the plaintext value never touches the LLM transcript.
## How It Works
```
┌──────────┐ ┌────────────────┐ ┌─────────────────┐
│ AI Agent │ ──→ │ Keyblind MCP │ ──→ │ Encrypted │
│ (Claude) │ │ Server │ │ SQLite Vault │
│ │ ←── │ (27 tools) │ ←── │ (AES-256-GCM) │
└──────────┘ └────────────────┘ └─────────────────┘
↑ │
│ secret value never appears │ secrets never
│ in conversation transcript │ stored in plaintext
```
## Quick Start
```bash
# 1. Install
npm i -g keyblind
# 2. One-command setup (initialize vault + configure Claude Code)
keyblind quickstart
# 3. Store secrets
echo "sk-proj-abc123" | keyblind set OPENAI_API_KEY
keyblind set DATABASE_URL - # prompts securely
# 4. Sandbox your .env (AI agents see fakes)
keyblind sandbox
# 5. Resolve a secret
keyblind get OPENAI_API_KEY
# 6. Run commands with secrets injected as env vars
keyblind run -- npm start
# 7. List all secrets (names only, values hidden)
keyblind list
```
> **That's it.** After `keyblind quickstart`, restart Claude Code. Then just say _"list my keyblind secrets"_ or _"use my OPENAI_API_KEY"_ — the AI agent resolves secrets at runtime without ever seeing them in the transcript.
## MCP Server
Keyblind is **MCP-first** — it works with every AI tool that speaks the Model Context Protocol (Claude Code, Cursor, Copilot, Windsurf, Cline, Zed).
### Setup (automatic)
```bash
keyblind setup-mcp
```
This auto-configures Claude Code, Cline, and Zed to use Keyblind. Works from any directory.
For project-local editors (Cursor, Windsurf, Copilot, Cline project mode), run from your project root:
```bash
keyblind setup-mcp --local
```
See [editor-specific configs](docs/editors.md) for details and manual setup.
### Setup (manual)
Add a `.mcp.json` to your project root, or use `claude mcp add`:
```bash
claude mcp add --scope user keyblind -- keyblind start
```
With biometric gate (Touch ID required before secrets are resolved):
```bash
keyblind unlock # Authenticate first
claude mcp add keyblind -- keyblind start --biometric
```
> Session expires after 15 minutes. Requires Pro or Team license.
### MCP Tools
| Tool | Description |
|------|-------------|
| `resolve_secret` | Resolve a secret at runtime (value hidden from transcript) |
| `store_secret` | Encrypt and store a secret |
| `list_secrets` | List secret names (values never revealed) |
| `delete_secret` | Delete a secret |
| `sandbox_env` | Replace `.env` values with deterministic fakes |
| `unsandbox_env` | Restore real `.env` values from vault |
| `audit_log` | View secret resolution audit trail |
| `totp_code` | Generate a TOTP 2FA code for a stored config |
| `totp_store` | Store a TOTP configuration from otpauth:// URI |
| `totp_list` | List all stored TOTP configurations |
| `totp_delete` | Delete a TOTP configuration |
| `create_share_link` | Create encrypted, expiring share link for a secret |
| `receive_share` | Receive and decrypt a shared secret |
| `deadman_status` | Check dead man's switch status |
| `deadman_checkin` | Reset dead man's switch timer |
| `team_init` | Create a shared team vault (encrypted SQLite) |
| `team_push` | Push a local secret to the team vault |
| `team_pull` | Import all secrets from the team vault |
| `team_list` | List secret names in the team vault |
| `team_resolve` | Resolve (decrypt) a secret from the team vault |
| `team_delete` | Delete a secret from the team vault |
| `sso_status` | Check SSO/OIDC authentication status |
| `register_agent` | Register an AI agent bound to a human sponsor |
| `record_action` | Append a signed action to the tamper-proof ledger |
| `verify_ledger` | Verify ledger integrity (hash chain + signatures) |
| `list_agents` | List registered AI agents |
| `export_compliance` | Export the agent ledger as a compliance report |
## Web Dashboard
Manage your secrets from a browser — **no sign-in or pairing required**. Open the local dashboard:
```bash
keyblind dashboard
```
This starts the local server and opens `http://localhost:4318/` in your browser. The dashboard is served same-origin with the REST API, so it works in every browser with no CORS, no pairing token, and no login. Features:
- View, add, copy, and delete secrets
- Audit log with full access history
- License management (tier, email, expiry)
- Pro/Team tier status
- Per-secret access policies and rotation reminders
## Browser Extension
The **Keyblind Chrome Extension** detects and blocks secrets from being pasted into AI chat interfaces (Claude.ai, ChatGPT, Copilot).
[](https://chromewebstore.google.com/detail/keyblind-%E2%80%94-blind-ai-to-yo/ljobkicejnncijfmnkkedpgngbaalnmd)
Features:
- Detects 12+ API key formats (OpenAI, GitHub, Stripe, AWS, etc.)
- Intercepts paste events on AI chat sites
- Warning banner when secrets are detected
- Popup with vault connection status
Located in `browser-extension/`. Load as unpacked extension from `chrome://extensions`.
## Pricing
| | Free | Pro | Team |
|------|------|-----|------|
| **Price** | $0 | $79/year | $29/user/month |
| **Secrets** | 5 | Unlimited | Unlimited |
| **Local vault** | ✓ | ✓ | ✓ |
| **Sandbox / Unsandbox** | ✓ | ✓ | ✓ |
| **MCP server** | ✓ | ✓ | ✓ |
| **Dashboard** | ✓ | ✓ | ✓ |
| **Browser extension** | ✓ | ✓ | ✓ |
| **7 backends** | ✓ | ✓ | ✓ |
| **Team vaults** | — | ✓ | ✓ |
| **Audit log** | — | ✓ | ✓ |
| **Secret sharing** | — | ✓ | ✓ |
| **Dead man's switch** | — | ✓ | ✓ |
| **TOTP 2FA** | — | ✓ | ✓ |
| **Biometric gate** | — | ✓ | ✓ |
| **SSO/OIDC** | — | — | ✓ |
| **CI/CD integration** | — | ✓ | ✓ |
```bash
# Buy a license at keyblind.dev, then activate:
keyblind activate <your-license-key>
# Check your status
keyblind status
```
## Backends
Keyblind supports multiple secret backends:
```bash
keyblind backends # List available backends
keyblind backend 1password # Switch to 1Password
keyblind backend bitwarden # Switch to Bitwarden
```
| Backend | Read | Write | Requires |
|---------|------|-------|----------|
| **local** (default) | ✓ | ✓ | Nothing |
| **1password** | ✓ | ✓ | `op` CLI |
| **bitwarden** | ✓ | — | `bw` CLI |
| **env** | ✓ | — | Nothing |
| **aws** | ✓ | ✓ | `aws` CLI |
| **gcp** | ✓ | ✓ | `gcloud` CLI |
| **azure** | ✓ | ✓ | `az` CLI |
## Keyblind vs Cloak
| | Keyblind | Cloak |
|------|----------|-------|
| **Protocol** | MCP (all editors) | VS Code extension only |
| **Editors** | Claude Code, Cursor, Copilot, Windsurf, Cline, Zed | VS Code, Cursor |
| **Storage** | AES-256-GCM SQLite | AES-256-GCM file |
| **Backends** | Local, 1Password, Bitwarden, Env, AWS, GCP, Azure | Local only |
| **Sandbox** | Deterministic HMAC fakes | AES-256-GCM encrypted |
| **Web dashboard** | ✓ (localhost:4318) | — |
| **Browser extension** | ✓ (Chrome) | — |
| **TOTP 2FA** | ✓ | — |
| **Secret sharing** | ✓ (encrypted URL fragment) | — |
| **Dead man's switch** | ✓ | — |
| **Touch ID** | ✓ (macOS biometric gate) | ✓ |
| **CI/CD** | `keyblind run` for env injection | — |
| **Network** | Zero (fully local) | Zero |
| **License** | MIT | Proprietary |
| **Free tier** | ✓ (5 secrets) | ✓ |
| **Pro** | $79/year (unlimited) | — |
## Security
- **AES-256-GCM** encryption with PBKDF2 key derivation (600K iterations)
- **Machine-identity-bound key** — encryption key XOR-wrapped with machine fingerprint
- **Zero network, zero telemetry** — no cloud, no accounts, no analytics
- **Vault stored at `~/.keyblind/`** with `0700` permissions
- **Deterministic sandbox fakes** using HMAC-SHA256 per project + key name
## Verifying Your Install
Releases are built and published from GitHub Actions with npm provenance, which
attests the tarball was produced from this repository's CI rather than a
developer machine.
```bash
npm audit signatures # Verify npm registry signatures
```
To verify build provenance for a release, open the release page at
https://github.com/aarifmms/keyblind/releases and check the "Provenance" and
"Attestations" sections, which link the tarball to the exact commit and workflow
run that built it.
- **Small dependency graph** — the CLI depends on three packages only (MCP SDK,
better-sqlite3, zod). Server-only deps (Stripe, Resend, the Vercel CLI) live in
the `hosted/` and `dashboard/` packages and are not installed by
`npm i -g keyblind`.
- **No source maps** — the published tarball ships compiled JavaScript with no
embedded original source.
## CLI Reference
```
keyblind quickstart One-command setup (init + configure Claude Code)
keyblind init Initialize the encrypted vault
keyblind set <name> Store a secret (value from stdin)
keyblind set <name> - Store a secret (prompts securely)
keyblind get <name> Resolve and print a secret
keyblind list List all stored secrets
keyblind delete <name> Delete a secret
keyblind setup-mcp Auto-configure MCP for Claude Code, Cline, Zed
keyblLo que la gente pregunta sobre keyblind
¿Qué es aarifmms/keyblind?
+
aarifmms/keyblind es mcp servers para el ecosistema de Claude AI. keyblind Tiene 3 estrellas en GitHub y su última actualización registrada es del 2026-10-21.
¿Cómo se instala keyblind?
+
Puedes instalar keyblind clonando el repositorio (https://github.com/aarifmms/keyblind) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.
¿Es seguro usar aarifmms/keyblind?
+
Nuestro agente de seguridad ha analizado aarifmms/keyblind y le ha asignado un Trust Score de 82/100 (tier: Trusted). Revisa el desglose completo de comprobaciones superadas y flags en esta página.
¿Quién mantiene aarifmms/keyblind?
+
aarifmms/keyblind es mantenido por aarifmms. La última actividad registrada en GitHub es del 2026-10-21, con 1 issues abiertos.
¿Hay alternativas a keyblind?
+
Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.
Despliega keyblind en tu cloud
Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.
¿Mantienes este repo? Añade un badge a tu README
Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.
[](https://claudewave.com/repo/aarifmms-keyblind)<a href="https://claudewave.com/repo/aarifmms-keyblind"><img src="https://claudewave.com/api/badge/aarifmms-keyblind" alt="Featured on ClaudeWave: aarifmms/keyblind" width="320" height="64" /></a>Más MCP Servers
Reverse engineer anything with agents, from app behavior down to native binaries.
Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.
User-friendly AI Interface (Supports Ollama, OpenAI API, ...)
An open-source AI agent that brings the power of Gemini directly into your terminal.
Real-time global intelligence dashboard. AI-powered news aggregation, geopolitical monitoring, and infrastructure tracking in a unified situational awareness interface
🕷️ A Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev