Keysrs MCP server
Commit Nov 7, 2026Provides short-lived, scoped API tokens for AI agents using macOS Keychain and Touch ID for secure credential management.
Also known as gshost1/Keysreallysafe, keysreallysafe
- Stars
- 1
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.16.0
- Last commit
- Nov 7, 2026
- License
- MIT
What is Keysrs MCP?
Keysrs provides short-lived, scoped API tokens for AI agents using macOS Keychain and Touch ID for secure credential management.
Summary generated from the project's README
About Keysrs MCP server
Keysrs provides a secure way for AI agents to access sensitive credentials without exposing actual API keys. Designed for macOS 14+ on Apple Silicon, it stores your real secrets in the macOS Keychain while issuing short-lived, scoped tokens to agents. Users interact with the system through an MCP server that integrates with clients like Claude Desktop, Cursor, and Codex. You manage access using Touch ID to approve specific grants for a single key, host, or time limit.
For developers working with remote environments, the service allows cloud VMs or sandboxes to use tokens instead of raw keys. You can establish a connection via SSH or a self-deployed Cloudflare Worker relay so that requests pass through a local gateway on your Mac. This setup ensures the real key is only swapped in at the gateway level. The tool also includes a command line interface for managing keys, issuing grants, and tracking estimated spend per provider.
What you can do with it
- 1Scan projects for credentialsAsk an AI agent to find potential API keys within your environment files without revealing the actual values.
- 2Securely wrap project keysConvert existing environment variables into 30-day project tokens and move the original secrets into the macOS Keychain.
- 3Grant temporary agent accessProvide an AI agent with a token that is restricted to one specific key and a set duration like 30 minutes.
- 4Connect remote cloud VMsAllow a remote machine to use your local API keys through an SSH tunnel or a custom relay.
Written from the project's README. Every use case is checked against a quote from it.
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablegshost1/keysreallysafe is public and reachablegithub.com/gshost1/keysreallysafe ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-07github.com/gshost1/keysreallysafe ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubKeysrs
Short-lived tokens for AI agents, on your Mac and on cloud VMs. Your real API keys stay in the macOS Keychain; agents get a scoped token instead.
- MCP-first. Agents talk to Keysrs over MCP: they find keys in a project, import them, and ask you for access. You approve each grant with Touch ID.
- Short-lived tokens. A grant covers one key, one host and minutes to hours; a project token lasts 30 days. Revoke everything in one call.
- Cloud VMs too. A VM or sandbox gets a token, never the key. Its calls come back to the gateway on your Mac, over SSH or a relay you deploy yourself, and the real key is swapped in there.
Keysrs also charts the calls made through its gateway: tokens, requests and estimated spend per key and provider.
Free and MIT-licensed. macOS 14+ on Apple Silicon.
Install
Download Keysrs-arm64.dmg from keysrs.com or the
latest release,
drag Keysrs to Applications and open it. It runs in the background (no Dock
icon or window until you open it again) and updates itself.
For the keys command line, choose Install Command Line Tool… in the
Keysrs menu, which links ~/.local/bin/keys.
Use it with your agents
keys setup mcp
This registers the Keysrs MCP server with Claude Code, Codex, Cursor, Droid and Claude Desktop. Restart the agent, then ask it in plain words:
- "Scan this project for API keys with Keysrs." It finds credential-shaped variables in your env files and reports names and last-4 hints, never values.
- "Import and wrap this project's keys." One Touch ID moves the keys into the macOS Keychain and rewrites the env files to a 30-day project token.
- "Ask me for a Keysrs grant for the key anthropic, 30 minutes." You approve with Touch ID; the agent gets a token scoped to one key, one host and a time limit.
- "Revoke everything." Ends every grant, project token and relay pairing at once, and turns the relay off.
keys unwrap puts the original values back.
Cloud VMs
keys gateway on openai # once per key
keys client issue openai --label "my vm" --days 7 # a revocable token for the VM
keys tunnel user@my-vm # VM reaches the gateway over SSH
On the VM, point the agent at http://127.0.0.1:12767/openai and use the
ksfc_… token as its API key. For a sandbox you can't SSH into, keys relay
carries the same gateway through a Cloudflare Worker you deploy into your own
account, and keys share "my box" --key openai hands a machine several keys
at once through it (one token, one pairing, printed as env lines to paste).
See cloud agents and the relay.
From the command line
keys add # guided: provider, name, hidden secret
keys list
keys grant openai --minutes 30 # a scoped token for a script
keys env openai OPENAI_API_KEY -- python run.py
keys spend --week
keys help # every command
Details: the full guide, agents and MCP, cloud agents and the relay.
Privacy
- Everything listens on
127.0.0.1only. The one optional way in from outside is a relay Worker you deploy into your own Cloudflare account, and keys never travel over it. - No tool, log, screen or report ever shows a key value. Copy, reveal, env and rotate ask for Touch ID every time.
- Keysrs counts only the calls made through its own gateway; it reads no
other tool's logs. It never reads
~/.codex/auth.json,~/.grok/auth.json, browser cookies or provider websites. - The app sends no analytics or telemetry.
- Update checks are one cookieless request to GitHub's release API.
Build from source
make build # signed debug CLI at .build/debug/keys
python3 scripts/build-app.py # Keysrs.app from the release build
swift test # offline; CI's env is in test.yml
Signing setup is in SIGNING.md; .github/workflows/test.yml is
the full list of checks CI runs.
Keysrs was called Keysreallysafe; the repository, the Keychain service and the data folder keep that name so existing installs keep working.
License
MIT. See LICENSE and third-party notices.
Keysrs MCP questions
How does Keysrs protect my real API keys?
Your real API keys stay in the macOS Keychain while agents receive scoped, short-lived tokens instead of the actual keys.
Can I use Keysrs with cloud VMs?
Yes, a VM or sandbox can receive a token and communicate with the gateway on your Mac via SSH or a self-deployed relay.
What operating systems are supported?
Keysrs requires macOS 14+ on Apple Silicon.