Secret Handoff runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 22 Oct 2026.
Let agents use temporary secrets without receiving their values in chat. Local stdio; Node 22+.
What the code does
We read the source, 2 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.
const child = spawn(binary, ['mcp'], { stdio: 'inherit', shell: false });
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 Secret Handoff
same job, measured the same wayLet AI agents use secrets without seeing them: inject into a command, redact the output.
Let AI agents use secrets without seeing them: masked output, every use approved in JFSecure.
Count secret-like patterns in bounded local files without returning values, keys, paths,...
Save and use 1Password secrets locally without exposing plaintext to AI agents.
Write secrets into .env without the agent ever seeing the value - Windows masked dialog (繁中 UI)
Secrets for developers and agents—secure context and workflows without exposing secret values.
Encrypted store for API keys and database URLs your code needs. Use them without reading them.
AI agents use your Obsidian secrets by name — values never reach their context.
Secret Handoff — questions
Answers built from our own checks of this server.