Bot Bridge CC Helper
MCPB · BOTBRIDGE-CC-HELPER.MCPB
Bridge a remote bot to a local Bot Bridge CC Helper: dispatch coding tasks and read progress.
Available components
Last scanned (20 hours ago)
Scores higher than 82% of MCPB servers
Category Developer Tools
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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 22 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 293 tokens (~58/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +2
- Maintenance: unverified → pass ▲ functional
- 2 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 1 Nov 26 −1
- Security disclosure: fail → unverified ▼ functional
- Maintenance: pass → unverified ▼ functional
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Analysed mcpb/https://github.com/1019666077-bit/botbridge-cc-helper-vscode/releases/download/v0.1.0-mcpb/botbridge-cc-helper.mcpb@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
cc_helper_dispatch ~131
Dispatch one task to the local Bot Bridge CC Helper by writing a job JSON into its inbox folder. The Helper daemon runs Claude Code with the prompt and streams progress. The user watches it in the tray. Returns the task id used for status polling and stop.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Optional unique task id. Omit to let the bridge generate one. Do not reuse an id. |
| prompt | string | yes | The work for the local Claude Code run. Be explicit about files and the expected result. Never include secrets. |
| title | string | – | Short human-readable label shown in the tray panel. |
No output schema declared.
No examples provided.
cc_helper_list_tasks ~24
List queued, running and finished tasks under the local Helper home folder.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cc_helper_status ~42
Check whether the local Bot Bridge CC Helper (Windows desktop Helper) is installed, and how many jobs are queued, running and done. Call this before dispatching.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cc_helper_stop ~47
Ask the local Helper to stop a running task by writing "stop" into its control folder. The Helper acts on its next poll.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Task id to stop. |
No output schema declared.
No examples provided.
cc_helper_task_status ~49
Read the state of one dispatched task: queued in inbox/, running with status.json + progress.md, or finished in done/.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Task id returned by cc_helper_dispatch. |
No output schema declared.
No examples provided.
How do I install the Bot Bridge CC Helper MCP server?
Bot Bridge CC Helper ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, cad74c8d776575c6888f1f9f55a2ec72fa1e7ed25f186f6a9d0a763fea769556; the commands to do that are on this page. If it does not match, do not open it.
mcpb · botbridge-cc-helper.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
cad74c8d776575c6888f1f9f55a2ec72fa1e7ed25f186f6a9d0a763fea769556
macOS / Linux
echo "cad74c8d776575c6888f1f9f55a2ec72fa1e7ed25f186f6a9d0a763fea769556 botbridge-cc-helper.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\botbridge-cc-helper.mcpb).Hash -eq "cad74c8d776575c6888f1f9f55a2ec72fa1e7ed25f186f6a9d0a763fea769556"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the Bot Bridge CC Helper MCP server?
Bot Bridge CC Helper is an MCP server listed in the public MCP registry as io.github.1019666077-bit/cc-helper. Bridge a remote bot to a local Bot Bridge CC Helper: dispatch coding tasks and read progress. This page covers its MCPB bundle (https://github.com/1019666077-bit/botbridge-cc-helper-vscode/releases/download/v0.1.0-mcpb/botbridge-cc-helper.mcpb).
Is the Bot Bridge CC Helper MCP server safe to use?
Bot Bridge CC Helper scores 51 out of 100 on VerifyMCP. 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 Bot Bridge CC Helper MCP server expose?
Bot Bridge CC Helper exposes 5 tools: cc_helper_status, cc_helper_dispatch, cc_helper_task_status, cc_helper_list_tasks, cc_helper_stop. Their descriptions and schemas cost roughly 293 tokens of context every time the server is loaded.
What licence is the Bot Bridge CC Helper MCP server under?
Bot Bridge CC Helper declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.