
Offline scanner that shows which of your crypto addresses expose their public key, with a calm plan
Offline scanner that shows which of your crypto addresses expose their public key, with a calm plan to hide what you can. 100+ networks. Sends nothing.
·
Bunker is an offline scanner for crypto addresses. You paste your addresses. The tool shows which addresses show their public key to the world. Then it gives you a calm plan, step by step, to hide what you can.
The tool runs only on your device. It does not connect to a wallet. It does not send or store anything. It knows more than 100 networks. It works in English and Spanish, for people and for AI agents.
Safety first. Bunker needs only your public addresses. Do not paste a seed phrase or a private key into this tool or into any other website. The tool blocks secrets if you paste them by mistake.
I see AI advancing at an alarming rate. AI models now solve math problems that stayed open for decades. The signatures that protect most crypto wallets depend on math problems that nobody has solved yet. Nobody has broken them today. But I do not want to wait for the day that someone does. Crypto needs extra security now.
The first step is simple: keep your funds on addresses whose public key the world has never seen. Most people do not know which of their addresses show the public key. Bunker gives that answer in about 30 seconds, with a plan to fix what you can.
Carlos A. Paredes Vargas, founder of NosisTech
Read docs/01-background.md for the full story.
You do not need to install anything.
Open https://bunker.nosistech.com, or use the file on your own computer:
dist/nosis-bunker.html and select the download icon ("Download raw file").The tool works with no internet connection. You can turn on airplane mode before you open the file.
The hash proves that your file is the same as the file in this repository.
Open your Downloads folder in File Explorer. Right-click an empty area and select Open in Terminal.
Type this command and press Enter:
Get-FileHash .\nosis-bunker.html -Algorithm SHA256Compare the result with the value in dist/SHA256SUMS.txt or at https://bunker.nosistech.com/SHA256SUMS.txt. The two values must be the same. Letter case does not matter.
On macOS or Linux, use shasum -a 256 nosis-bunker.html.
Use the EN / ES switch and the sun or moon button at the top. The page starts in the language and the color theme of your system. It saves nothing, so a new visit starts from your system settings again. To open the page in Spanish, use https://bunker.nosistech.com/#es.
The same engine is available to AI agents in two local forms. Both run offline, read only, and need Node.js 22.23.4, 24.22.1 or 26.12.1, or a newer release of the same line (24 is the tested one). Get the code with git clone https://github.com/nosistech/nosis-bunker.git. A clone needs no install step.
Command line (JSON):
node cli/bunker.js --json addresses.txt
cat addresses.txt | node cli/bunker.js --json --lang es
node cli/bunker.js --networksMCP server (Claude Desktop, Claude Code, Cursor and other MCP clients):
{
"mcpServers": {
"bunker": { "command": "node", "args": ["C:\\path\\to\\nosis-bunker\\mcp\\server.js"] }
}
}Tools: scan_addresses and list_networks. The website also has /llms.txt and /networks.json. Read docs/10-agents.md for the details, the JSON shape and the security rules.
Install the bunker-mcp command
Install the command from this GitHub repository. The package is private and is not published on npm.
npm install -g github:nosistech/nosis-bunkerUse Node.js 22.23.4, 24.22.1 or 26.12.1, or a newer release of the same line. Node.js must be on your PATH.
An MCP client can then start Bunker by the command name:
{
"mcpServers": {
"bunker": { "command": "bunker-mcp" }
}
}The command reads standard input. It writes the protocol on standard output. Logs go to standard error. The node settings above and the Docker image below still work.
You can also start the MCP server in a container. The image needs no environment variables and starts the server on standard input and output.
docker build -t nosis-bunker .
docker run -i --rm nosis-bunkerThe -i flag keeps standard input open, which the protocol needs. The --rm flag removes the container when it exits.
You paste these three lines:
bc1p5cyxnuxmeuwuvkwfem96lqzszd02n6xdcjrs20cac6yqjjwudpxqkedrcr Ordinals
bc1qw508d6qejxtdg4y5r3zarvary0c5xw7kv8f3t4 Savings
0x5aAeb6053F3E94C9b9A09f33669435E7Ef1BeAed Daily walletThe tool shows:
| Address | Result | Why |
|---|---|---|
bc1p... Ordinals | Lock visible | A Taproot address contains the public key. |
bc1q... Savings | Check needed | The key stays hidden until the address spends. You answer "No", so the result becomes Lock hidden. |
0x5a... Daily wallet | Check needed | You answer "Yes" because you used it. The result becomes Lock visible. |
The plan then says: move the daily wallet funds to a new account that only receives. Keep the inscriptions on Taproot until Bitcoin activates BIP-360. Keep the savings address hidden.
| Result | Meaning | What to do |
|---|---|---|
| Lock visible | The public key is on chain or in the address. | Move to a hidden address type if the network has one. |
| Check needed | The key is hidden until the address sends or signs. | Answer the question on the card. |
| Lock hidden | The key has never been shown. | Use this address only to receive. |
| Hash-protected | The address type has no curve key (for example BIP-360). | Nothing. |
| Ask your provider, Check your pool | A permissioned network, such as Canton, or a Zcash unified address, whose pool decides the risk. | Ask the operator the questions in the plan, or check the pool. |
| Shows every key | An extended public key (xpub). | Stop sharing it with apps and trackers. |
| Not rated | A typo, a test network, a contract, or an unknown format. | Read the note on the card. |
You need Node.js 22.23.4, 24.22.1 or 26.12.1, or a newer release of the same line (24 is the tested one). Older versions and the odd-numbered lines (23, 25) have known security flaws or no security fixes, and the build tools stop on them. The CLI and the MCP server only warn. The project has no other dependencies.
node --version and press Enter. The result must be v24.22.1 or a newer 24 release.npm test and press Enter. All tests must pass.npm run dist and press Enter. The tool writes dist/nosis-bunker.html and the website folder site/.| Command | What it does |
|---|---|
npm test | Runs all tests (node --test). |
npm run dist | Checks the Node.js version, then builds dist/ and site/. |
npm run check | Version check, build, tests and the writing check together. |
npm run check-links | Opens every explorer link once. This command uses the internet. |
Read docs/08-testing.md to learn how to read the test results.
nosis-bunker/
dist/ the built page (one file) and its SHA-256 hash
site/ the website for bunker.nosistech.com (made by tools/site.js)
assets/ social preview source and PNGs (ADR-031)
src/
core/ hashes and encodings: SHA-256, SHA-512/256, Keccak, BLAKE2b, Base58, Bech32, ...
networks/ one small detector for each network family
index.js the detector pipeline and its order
model.js the exposure model and the card status rules
chains.js network names and verified explorer links
guard.js the secret guard (seed phrases and private keys)
classify.js one address in, one result out
parse.js the input box in, a list of results out
advice.js, plan.js the bunker plan
explorer.js safe explorer links
i18n/ English to Spanish
agent/ the JSON report for the CLI and the MCP server
ui/ the page: template.html, styles.css and the page modules
cli/ command-line tool for people and agents (JSON output)
mcp/ MCP server for AI agents (stdio)
Dockerfile image that starts the MCP server over stdio
audit/ accessibility audit script (manual release step)
tools/ build, website, files for agents, Node.js version gate, writing check, link check
test/ tests and real address fixtures
docs/ all documentation
deploy/ Caddy configuration for a VPSEvery core, network and pipeline module is less than 100 lines. Read docs/04-architecture.md for the data flow.
| Document | Content |
|---|---|
| 01 Background | Why the tool exists, the sealed-box idea, and examples. |
| 02 How it works | The five steps from input to plan. |
| 03 Networks | Every network, its format, its rule and its checksum. |
| 04 Architecture | Modules, data flow, and how to add a network. |
| 05 How it was built | The story of the build and the main choices. |
| 06 Problems and fixes | Each problem, the options, and the fix. |
| 07 UX and UI | Design choices for the page. |
| 08 Testing | What the tests prove and how to run them. |
| 09 Glossary | The words in this project. |
| Decision records | 31 decisions, each with two or more options. |
| Security | OWASP mapping, threat model, supply chain and hosting. |
| 10 Agents | The CLI, the MCP server, llms.txt and the JSON report. |
| 11 Accessibility | WCAG 2.2 AA target, test method and results. |
| Writing style | The writing rules that the docs follow. |
The story of the build, in 13 articles on nosistech.com. Read them in this order.
Read SECURITY.md. In short:
innerHTML and no eval. Tests fail the build if this changes.Bunker is free so that as many people as possible can use it. If you use it, host it, build on it or show its results, please give credit:
Bunker by NosisTech (https://bunker.nosistech.com)This is a request, not a condition. When you redistribute the code, the license requires a copy of the license, the NOTICE text and a note in changed files, and nothing more. The CLI, the MCP server and the plan text include this credit, so it travels with the results.
Apache License 2.0. Copyright 2026 NosisTech LLC. Created by Carlos A. Paredes Vargas. See LICENSE and NOTICE.
You can use, copy, change and sell this tool. If you redistribute it or a work based on it, you must keep the text of the NOTICE file, which names the author. The license gives no right to use the names "Bunker by NosisTech" or "NosisTech", except to say where the code comes from (section 6). Do not present a changed copy as the official version.
Bunker is an educational tool. It is not financial, legal or security advice. It has no warranty. Examine each address on a block explorer and send a small test amount before you move funds.
Pick your client and paste the snippet. Each one is the same server, written the way that client expects it.
claude mcp add bunker -- node C:\path\to\nosis-bunker\mcp\server.js{
"mcpServers": {
"bunker": {
"args": [
"C:\\path\\to\\nosis-bunker\\mcp\\server.js"
],
"command": "node"
}
}
}code --add-mcp '{"name":"bunker","args":["C:\\path\\to\\nosis-bunker\\mcp\\server.js"],"command":"node"}'[mcp_servers.bunker]
command = "node"
args = ["C:\\path\\to\\nosis-bunker\\mcp\\server.js"]Runs locally on your device. Your client starts the server itself, so nothing has to be hosted.
Paste this prompt into your agent. It reads this page and does the setup for you.
Read https://aiagentslisting.com/mcp/bunker-by-nosistech to learn what the "Bunker by NosisTech" MCP server does and how to install it. Add it to my coding agent's MCP configuration as documented on that page, then confirm the server connects and list the tools it exposes.Agents can also browse this directory over MCP at https://aiagentslisting.com/api/mcp
npm install -g github:nosistech/nosis-bunkerdocker run -i --rm nosis-bunkerThis server runs locally, so we can't read its tool list over the web yet.
We could not run this server: it ships no npx package for our sandbox and no public endpoint. The four checks that need a live server are left out, and the grade tops out at B until one exists.
Maintain this server? Claiming proves you own the listing and earns the last 4 points.
Claim this listingPaste this line near the top of your repository's README. The badge always renders the current score.
[](https://aiagentslisting.com/mcp/bunker-by-nosistech)Nothing comparable is listed yet.
v1.2.2Bunker 1.2.2Release notesConnect to the AI Agents Listing MCP server at https://aiagentslisting.com/api/mcp using the HTTP transport and complete the sign-in when it asks. Then call the submit_review tool for the listing "bunker-by-nosistech" with a rating from 1 to 5 and a short note on what worked and what did not.No reviews yet
Be the first to share your experience with this tool.
One email a week. New agents, MCP servers and skills, and what is actually getting traction.