io.github.spranab/brainstorm-mcp
NPM · BRAINSTORM-MCP
Multi-model AI brainstorming debates with code review and quick perspectives
Available components
Last scanned (1 hour ago)
Scores higher than 43% of npm servers
Category AI and Machine Learning
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 94 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 (MIT).Pass
- Actively maintained (last published 36 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1646 tokens (~235/item across 7 items; 7 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 Management67
- Stability observed for 20 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
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.
- 5 Nov 26 −5
- Stability: pass → 0.67 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 20 Oct 26 +1
- Stability: 0.97 → pass security
- 18 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.
- 16 Oct 26 +42
- Injection markers: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.87 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 13 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 12 Oct 26 −43
- Stability: 0.97 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Security disclosure: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Schema quality: Schema quality not yet verified: this package could not be installed in a clean environment, so we have no schema to assess. functional
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 97. That category is still filling its 30-day observation window: 27 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 5 Nov 2026 · Analysed npm/brainstorm-mcp@1.8.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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 30 |
| 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 →
add_provider ~348
Add a new AI provider for brainstorming. Supports any OpenAI-compatible API, or a locally installed agent CLI (kind='cli') that runs on an existing subscription instead of API credits.
| Name | Type | Req | Description |
|---|---|---|---|
| adapter | string | – | cli only: built-in adapter — claude, codex, gemini, qwen, kimi, cursor-agent, opencode, droid — or 'custom'. Defaults to the provider name. |
| apiKeyEnvVar | string | – | api only: environment variable holding the API key. Use 'NONE' if no key required. |
| args | array | – | cli only ('custom' adapter): argv template. Placeholders: {{model}}, {{system}}, {{prompt}}, {{outfile}}. |
| backend | string | – | cli only: run the Claude CLI against another vendor's coding plan — moonshot, minimax, glm. Overrides 'adapter'. |
| baseURL | string | – | api only: base URL, e.g. 'http://localhost:11434/v1' for Ollama |
| command | string | – | cli only: executable to run. Required for adapter 'custom'. |
| defaultModel | string | yes | Default model for this provider, e.g. 'llama3', 'sonnet'. Use 'default' to let a CLI pick its own. |
| kind | string | – | 'api' (default) for an OpenAI-compatible HTTP endpoint, 'cli' for a local agent CLI. |
| name | string | yes | Provider name, e.g. 'groq', 'ollama', 'mistral', 'claude' |
| promptVia | string | – | cli only ('custom' adapter): how the prompt reaches the CLI. |
No output schema declared.
No examples provided.
brainstorm ~592
Run a multi-round brainstorming debate between multiple AI models. IMPORTANT: Before calling this tool, you MUST ask the user to choose a mode: 1. **API mode** — Calls configured providers. These are either HTTP APIs billed per token (OpenAI, Gemini, DeepSeek, ...) or locally installed agent CLIs such as 'claude' and 'codex', which run on the user's existing subscription at no API cost. Call list_providers to see which of each are available. 2. **Hosted mode** — No API keys needed. You execute prompts using sub-agents with models available in your environment (opus/sonnet/haiku, GPT, Gemini, etc.). Same model can be used multiple times — each run produces different perspectives. Present these two options to the user with a one-liner explanation, then proceed based on their choice. For API mode: set mode='api'. When participate=true (default), YOU also participate as a debater alongside external models via brainstorm_respond. For Hosted mode: set mode='hosted'. Ask the user which models to use, then spawn sub-agents for each model, collect responses, and call brainstorm_collect.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Optional context to ground the debate — code snippets, PR diffs, error logs, architecture docs, etc. Models will see this alongside the topic. |
| mode | string | – | Execution mode. Must be provided — if not, the tool will return options for the user to choose. 'api' — MCP server calls model APIs directly using configured API keys. 'hosted' — No API keys needed.… |
| models | array | – | Optional: specific models to use as 'provider:model' (e.g. 'openai:gpt-4o', or 'claude:sonnet' / 'codex:default' for subscription-backed CLI providers). If not provided, all configured providers are… |
| participate | boolean | – | Whether Claude should actively participate as a debater in each round (default: true). Set to false for a non-interactive debate between external models only. |
| rounds | integer | – | Number of debate rounds (default: 3) |
| style | string | – | Debate style. 'freeform' (default): open brainstorming. 'redteam': adversarial — models find flaws, risks, and weaknesses. 'socratic': probing questions that expose assumptions and push for deeper un… |
| synthesizer | string | – | Optional: model for final synthesis as 'provider:model'. Defaults to the first model. |
| systemPrompt | string | – | Optional system prompt to guide the brainstorming style or constraints |
| topic | string | yes | The topic, question, or prompt to brainstorm about |
No output schema declared.
No examples provided.
brainstorm_collect ~155
Submit collected model responses for a hosted brainstorm session. After receiving prompts from `brainstorm` (mode='hosted') or a previous `brainstorm_collect` call, execute each prompt by spawning a sub-agent for EACH model (use the model parameter to select the right model, e.g., model='sonnet' or model='haiku'). Collect all responses and submit them here. This tool returns either: (1) the next round's prompt to execute, (2) a synthesis prompt for a single model, or (3) the final formatted debate result when complete.
| Name | Type | Req | Description |
|---|---|---|---|
| responses | array | yes | Array of model responses collected by the host |
| session_id | string | yes | The session ID from the brainstorm tool |
No output schema declared.
No examples provided.
brainstorm_quick ~182
Get instant multi-model perspectives on any question — no debate rounds, no synthesis delay. Fires all models in parallel and returns a compact comparison. Under 10 seconds. Use this for quick second opinions, snap decisions, or when you want diverse perspectives fast. For deeper analysis with multiple rounds and synthesis, use the `brainstorm` tool instead.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Optional context — code snippets, error logs, etc. Models will see this alongside the topic. |
| models | array | – | Optional: specific models as 'provider:model' (API providers, or CLI providers like 'claude:sonnet' that use a subscription instead of API credits). If not provided, all configured providers are used. |
| style | string | – | Perspective style (default: freeform) |
| topic | string | yes | The question or topic to get quick perspectives on |
No output schema declared.
No examples provided.
brainstorm_respond ~132
Submit YOUR (Claude's) response for the current round of an interactive brainstorm session. After the brainstorm tool returns external models' responses, call this tool with your substantive contribution. Read all responses carefully and engage with specific points — agree, disagree, build upon, or challenge ideas. Do not just summarize. After your response, the next round runs automatically (or synthesis if final round).
| Name | Type | Req | Description |
|---|---|---|---|
| response | string | yes | Your substantive contribution to this round of the debate. Engage deeply with the other models' responses. Minimum 50 characters. |
| session_id | string | yes | The session ID returned by the brainstorm tool |
No output schema declared.
No examples provided.
brainstorm_review ~189
Multi-model code review. Pass a diff and get structured findings with severity, file/line references, and a verdict (approve / approve with warnings / needs changes). Multiple models review independently, then findings are synthesized and deduplicated. Use this for PR reviews, code audits, or pre-commit checks.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional: PR description or commit message |
| diff | string | yes | The unified diff to review (e.g., output of `git diff`) |
| focus | – | – | Optional: focus areas for the review. Default: all categories. |
| instructions | string | – | Optional: repo-specific review instructions (e.g., 'we use strict null checks', 'focus on SQL injection risks') |
| models | array | – | Optional: specific models as 'provider:model'. Default: all configured providers. |
| title | string | – | Optional: PR title or change summary for context |
No output schema declared.
No examples provided.
list_providers ~48
List all configured AI providers and their default models for brainstorming. Includes locally installed agent CLIs (claude, codex, ...) which run on an existing subscription instead of metered API credits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.spranab/brainstorm-mcp server?
io.github.spranab/brainstorm-mcp runs locally as an npm package, launched with npx -y brainstorm-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 · brainstorm-mcp
claude mcp add spranab-brainstorm-mcp -- npx -y brainstorm-mcp
What is the io.github.spranab/brainstorm-mcp server?
io.github.spranab/brainstorm-mcp is listed in the public MCP registry as io.github.spranab/brainstorm-mcp. Multi-model AI brainstorming debates with code review and quick perspectives. This page covers its npm package (brainstorm-mcp).
Is the io.github.spranab/brainstorm-mcp server safe to use?
io.github.spranab/brainstorm-mcp scores 72 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 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 io.github.spranab/brainstorm-mcp server expose?
io.github.spranab/brainstorm-mcp exposes 7 tools: brainstorm, brainstorm_respond, brainstorm_collect, brainstorm_quick, brainstorm_review, and 2 more. Their descriptions and schemas cost roughly 1,646 tokens of context every time the server is loaded.
Is the io.github.spranab/brainstorm-mcp server still maintained?
io.github.spranab/brainstorm-mcp is still listed as active in the MCP registry. We last reached this channel on 5 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 io.github.spranab/brainstorm-mcp server under?
io.github.spranab/brainstorm-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.