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.
npx agentmods add mcp/ybookoff/thebrain-mcp/thebraingit clone --depth 1 https://github.com/yBookoff/thebrain-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/ybookoff/thebrain-mcp/thebrain)<a href="https://agentmods.dev/mcp/ybookoff/thebrain-mcp/thebrain"><img src="https://agentmods.dev/badge/mcp/ybookoff/thebrain-mcp/thebrain.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
thebrain 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 6d 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
{
"thebrain": {
"command": "npx",
"args": [
"-y",
"thebrain-mcp-server"
],
"env": {
"THEBRAIN_API_KEY": "",
"THEBRAIN_BASE_URL": "",
"THEBRAIN_DATA_DIR": "",
"THEBRAIN_ALLOW_DESTRUCTIVE": "",
"THEBRAIN_EMBEDDING_MODEL": "",
"THEBRAIN_EMBEDDING_DTYPE": "",
"THEBRAIN_TIMEOUT_MS": ""
}
}
}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.
- 6d ago First seen · 18 lines scan A b34ad4588b47
thebrain is an MCP server published in the GitHub repository yBookoff/thebrain-mcp (6 stars, last pushed 24d 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-31.
Other mcp servers, from other repositories
second-brain-mcp
Second brain en Obsidian: notas, conceptos como nodos, resurfacing y salud del grafo. En castellano. Runs locally from the @toportal/second-brain-mcp npm package. Needs 2 environment variables to run.
NOUZ-MCP
MCP server for Obsidian — semantic knowledge graph with auto-classification, DAG hierarchy, and cross-domain bridge detection. Runs locally from the nouz-mcp Python package. Needs 8 environment variables to run.
talamus
MCP server "talamus" as configured in ampres-ai/talamus. Runs locally from the talamus[mcp] Python package.
talamus
Local-first, source-grounded memory for AI agents with citations, bitemporal history, and MCP. Runs locally from the talamus Python package.
LINZA-MCP
Local-first MCP sidecar for agent workspaces, artifacts, review intents, and context export. Runs locally from the linza-mcp Python package. Needs 9 environment variables to run.
june-mcp
MCP server for Junê — give any MCP agent (Claude Desktop, Claude Code, …) a shared, cited knowledge-graph memory backed by a June endpoint. Runs locally from the june-mcp Python package. Needs 13 environment variables to run.