Guided first use

Try Bunker by NosisTech

Offline, read-only MCP server that classifies public crypto addresses for public-key exposure and returns a step-by-step plan. It never sign Follow the three steps below with your own setup — nothing on this page runs on your machine or changes a policy.

Step 1 · Check fit

What this coverage governs

Offline, read-only MCP server that classifies public crypto addresses for public-key exposure and returns a step-by-step plan. It never signs or submits transactions, and it rejects recognized seed phrase and private key formats. External integration; off until you turn it on.

External — off until you opt in

This coverage stays off until you explicitly enable it from your Guard workspace controls. Reading this page never changes your policy; activation happens in Guard itself.

Harness support

Not documented yet

Contributor-supplied harness support text is not independently verified. Any MCP client that can start a local stdio server, such as Claude Desktop, Claude Code and Cursor. The repo documents these three. Windows, macOS and Linux with Node.js. Docker is also documented on the main branch.

  • Any MCP client that can start a local stdio server, such as Claude Desktop, Claude Code and Cursor. The repo documents these three.
  • Windows, macOS and Linux with Node.js. Docker is also documented on the main branch.

Prerequisites

Not documented yet

Contributor-supplied prerequisite text is not independently verified.

  • Node.js 22.23.4, 24.22.1 or 26.12.1, or a newer release of the same line. Version 24 is the tested one.
  • npm and git, for the global install from GitHub.
  • No accounts, keys or internet access are needed after install.

Known limitations

Reviewed as supported

Limitations are copied from the reviewed catalog facts. Contributor-supplied limitation notes are not independently verified. Coverage limits declared in the reviewed catalog appear automatically when this guide is published.

  • Coverage is limited to the reviewed operations and the surrounding Guard policy.
  • A maintainer profile is not a security certification or an official upstream endorsement.
  • Coverage is limited to the reviewed operations and the surrounding Guard policy.
  • A maintainer profile is not a security certification or an official upstream endorsement.

Catalog version 1.0.0 · source snapshot 5ade44bebc

Step 2 · Set up

Install and activate

Install Guard Open Guard activation

New to Guard? Start with Install Guard. Already installed? Skip install — this coverage stays off until you enable it from your workspace controls.

Activation happens in your Guard workspace. This page links to it; it never enables the coverage for you.

Install

Run npm install -g github:nosistech/nosis-bunker. That puts bunker and bunker-mcp on your PATH. The package is not on the npm registry. From a clone, node mcp/server.js also works.

Activation

Add {"mcpServers": {"bunker": {"command": "bunker-mcp"}}} to your MCP client and restart it. In HOL Guard the coverage is external and opt-in, so it stays off until you turn it on.

Back to fit

Step 3 · Verify the result

Run a safe test and compare

Safe fixture inputs

Ask the agent to call list_networks. Then call scan_addresses with one public address you are happy to check. Never test with a real seed phrase or private key.

Expected outcome

Not documented yet

Contributor-supplied expected-outcome text is not independently verified. list_networks returns the supported networks and exposure models. scan_addresses returns a summary, results per address, and a step-by-step plan. Input that looks like a seed phrase or private key returns an error with the code SECRET_DETECTED. The secret is never repeated.

  • list_networks returns the supported networks and exposure models.
  • scan_addresses returns a summary, results per address, and a step-by-step plan.
  • Input that looks like a seed phrase or private key returns an error with the code SECRET_DETECTED. The secret is never repeated.

Did it work?

Sign in to record an honest self-report. It is stored as your report — never as a verified evaluation.

Sign in to report

Turn it off or recover

Reviewed as supported

Remove the bunker entry from your MCP client config. Turn the coverage off in HOL Guard. Run npm uninstall -g nosis-bunker to remove the commands.

Back to setup
Back to coverage details