Keysrs runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 7 Nov 2026.
Local Mac API-key vault: Touch ID-approved, scoped grants for agents, not keys. Needs Keysrs.app.
What the code does
We read the source, 21 h ago · rules 995398eba69f
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
rm -rf "$2" || true
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
.appendingPathComponent("Library/LaunchAgents/\(label).plist")
subprocess.run(['node', '-e', script, str(ROOT)], cwd=REPO/'scripts/tests', check=True)
var attributes: posix_spawnattr_t?
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found things in this code
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Keysrs and you get told the day something new turns up.
Alternatives to Keysrs
same job, measured the same wayLocal AES-256-GCM vault for AI agents. Secrets stay local, LLMs never see real API keys.
ProphetKey MCP bridge - encrypted local-first API key vault for AI agents, keys never exposed
Persistent knowledge-graph memory for AI agents, with local semantic search. No API keys.
Typed answers with calibrated confidence for agents. Local-first, no API key.
Personal memory for AI agents from a vault on your Mac, with per-agent scopes and approvals
Local, stateful twins of any API (Stripe, Twilio, any OpenAPI spec) for agents. No keys, no bill.
Local encrypted secret broker for AI agents: request keys by name, approve each use over MCP.
Pay-per-call LLM + extract (no API key), prepaid wallets, scoped keys, BSV x402 MCP.
Keysrs — questions
Answers built from our own checks of this server.