brainCloud MCP Helper
NPM · @BRAINCLOUD/MCP-HELPER · SCANNED SEP 24
Helper for brainCloud MCP that gives it local file access, enabling easy git sync of cloud code.
Available components
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 Security98
- 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
- 31 of 99 dependencies flagged as unhealthy. View diagnostics → Partial
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 (Apache-2.0).Pass
- Actively maintained (last published 75 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1428 tokens (~357/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
How do I install the brainCloud MCP Helper server?
brainCloud MCP Helper runs locally as an npm package, launched with npx -y @braincloud/mcp-helper. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @braincloud/mcp-helper
claude mcp add com-braincloudservers-braincloud-mcp-helper -- npx -y @braincloud/mcp-helper
{
"mcpServers": {
"com-braincloudservers-braincloud-mcp-helper": {
"command": "npx",
"args": [
"-y",
"@braincloud/mcp-helper"
]
}
}
} {
"servers": {
"com-braincloudservers-braincloud-mcp-helper": {
"command": "npx",
"args": [
"-y",
"@braincloud/mcp-helper"
]
}
}
} codex mcp add com-braincloudservers-braincloud-mcp-helper -- npx -y @braincloud/mcp-helper
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-braincloudservers-braincloud-mcp-helper": {
"type": "local",
"command": [
"npx",
"-y",
"@braincloud/mcp-helper"
],
"enabled": true
}
}
} openclaw mcp add com-braincloudservers-braincloud-mcp-helper --command npx --arg -y --arg @braincloud/mcp-helper
mcp_servers:
com-braincloudservers-braincloud-mcp-helper:
command: "npx"
args: ["-y", "@braincloud/mcp-helper"] {
"McpServers": {
"com-braincloudservers-braincloud-mcp-helper": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@braincloud/mcp-helper"
]
}
}
} assistant mcp add com-braincloudservers-braincloud-mcp-helper -t stdio -c npx -a -y @braincloud/mcp-helper
{
"mcpServers": {
"com-braincloudservers-braincloud-mcp-helper": {
"command": "npx",
"args": [
"-y",
"@braincloud/mcp-helper"
]
}
}
} 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.
- 23 Sept 26 −2
- Stability: pass → 0.83 functional
- 22 Sept 26 0
- Stability: 0.97 → pass security
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 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 24 Sept 2026 · Analysed npm/@braincloud/mcp-helper@6.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 99 packages
| Packages resolved | 99 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
pull Pull cloud-code to local ~345
Apply brainCloud → local for non-conflicting changes (pull / pull-new). Conflicts and local-only changes are left untouched and reported in "skipped". Local deletes only happen with allowDeletes=true. Use a "read" ticket from getSyncTicket.
| Name | Type | Req | Description |
|---|---|---|---|
| adoptNoGitBranch | boolean | – | Confirm moving the no-git sync state and app mapping onto the current git branch (dropping the no-branch entry). Needed once, when a folder first synced without git is now on a real branch; the tool… |
| allowDeletes | boolean | – | Delete local files for scripts removed on brainCloud (default false). |
| branch | string | – | Git branch to sync. Defaults to the current branch from .git/HEAD; if the folder is not a git repo, a reserved no-branch key is used and can later be adopted onto a real branch. |
| confirmAppName | string | – | Safety confirmation. Only needed for a previously-synced folder that has no committed .bcsync app mapping (e.g. synced by an older helper): set this to the ticket's appName to confirm you intend to s… |
| rootDir | string | – | Absolute path to the local cloud-code sync folder (the .ccjs tree + .bcsync). Optional: if omitted, the helper discovers the nearest .bcsync folder at or above its working directory. Pass it explicit… |
| ticket | object | yes | Short-lived ticket from the hosted MCP getSyncTicket tool. |
No output schema declared.
No examples provided.
push Push local cloud-code to brainCloud ~344
Apply local → brainCloud for non-conflicting changes (push / push-new) via one bulk import (mode addAndUpdateOnly — never deletes). Conflicts and remote-only changes are left untouched and reported in "skipped". Requires a "write" ticket from getSyncTicket (the hosted MCP refuses a write ticket for a live-locked app).
| Name | Type | Req | Description |
|---|---|---|---|
| adoptNoGitBranch | boolean | – | Confirm moving the no-git sync state and app mapping onto the current git branch (dropping the no-branch entry). Needed once, when a folder first synced without git is now on a real branch; the tool… |
| branch | string | – | Git branch to sync. Defaults to the current branch from .git/HEAD; if the folder is not a git repo, a reserved no-branch key is used and can later be adopted onto a real branch. |
| confirmAppName | string | – | Safety confirmation. Only needed for a previously-synced folder that has no committed .bcsync app mapping (e.g. synced by an older helper): set this to the ticket's appName to confirm you intend to s… |
| rootDir | string | – | Absolute path to the local cloud-code sync folder (the .ccjs tree + .bcsync). Optional: if omitted, the helper discovers the nearest .bcsync folder at or above its working directory. Pass it explicit… |
| ticket | object | yes | Short-lived ticket from the hosted MCP getSyncTicket tool. |
No output schema declared.
No examples provided.
status Cloud-code sync status ~324
Dry-run: classify every cloud-code script for the branch (in-sync / pull / push / conflict / pull-new / push-new / delete-local / delete-remote). Always safe — no writes. Use a "read" ticket from getSyncTicket.
| Name | Type | Req | Description |
|---|---|---|---|
| adoptNoGitBranch | boolean | – | Confirm moving the no-git sync state and app mapping onto the current git branch (dropping the no-branch entry). Needed once, when a folder first synced without git is now on a real branch; the tool… |
| branch | string | – | Git branch to sync. Defaults to the current branch from .git/HEAD; if the folder is not a git repo, a reserved no-branch key is used and can later be adopted onto a real branch. |
| confirmAppName | string | – | Safety confirmation. Only needed for a previously-synced folder that has no committed .bcsync app mapping (e.g. synced by an older helper): set this to the ticket's appName to confirm you intend to s… |
| rootDir | string | – | Absolute path to the local cloud-code sync folder (the .ccjs tree + .bcsync). Optional: if omitted, the helper discovers the nearest .bcsync folder at or above its working directory. Pass it explicit… |
| ticket | object | yes | Short-lived ticket from the hosted MCP getSyncTicket tool. |
No output schema declared.
No examples provided.
sync Two-way sync cloud-code with brainCloud ~415
Full bidirectional sync for the branch: pulls non-conflicting remote changes, pushes non-conflicting local changes, and 3-way-merges scripts changed on BOTH sides (using brainCloud version history for the merge base). Cleanly-merged scripts are written locally and pushed; genuine conflicts get git-style <<<<<<< markers written into the file and are reported in "conflicted" for you to resolve, then re-run sync. Deletions (delete-local / delete-remote) are applied only when allowDeletes=true. Requires a "write" ticket from getSyncTicket (refused for a live-locked app).
| Name | Type | Req | Description |
|---|---|---|---|
| adoptNoGitBranch | boolean | – | Confirm moving the no-git sync state and app mapping onto the current git branch (dropping the no-branch entry). Needed once, when a folder first synced without git is now on a real branch; the tool… |
| allowDeletes | boolean | – | Apply deletions in both directions (default false). |
| branch | string | – | Git branch to sync. Defaults to the current branch from .git/HEAD; if the folder is not a git repo, a reserved no-branch key is used and can later be adopted onto a real branch. |
| confirmAppName | string | – | Safety confirmation. Only needed for a previously-synced folder that has no committed .bcsync app mapping (e.g. synced by an older helper): set this to the ticket's appName to confirm you intend to s… |
| rootDir | string | – | Absolute path to the local cloud-code sync folder (the .ccjs tree + .bcsync). Optional: if omitted, the helper discovers the nearest .bcsync folder at or above its working directory. Pass it explicit… |
| ticket | object | yes | Short-lived ticket from the hosted MCP getSyncTicket tool. |
No output schema declared.
No examples provided.
What is the brainCloud MCP Helper server?
brainCloud MCP Helper is listed in the public MCP registry as com.braincloudservers/braincloud-mcp-helper. Helper for brainCloud MCP that gives it local file access, enabling easy git sync of cloud code. This page covers its npm package (@braincloud/mcp-helper).
Is the brainCloud MCP Helper server safe to use?
brainCloud MCP Helper scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. 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 brainCloud MCP Helper server expose?
brainCloud MCP Helper exposes 4 tools: status, pull, push, sync. Their descriptions and schemas cost roughly 1,428 tokens of context every time the server is loaded.
Is the brainCloud MCP Helper server still maintained?
brainCloud MCP Helper is still listed as active in the MCP registry. We last reached this channel on 24 September 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 brainCloud MCP Helper server under?
brainCloud MCP Helper declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.