unseenkey
Related Servers
Alternatives to unseenkey
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to call APIs without holding credentials by injecting keys locally, enforcing allow/deny/ask policies, holding risky calls for human approval, and recording requests.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to securely use API keys by storing them in an encrypted vault and injecting them on demand with user approval, without exposing the key values to the model.3MIT
- FlicenseNot gradedqualityDmaintenanceLocal encrypted vault for API keys. LLMs never see your real keys — the server injects them transparently into HTTP requests.-
- AlicenseAqualityBmaintenanceEnables AI agents to stage API keys into non-exposing handles and make API calls where the real key is injected locally, so secrets stay out of prompts, transcripts, tool arguments, and logs. Also allows listing handles, revoking secrets, and inspecting vault info without ever returning raw secret values.51MIT No Attribution
- AlicenseAqualityBmaintenanceLocal credential broker for AI agents: they call HTTP APIs, SSH, SFTP and databases through allow-listed presets while secrets stay in the OS keychain. Per-preset approval (desktop, terminal or Telegram) and an append-only audit log.714Apache 2.0
- AlicenseNot gradedqualityBmaintenanceLets AI agents make authenticated API and OAuth calls using stored credentials they never see, with per-credential Touch ID approval, proxy execution, and a local audit log of every use.1Apache 2.0
TDQS
Scored across 4 tools
Each tool has a clearly distinct role: discovery, credential-backed API calls, access escalation, and policy explanation. list_secrets and explain_policy both touch policy, but one enumerates usable secrets while the other explains constraints, so they are not easily confused.
All tools use consistent snake_case and follow a predictable verb_noun pattern: list_secrets, call_api, request_access, explain_policy. The naming is uniform and easy to scan.
Four tools is well-scoped for a secret broker: discover secrets, use them, request additional access, and understand policy. Each tool earns its place without redundant operations.
The agent-facing lifecycle is well covered: listing secrets, calling APIs, escalating access, and explaining policy. Minor gaps exist around secret administration or revocation, but those may intentionally be owner-managed rather than agent-facing.