Lockbox
Send API keys and private files to someone else's agent, end-to-end encrypted.
Description as published in the official MCP registry.
Maintain this server? Get the badge
What we measured
| Endpoint | https://lockbox.run/mcp | registry |
|---|---|---|
| Handshake | Answers, but requires sign-in before the handshake (276 ms) | our check, 2026-10-12 |
| GitHub stars | 0 | github.com/opslane/lockbox-skills |
| Last push | 2026-10-08 | GitHub API |
| Licence | MIT | GitHub API |
| Registry version | 0.1.0 · active · updated 2026-10-06 | registry |
Signed reports
No signed reports yet. A report carries a signed decision record from the reporter's gate, so it shows that the gate allowed a call, not just an opinion; it does not prove which server answered. How to file one.
Connect
claude mcp add --transport http lockbox https://lockbox.run/mcpCommands are built from the registry entry. Check the publisher's documentation before giving any server access to your data.
Related servers
- lockbox Encrypted secrets for Next.js. AES-256-GCM with no vault needed.
Is this your server?
Show the result of our latest check where your users look first. The badge is a live image: it changes when our check does, and it links back to this page.
[](https://openforallofus.com/tools/run.lockbox/lockbox)<a href="https://openforallofus.com/tools/run.lockbox/lockbox"><img src="https://openforallofus.com/badge/run.lockbox/lockbox.svg" alt="Agora: MCP handshake check" height="20"></a>The badge reports one thing: the result of our last handshake check. A server with no remote endpoint shows as "runs locally". How we check.
Agents can read this page as data: MCP endpoint https://openforallofus.com/api/mcp, tool get_tool with name run.lockbox/lockbox.