Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

bundlebox

NPM · BUNDLEBOX

Where the work is, packed before the agent reads: brief, symbol tables, findings, token bill.

Available components

0 this week 92 Trust /100

Last scanned (16 hours ago)

Scores higher than 92% of npm servers

Category Developer Tools

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to blackswanalpha/bundlebox). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 59 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 634 tokens (~63/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 13% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Nov 26 +1
    • Stability: 0.97 → pass security
  • 18 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 12 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 5 Nov 26 −3
    • Stability: pass → 0.77 functional
  • 30 Oct 26 +1
    • Stability: 0.97 → pass security
  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/bundlebox@0.8.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo blackswanalpha/bundlebox
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/blackswanalpha/bundlebox/.github/workflows/release.yml@refs/tags/v0.8.0
Rekor log index 2910210156
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:a50d3832a62c7a3e5214aa56906a9d0eb3ba42f682b2484daaf680cd39781ce0d88adfafd6ee3cb553ffeb906bb1e20f5c9f1f277c34d7e8b4ba263f0

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~600 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
bb_context ~68

Does this set of files fit in one session? Returns FITS / TIGHT / SPLIT / HEAVY with the token parts (overhead, payload, churn, reserve) and, when SPLIT, the cut.

NameTypeReqDescription
kindstring––
pathsarrayyes–

No output schema declared.

No examples provided.

bb_explain ~43

One finding in full: evidence, fix hint, actuator, and the triage derivation (why it was or was not promoted).

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

bb_findings ~57

Open findings from the last `bb scan`: id, severity, detector, title, primary file. Filter by detector or minimum severity.

NameTypeReqDescription
detectorstring––
limitinteger––
severitystring––

No output schema declared.

No examples provided.

bb_oversight_brief ~57

What is already known about these files from the last oversight scan: god-shaped, duplicated, bloated, vibe-coded marks, and the guideline to apply while editing. About 300 tokens.

NameTypeReqDescription
pathsarrayyes–

No output schema declared.

No examples provided.

bb_pinpoint ~100

One problem -> one focused brief: the files and symbol regions located already (quoted with line numbers), the scope that fits one window, evidence already on file, the acceptance command, traps and guidelines. Call this BEFORE searching the tree.

NameTypeReqDescription
filesarray–files you already know are involved (optional)
kindstring––
max_filesinteger––
problemstringyesthe task in one or two sentences

No output schema declared.

No examples provided.

bb_scan ~41

Run the zero-token detectors now (seconds) and return the per-detector counts. Use bb_findings to read the results.

NameTypeReqDescription
onlyarray––

No output schema declared.

No examples provided.

bb_session ~45

What the current or last session used (measured from the transcript) and what it was spared (cache: measured; automation: estimate range).

NameTypeReqDescription
session_idstring––

No output schema declared.

No examples provided.

bb_situation ~74

Where this work stands, in one call: branch and what is uncommitted, what proves a change here, which artefacts are missing or stale, the work already packed, and what the last echos run saw. Call this instead of git status + git diff + bb env + bb findings + bb echos.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

bb_snapgen ~80

Reference tables built from the tree and kept fresh by fingerprint: layout, symbols-<dir> (name file:line), routes, docs, commands, hot, tests, deps. With no `table` returns the INDEX with each table's token cost so you can choose. Read a table instead of grepping.

NameTypeReqDescription
tablestring––

No output schema declared.

No examples provided.

bb_tokens_estimate ~35

Estimated tokens per file and in total, with the calibrated estimator (not chars/4).

NameTypeReqDescription
pathsarrayyes–

No output schema declared.

No examples provided.

Install

How do I install the bundlebox MCP server?

bundlebox runs locally as an npm package, launched with npx -y bundlebox mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · bundlebox

# add to Claude Code
claude mcp add blackswanalpha-bundlebox -- npx -y bundlebox mcp
Common questions

What is the bundlebox MCP server?

bundlebox is an MCP server listed in the public MCP registry as io.github.blackswanalpha/bundlebox. Where the work is, packed before the agent reads: brief, symbol tables, findings, token bill. This page covers its npm package (bundlebox).

Is the bundlebox MCP server safe to use?

bundlebox scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the bundlebox MCP server expose?

bundlebox exposes 10 tools: bb_pinpoint, bb_context, bb_snapgen, bb_findings, bb_scan, and 5 more. Their descriptions and schemas cost roughly 600 tokens of context every time the server is loaded.

Is the bundlebox MCP server still maintained?

bundlebox is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the bundlebox MCP server under?

bundlebox declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the bundlebox MCP server?

VerifyMCP ran 16 checks on bundlebox, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.