B

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

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.

mcp.nosis-bunker · v1.0.0 · Specialized tools

By Community contributorExternal · opt-inMCP server
Protection rules
0
Permission checks
1
Mapped commands
1

Overview

What this coverage does

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.

Key facts

Catalog ID
mcp.nosis-bunker
Version
v1.0.0
Kind
MCP server
Category
Specialized tools
Protection rules
0
Permission checks
1
Mapped commands
1
Maintainer
Community contributor(community, provenance recorded)
Source commit
5ade44b
Protection model
External · opt-in
External · opt-in

External coverage. It must be enabled through Guard controls; this page does not activate it.

Stated limits

  • 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.

Command mapping

Every command this extension recognizes, with the catalog default floor Guard applies before workspace policy. Search the table, then open an operation for safe variants and the permission ID.

No per-command matchers are published for this listing. Coverage is described by the reviewed rule count, permission checks, and the surrounding Guard policy.

Tool state mapping

ToolGuard state
scan_addressesInherit policy
list_networksInherit policy
otherInherit policy

Runtime identity

Catalog ID
mcp.nosis-bunker
Guard enforcement ID
command.mcp-nosis-bunker
Source path
contributions/mcp-servers/mcp.nosis-bunker.json
Contribution digest
sha256…203dae

Mapped executables

bunker-mcp

Action classes

mcp nosisxhbunker tool

Technical profile

Independent technical profile

Published revision 1
Marketing distribution: off.This profile has no audience, channel, or promotion controls.
Profile content digest
sha256:67e4501079d1bab95aa13731f80b5203443580a2ec89eb2a1507f2bdde3aca1c
Profile source SHA
4acc2c58be767c917e831182245ac4adc565b294
Source version
1.0.0
Native source path
contributions/mcp-servers/mcp.nosis-bunker.json
Native extension ID
mcp.nosis-bunker
Runtime extension ID
command.mcp-nosis-bunker
Contribution digest
sha256:5d5dbb94dd00d4ef79b0697e6f4eab2646d143322f5b5b63a2850d572d203dae
Source contract fingerprint
sha256:df1f30bcd5b5184ffe165cd4473c4a88c45387cece081b083d150c7e3f2e7c3d

Native contribution

Supported by reviewed source projection

Source version

Supported by reviewed source projection

Runtime capability

Supported by reviewed source projection

Permissions

Supported by reviewed source projection

The reviewed catalog declares 1 extension permission(s).

  • scan_addresses: inherit
  • list_networks: inherit
  • other: inherit

Harness support

Unknown / self-reported

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

Unknown / self-reported

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.

Expected outcomes

Unknown / self-reported

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.

Limitations

Supported by reviewed source projection

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.

Residual effects

Unknown / self-reported

Contributor-supplied residual-effect text is not independently verified. Bunker writes no files and keeps no logs, so nothing of yours stays behind. Your MCP client may keep its own chat history, which Bunker does not control.

Release evidence

Unknown / self-reported

Accepted contributors recorded in the reviewed catalog: @arparvar (author).

Controlled fixture proof (separate)

Unknown / self-reported

No controlled fixture proof has been supplied.

Exact installation and activation guide

Commands are copied only when the reviewed source supplies an exact argv contract. Other guidance is labeled unknown and is not executed by this page.

Install

Contributor-reported support

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

Contributor-reported support

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.

Safe fixture inputs

Contributor-reported support

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.

Disable / remove

Contributor-reported support

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.

FAQ

Frequently asked questions

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. The listing declares 0 rules and 1 permission check, with per-tool mapping for 3 tools. No per-command matchers are published for this listing.. Coverage is limited to these reviewed operations and the surrounding Guard policy.

External · opt-in: External coverage. It must be enabled through Guard controls; this page does not activate it. Enabling state is always controlled through Guard policy, never from this directory.

This listing entered the catalog as a community contribution through a public pull request with recorded provenance, with public credit to @arparvar, and 1 GitHub maintainer is recorded on the listing. Credit is attribution only. A verified publisher profile and the claim flow verify authority separately; neither is an upstream endorsement or a HOL safety certification.

No. Every listing documents source, activation model, maintainer identity, and stated limitations so you can evaluate coverage before enabling it. Review the stated limitations and the exact source tree before relying on any single control.

This listing does not publish per-command matchers. Exact behavior follows your Guard policy combined with this entry's 0 rules and 1 permission check.

External coverage. It must be enabled through Guard controls; this page does not activate it. Enablement is managed through your workspace's Guard policy and controls — never from this directory. Open the install guidance for the setup flow, then adjust the MCP coverage for mcp.nosis-bunker in Guard's policy surface.

The matching action is stopped at Guard's pre-action boundary before it executes, and the decision is recorded with evidence your workspace can review. Exact behavior follows your Guard policy combined with this entry's 0 rules and 1 permission check.

No. Guard is local-first: interception, decisions, and evidence stay on your machine unless your workspace explicitly configures cloud features. This page is documentation only — it never executes a command or changes protection state.

Guard runs locally alongside the major AI coding agents and MCP-capable harnesses, so this coverage applies wherever Guard intercepts actions. See the supported harness guides at https://hol.org/guard/harnesses for per-tool approval behavior and limitations.

Guard has a free local tier that includes command interception, evidence, and the policy controls this listing documents. Team plans add shared policy, review queues, and audit surfaces. Current plans: https://hol.org/guard/pricing

Open an issue or pull request against the hol-guard repository, where the canonical catalog lives: https://github.com/hashgraph-online/hol-guard Listings are corrected through the same public review process that adds them.

Yes. Community extensions are merged through public pull requests with recorded provenance, and you can claim the publisher page for a contribution you maintain through the Publisher Studio.

The command mapping table is the audit trail for covered commands and catalog default floors. Pair it with the reviewed rule and permission counts, the per-tool state mapping, and the exact source tree linked from View exact source at the reviewed commit. Guard records enforcement decisions with evidence locally, so what ships matches what you reviewed.