Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/spranab/brainstorm-mcpInstalling this writes the configuration, not the program: `node` runs a file from the repository, so clone it first and make the path in the command match where you put it.
Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/spranab/brainstorm-mcp/brainstorm)<a href="https://agentmods.dev/mcp/spranab/brainstorm-mcp/brainstorm"><img src="https://agentmods.dev/badge/mcp/spranab/brainstorm-mcp/brainstorm/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/spranab/brainstorm-mcp/brainstorm"><img src="https://agentmods.dev/badge/mcp/spranab/brainstorm-mcp/brainstorm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
brainstorm scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"brainstorm": {
"command": "node",
"args": [
"${workspaceFolder}/dist/index.js"
],
"env": {
"BRAINSTORM_CONFIG": "${workspaceFolder}/brainstorm.config.json"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 11 lines scan A a5bbfdea590c
brainstorm is an MCP server published in the GitHub repository spranab/brainstorm-mcp (71 stars, last pushed 17d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-08.
Other mcp servers, from other repositories
external-agents
Multi-LLM MCP server for Claude Code & Codex — route AI agent work across 20+ low-cost provider buckets with round-robin dispatch and quota-aware fallback. Runs locally from the @mrrlin-dev/external-agents npm package.
fcc-graph
MCP server "fcc-graph" as configured in sepehrbayat/SEPCC. Runs locally from the python Python package. Needs 1 environment variable to run.
llm-usage-mcp
Local-first, multi-provider tool that captures LLM API spend and exposes it to coding agents via MCP. Runs locally from the llm-usage-mcp Python package.
deepseek-delegate-mcp
MCP server "deepseek-delegate-mcp" as configured in trixmix821/deepseek-delegate-mcp. Runs locally from the deepseek-delegate-mcp npm package.
codereview-mcp
MCP server "codereview-mcp" as configured in lfylow/codereview-mcp. Runs locally from the codereview-mcp Python package.
db-semantic-mcp
A multi-backend MCP server (PostgreSQL + SQL Server) for AI coding agents — schema metadata + semantic search. Runs locally from the db-semantic-mcp Python package.