Clipboard History MCP runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 2 Aug 2026.
Your clipboard, but Claude can read it. Type-classified, secret-encrypted. macOS + Linux.
What the code does
We read the source, 4 d ago · rules 995398eba69f
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.
std::path::PathBuf::from(&home).join(format!("Library/LaunchAgents/{}.plist", LABEL));
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
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.
Alternatives to Clipboard History MCP
same job, measured the same wayTeam secrets your AI agent can use but never read: encrypted in the repo, value-blind tools.
Find every leaked secret on your machine — API keys in .env files, shell history, and configs.
Encrypted store for API keys and database URLs your code needs. Use them without reading them.
MCP server for creating and managing SOPS-encrypted secrets
Send and read one-time encrypted secrets with local encryption.
Local secret & credential checks for AI-assisted dev — runs on your machine, results redacted.
Local encrypted secret broker for AI agents: request keys by name, approve each use over MCP.
One searchable history across every AI coding tool, with secret scanning and a shared task board.
Clipboard History MCP — questions
Answers built from our own checks of this server.