aarifmms/keyblind
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KEYBLIND_AUTO_INIT | No | true |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| resolve_secretA | 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 is never visible in the LLM conversation transcript — it is resolved just-in-time for the current operation. |
| store_secretA | 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 transcript after this call. |
| list_secretsA | List all stored secret names (names only — values are never revealed in this listing). |
| sandbox_envA | 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 only see fakes. Use unsandbox_env to restore real values. |
| unsandbox_envC | Restore real .env values from the vault. Reverses the sandbox operation. |
| delete_secretC | Delete a secret from the vault. |
| audit_logA | View the audit log of secret resolutions, stores, and deletes. Shows who accessed which secret and when. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: audit logging, listing, storing, deleting, resolving secrets, and sandboxing .env files. No overlap or ambiguity.
All tool names use consistent snake_case and follow a clear verb_noun pattern (e.g., list_secrets, store_secret, resolve_secret).
7 tools is well-scoped for a secret management server, covering CRUD, audit, and sandbox operations without being excessive.
Covers core secret lifecycle (create, read, list, delete) and audit, but lacks an explicit update tool; users must delete and recreate.