Keystash runs on your own machine — the client starts it, so there is no endpoint to ping. 1 697 installs a week from pypi. Last commit 8 Oct 2026.
Keychain-backed secret broker: an AI agent can use your keys, but no tool ever returns one.
We read the source, 3 d ago · rules ccca72095570
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.
subprocess.run(cmd, input=text.encode("utf-8"), check=True)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add keystash -- uvx keystash
{
"mcpServers": {
"keystash": {
"args": [
"keystash"
],
"command": "uvx"
}
}
}
[mcp_servers.keystash]
command = "uvx"
args = ["keystash"]
{
"mcpServers": {
"keystash": {
"args": [
"keystash"
],
"command": "uvx"
}
}
}
{
"mcpServers": {
"keystash": {
"args": [
"keystash"
],
"command": "uvx"
}
}
}
Team secrets your AI agent can use but never read: encrypted in the repo, value-blind tools.
Local encrypted secret broker for AI agents: request keys by name, approve each use over MCP.
Lets an AI agent hand a secret to a person as a one-time link, with no way to read it back.
OS keychain secrets for AI coding agents, over MCP.
AI agents use your Obsidian secrets by name — values never reach their context.
Encrypted store for API keys and database URLs your code needs. Use them without reading them.
Local MCP tools for secret status and guarded deployment. Values never reach the agent.
Find every leaked secret on your machine — API keys in .env files, shell history, and configs.
Answers built from our own checks of this server.