
Keyblind
io.github.aarifmms由 GitHub 帳號 aarifmms 發布v0.8.8更新於 Oct 24, 2026
Encrypted secrets vault for AI agents. 27 MCP tools resolve secrets at runtime, never leaking them.
概覽
本機加密密鑰保險庫,透過 MCP 讓 AI 助理儲存、列出與解析密鑰,而明文不會進入對話紀錄。
- 可以做什麼
- 在本機加密保險庫中儲存、列出、解析與刪除密鑰,值不會進入對話紀錄
- 對 .env 檔案進行沙箱與還原,讓代理只看到確定性的假值
- 檢視稽核日誌、產生 TOTP 驗證碼,建立或接收加密的限時分享連結
- 管理團隊保險庫、註冊代理、記錄簽章動作並匯出合規報告
- 查詢死亡開關狀態與 SSO/OIDC 驗證狀態
- 適用情境
- 適合讓編碼代理在需要 API 密鑰、資料庫連線字串或權杖的專案中工作,並希望這些值在執行時解析,而不是被貼進對話或提交到 .env 檔案。也適合需要稽核紀錄、依密鑰設定原則或代理存取審批的團隊。
- 執行需求
- 以 npm 套件 keyblind 形式透過 stdio 在本機執行,通常用 npx 或 keyblind start 啟動,需先初始化保險庫。未宣告任何帳號、API 密鑰或環境變數。選用的 1Password、Bitwarden、AWS、GCP、Azure 後端需要各自對應的 CLI。團隊保險庫、稽核日誌、分享、TOTP、生物辨識門檻與 SSO 等功能需要付費的 Pro 或 Team 授權。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Keyblind,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
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.
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
Quick Start
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)
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:
See editor-specific configs for details and manual setup.
Setup (manual)
Add a .mcp.json to your project root, or use claude mcp add:
With biometric gate (Touch ID required before secrets are resolved):
Session expires after 15 minutes. Requires Pro or Team license.
MCP Tools
Web Dashboard
Manage your secrets from a browser — no sign-in or pairing required. Open the local 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
- Agent action approvals (approve/deny queued agent writes)
- Central control plane (org-wide visibility + signed revocation)
A hosted control plane (hosted/) adds orgs, roles, groups, a signed
revocation + group-scope manifest, multi-provider SSO login (with org
auto-provisioning, multi-org switching, and IdP end-session revocation), and
short-lived agent credentials. See docs/enterprise.md (Phase 2).
Browser Extension
The Keyblind Chrome Extension detects and blocks secrets from being pasted into AI chat interfaces (Claude.ai, ChatGPT, Copilot).
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
Backends
Keyblind supports multiple secret backends:
Keyblind vs Cloak
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/with0700permissions - 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.
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/anddashboard/packages and are not installed bynpm i -g keyblind. - No source maps — the published tarball ships compiled JavaScript with no embedded original source.
CLI Reference
Development
License
MIT
來源:README.md,提交 6622cbb
工具
0版本歷史
2- v0.8.8最新Oct 21, 2026
- v0.1.4Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分