unseenkey
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Unseenkey lets you use the owner's API keys without ever seeing them. Secret values are never returned by any tool and cannot be obtained; do not try. To call an API, use call_api with the secret's name. If a call is denied by policy, use request_access to ask the owner, explaining why. Never ask the user to paste a key into the chat; ask them to run usk add <name> instead. Unseenkey is not set up on this computer. Ask the user to install it (https://unseenkey.com) and run usk init, then try again.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_secretsA | List the secrets you may use, with their provider and the policy that applies to you. Never returns values. |
| call_apiA | Call a provider API using a stored secret by name. The broker injects the real credential; you only see the (scrubbed) response. Paths are relative to the provider, e.g. secret="stripe-live", method="GET", path="/v1/customers?limit=3". For generic secrets and providers that span many hosts (AWS: upstream="https://s3.eu-west-1.amazonaws.com") pass upstream="https://host". |
| request_accessA | Ask the owner to approve a request that policy gates behind approval (for example POST /v1/refunds), or to allow a host the secret is not yet locked to (pass upstream). Waits briefly for a decision. If the policy denies the path outright, the owner must change the policy; this tool will say so. |
| explain_policyC | Plain-English description of what you may do with a secret. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| setup-project | Replace real keys in this project's .env with Unseenkey handles |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Provider presets | Providers and their ready-made policies |
| Recent audit events | Your last 50 broker events |
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.