Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words Sign in

Lockbox

by rosostolatoversion 0.1.1i★ 2iRuns on your computerRepository ↗
Registry nameio.github.rosostolato/lockbox-mcp

How to install

What it does

Let your AI agent set up API keys without ever seeing them.

  • Connects Runs on your computer
  • Account or key No key needed
  • Category Other

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity12/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score24/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: 6 (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install Lockbox. Follow https://mcp.popnx.com/i/rosostolato-lockbox-mcp.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Lockbox for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "lockbox": { "command": "npx", "args": [ "-y", "lockbox-mcp", "serve" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Lockbox tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  3. Paste these settings and save the file

    {
      "mcpServers": {
        "lockbox": {
          "command": "npx",
          "args": [
            "-y",
            "lockbox-mcp",
            "serve"
          ]
        }
      }
    }
  4. Quit Claude and open it again

  5. Try it

    Use Lockbox and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Lockbox or shows a Lockbox tool in the answer, you are connected

1 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • LOCKBOX_ENV_ALLOWED_ROOTS Folders that file destinations may write inside. Defaults to the current directory.

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Lockbox yet

Lockbox runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect Lockbox

  • Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time)

B · Others in Other that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Lockbox for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user lockbox -- npx -y lockbox-mcp serve 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Lockbox tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  3. Paste this command and press Enter

    claude mcp add --scope user lockbox -- npx -y lockbox-mcp serve
  4. Type /mcp in Claude Code

    You should see Lockbox listed as connected

  5. Try it

    Use Lockbox and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Lockbox or shows a Lockbox tool in the answer, you are connected

1 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • LOCKBOX_ENV_ALLOWED_ROOTS Folders that file destinations may write inside. Defaults to the current directory.

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Lockbox for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "lockbox": { "command": "npx", "args": [ "-y", "lockbox-mcp", "serve" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Lockbox tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  3. Open the AI chat in Cursor in Agent mode

  4. Try it

    Use Lockbox and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Lockbox or shows a Lockbox tool in the answer, you are connected

1 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • LOCKBOX_ENV_ALLOWED_ROOTS Folders that file destinations may write inside. Defaults to the current directory.

Descriptions are as written by the maker.

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Lockbox for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "lockbox": { "type": "stdio", "command": "npx", "args": [ "-y", "lockbox-mcp", "serve" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Lockbox tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  3. Open the AI chat in VS Code in Agent mode

  4. Try it

    Use Lockbox and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Lockbox or shows a Lockbox tool in the answer, you are connected

1 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • LOCKBOX_ENV_ALLOWED_ROOTS Folders that file destinations may write inside. Defaults to the current directory.

Descriptions are as written by the maker.

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Lockbox💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user lockbox -- npx -y lockbox-mcp serve

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "lockbox": {
      "command": "npx",
      "args": [
        "-y",
        "lockbox-mcp",
        "serve"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "lockbox": {
      "command": "npx",
      "args": [
        "-y",
        "lockbox-mcp",
        "serve"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "lockbox": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "lockbox-mcp",
        "serve"
      ]
    }
  }
}

Values you fill in

  • LOCKBOX_ENV_ALLOWED_ROOTS env
    Folders that file destinations may write inside. Defaults to the current directory.

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
357/wk
Licencei
Apache-2.0
Connection
Runs on your computer
Latest versioni
0.1.1
Categoryi
Other
Published to registryi
Nov 14, 2026
Code last changedi
Nov 14, 2026
Maker
rosostolato
Packages
npm: lockbox-mcp
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 21, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account rosostolato, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 7 days ago

  • ✓ Pass

    Has a licence

    Uses Apache-2.0

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for lockbox-mcp@0.1.1

Checks only this package version, not every dependency · checked Nov 15, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/rosostolato-lockbox-mcp.svg)](https://mcp.popnx.com/en/servers/rosostolato-lockbox-mcp)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Otheri

  • More stars than 91% of the other 21041 servers in this category
  • Published to the registry more recently than 88% of the other 21041 servers in this category
  • Basic checks equal to or better than 99% of the other 21041 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Lockbox safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 7 days ago, and the latest version (0.1.1) reached the registry 7 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

by koala73Widely used★ 91KUpdated 5 days ago

Runs in the cloud✓ service owner · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

by openstatusHQWidely used★ 9.3KUpdated 2 months ago

Runs in the cloud✓ service owner · openstatus.dev

Oh My Posh Validator

Validate oh-my-posh configurations and segment snippets against the official schema.

by JanDeDobbeleerWidely used★ 23.8K Stars for the whole repoUpdated 32 days ago

Runs in the cloud✓ service owner · ohmyposh.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

by Klavis-AIGrowing★ 5.8KUpdated 14 months ago

Runs in the cloudRepo archived✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

by jitsucomWidely used★ 5.1KUpdated 4 months ago

Runs in the cloud✓ service owner · jitsu.com
Compared with similar ones
This one
Lockbox
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks3/34/44/44/41/44/4
LicenseApache-2.0AGPL-3.0AGPL-3.0MITApache-2.0MIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Lockbox

Let your AI agent set up API keys without ever seeing them.

You ask Claude, Cursor or any MCP client to *"put the Stripe key in our .env"* — or in Secret Manager, Vercel, your own API. The agent describes where it goes. You read that in Lockbox's own window and paste the value there. The key goes straight to the destination and never enters the chat, the prompt or the logs.

  1. The agent describes the destination. A file, a program such as gcloud, or an HTTPS request, with {{secret}} where the value goes. The tool has no field that could carry a value.
  2. You check and paste. Lockbox's local window shows where the key goes in one line, warns about anything new or odd, and checks the key's format. The exact request is one click away.
  3. Lockbox sends it. The agent only learns STORED and a reference. It never sees the key.
claude mcp add lockbox -e LOCKBOX_ENV_ALLOWED_ROOTS="$PWD" -- npx -y lockbox-mcp serve

Then ask your agent: *"store my Stripe test key in .env"*.


Install

Lockbox is a stdio MCP server, so you do not run it yourself — your MCP client starts it, the same way it starts any other npm-published server. Requires Node 20+.

Claude Code
cd ~/some/project

claude mcp add lockbox -e LOCKBOX_ENV_ALLOWED_ROOTS="$PWD" -- npx -y lockbox-mcp serve

Add -s project to record it in the repository's .mcp.json instead of your own config.

Any other client (Claude Desktop, Cursor, Windsurf, VS Code, Zed…)

Drop this into the client's MCP configuration — the mcpServers block is the same shape everywhere:

{

"mcpServers": { "lockbox": { "command": "npx", "args": ["-y", "lockbox-mcp", "serve"], "env": { "LOCKBOX_ENV_ALLOWED_ROOTS": "/absolute/path/to/your/project" } } } }

Prefer a pinned install to an ephemeral one:

npm install -g lockbox-mcp

then use lockbox-mcp serve as the command, with no npx

The package is published to npm, unscoped, as lockbox-mcp.

Set `LOCKBOX_ENV_ALLOWED_ROOTS`. File destinations refuse to write outside those directories, and they default only to the server's working directory. Everything else is optional — see Configuration.

Destinations behind a login (Google Secret Manager, Vercel, GitHub) are reached through their own CLI, which uses the login you already have — gcloud, vercel, gh. See Destinations.

First run

Ask your agent for something like *"store my Stripe test key in .env"*. Lockbox opens its window on your machine; the agent does not receive that link. The band at the top tells you the environment at a glance, and the field tells you whether the key looks right before you send it.

Catches the wrong key. A test key headed for production gets flagged in the window. The check runs locally and never shows the value.

Confirms before sending. Nothing is sent until you type where it goes: the host, the program or the file.

Tells the agent only "stored". Lockbox wipes the value and hands back a reference such as the file and variable.

Enter continues and Esc cancels. The link works once: if anything opened it before your browser did, Lockbox shows an alarm and a Cancel button instead of the request. Lockbox's stderr carries structured audit JSON; nothing else is expected of you in the terminal.


What Lockbox solves

It removes an entire class of failures caused by the agent knowing the secret. With Lockbox in the loop, a credential does not pass through:

  • LLM prompts or conversation history
  • MCP tool arguments or tool results
  • agent memory or generated code
  • shell command arguments or process argv
  • logs, debug traces or telemetry
  • URLs
  • model-visible command output

What Lockbox does not solve

Lockbox does not make an AI agent trustworthy, and it is not "safe AI". It does not guarantee that the agent picked the right destination, that it understood you, that it is free of prompt injection, that the destination is itself secure, that your machine is uncompromised, or that a credential cannot be misused later by software that legitimately receives it.

There are two separate problems here:

QuestionLockbox's answer
Should the agent know the secret?No.
Should the agent decide alone where the secret goes?Not without human authorization.

Lockbox answers those two. It does not claim to answer the rest.


Trust model

Trusted with the credential value:

The human at the keyboard Lockbox's secure input UI (loopback only, in your control) Lockbox's secure input broker (this process) The destination you approved (a file, a program, an HTTPS endpoint)

NOT trusted with the credential value:

The LLM The agent / MCP client The conversation The prompt and any repository content it read Generated code Logs, telemetry, crash reports

Lockbox's runtime dependency list is one package (zod, for input validation). The MCP protocol is implemented in-tree rather than through the official SDK, which would add ~90 packages — including HTTP servers and an OAuth stack — to a process that holds plaintext credentials.

This diagram does not claim the trusted components are invulnerable. It says where the credential is *allowed* to exist. Lockbox is security-sensitive software: if Lockbox itself is malicious or compromised, the boundary is gone. Its source, dependencies and releases deserve the scrutiny you would give any credential-handling tool.


The two flows

The secret flow — the human's path, which the model cannot observe:

Human ─▶ Lockbox secure UI (127.0.0.1) ─▶ Broker ─▶ approved definition ─▶ Destination

The agent flow — everything the model sees:

LLM ─▶ MCP client ─▶ Lockbox MCP server ─▶ non-sensitive result metadata

The MCP tool schema has no property capable of carrying a credential. That is structural, not a prompt instruction: there is no value, secret_value, password, token, content or raw_secret field to abuse, closed schemas reject unknown properties, and arguments are screened for credential-shaped values before they are parsed.

What the agent calls
{

"destination": "custom", "name": "STRIPE_SECRET_KEY", "target": { "definition": { "kind": "command", "label": "Google Secret Manager", "executable": "/opt/homebrew/bin/gcloud", "args": ["secrets", "versions", "add", "stripe-secret-key", "--project", "acme-prod", "--data-file=-"], "stdin": "{{secret}}" } }, "environment": "production", "description": "Stripe production API key" }

Lockbox replies with a request_id, a risk classification and the normalized destination — and opens its own authorization window on your machine. The agent polls secret_status. destination: "saved: " reuses a destination the human saved earlier.

The agent does not get the authorization link. That link is a capability: anything holding it can complete the human's half of the flow, and an agent with a shell or an HTTP tool is precisely the threat model. Lockbox hands it straight to your browser. Set LOCKBOX_DISCLOSE_AUTHORIZATION_URL=true if your setup needs the agent to relay the link (for example, a remote or headless session) — and understand that this lets a compromised agent authorize its own request.

The link works once. Opening it trades it for an HttpOnly; SameSite=Lax session cookie scoped to that request and redirects to an address with no token in it; every later page and form needs the cookie. A second opening of the same link gets an alarm page ("This link was already opened") with a Cancel button, never the request. So a copy left in browser history, a process list or a log is dead once you open it, and one used by someone else first is visible to you.

Logs never hold the identity phrase, and hold the link only as a last resort. MCP hosts save server stderr to files any process running as you can read (Claude Desktop under ~/Library/Logs/Claude/, Claude Code under its cache directory), so the audit record carries a short fingerprint of the link instead. The full link is logged only when no browser could be opened (LOCKBOX_OPEN_BROWSER=false, too many windows, or the opener failed), because the operator then has no other way in.

ToolPurpose
secret_storeCreate a credential request. Returns non-sensitive metadata and a request id.
secret_statusPoll a request. Never returns credential material.
secret_cancelCancel a pending request; any entered value is destroyed.
secret_reviseInvalidate an authorization and start a new one. Nothing is edited in place.
secret_destinationsThe definition contract, worked examples, and the user's saved destinations.
What the human sees

Stage A shows the credential name and one destination line — the definition's label and its host, program or file — plus a line for anything worth a second look: a host never used before, a host spelled with non-ASCII characters, an IP address instead of a name, a program outside the system folders, a saved destination that changed. The full request (the URL, every header and the body; or the program, each argument and stdin; or the file and its content) sits behind "See exactly what will be sent", closed by default, with the canonical JSON and its hash. Every custom destination needs a second confirmation in Stage B, after entry and before anything is sent: the human types the host, the program name or the file (.env:API_TOKEN for a variable), and the server checks it. This is an attention check, not authentication: the expected text is on the page. What keeps a second party out of Stage B is the session cookie. The value is never displayed back.

POSTs are refused unless they come from Lockbox's own page (Origin and Sec-Fetch-Site), and every response sets Cross-Origin-Opener-Policy and `Cross-Origin-Reso

Only the beginning is shown; read the rest in the repo