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/mordechaipotash/brain-mcpWrote 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/mordechaipotash/brain-mcp/brain)<a href="https://agentmods.dev/mcp/mordechaipotash/brain-mcp/brain"><img src="https://agentmods.dev/badge/mcp/mordechaipotash/brain-mcp/brain.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
brain 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 7d 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
{
"brain": {
"command": "uvx",
"args": [
"brain-mcp==2.0.0b3",
"serve"
],
"env": {
"BRAIN_HOME": "${user_config.brain_home}"
}
}
}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.
- 7d ago First seen · 12 lines scan A a73ab1add37b
brain is an MCP server published in the GitHub repository mordechaipotash/brain-mcp (69 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-08-30.
Other mcp servers, from other repositories
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
neverinfamous-memory-journal-mcp
A MCP server built for developers enabling Git based project management with project and personal… Remote server at server.smithery.ai.
engineering-os
MCP server "engineering-os" as configured in engineering-os/engineering-os. Launched with eos serve.
memex
MCP server "memex" as configured in BongSuCHOI/memex. Runs cli/runtime-exec.js with node.
playwright
Lets the agent drive a real browser: open pages, click, type, take screenshots and read the accessibility tree, using Playwright. Runs locally from the @playwright/mcp npm package.
lore-context-mcp
Governed AI-agent memory, Evidence Ledger traces, evals, and portable context tools. Runs locally from the @lore-context/server npm package. Needs 3 environment variables to run.