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/zensation-ai/zenbrainWrote 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/zensation-ai/zenbrain/mcp-zenbrain)<a href="https://agentmods.dev/mcp/zensation-ai/zenbrain/mcp-zenbrain"><img src="https://agentmods.dev/badge/mcp/zensation-ai/zenbrain/mcp-zenbrain/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/zensation-ai/zenbrain/mcp-zenbrain"><img src="https://agentmods.dev/badge/mcp/zensation-ai/zenbrain/mcp-zenbrain.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
zenbrain 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 9d 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
{
"zenbrain": {
"command": "npx",
"args": [
"-y",
"@zensation/mcp"
],
"env": {
"ZENBRAIN_DB": "./zenbrain.db",
"ZENBRAIN_CONTEXTS": "personal,work,learning,creative"
}
}
}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.
- 9d ago First seen · 13 lines scan A ee91aa6027d6
zenbrain is an MCP server published in the GitHub repository zensation-ai/zenbrain (22 stars, last pushed 2d ago), licensed Apache-2.0. 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
deepmem
Mem0-compatible persistent memory for AI agents: write facts once, recall them semantically. Remote server at deepmem.dev.
veracium
Provenance-aware memory for AI agents. Runs locally from the veracium Python package. Needs 3 environment variables to run.
pseudolife-memory
MCP server "pseudolife-memory" as configured in Pseudogiant-xr/Pseudolife-MCP. Launched with C:\path\to\Pseudolife-MCP\.venv\Scripts\pseudolife-mcp.exe. Needs 3 environment variables to run.
pseudolife-mcp
Pseudolife persistent long-term memory for MCP-compatible coding agents. Runs locally from the pseudolife-mcp Python package.
memoweft
Portable AI memory as MCP tools: five reads and three controlled writes. Runs locally from the @memoweft/mcp-server npm package. Needs 1 environment variable to run.
trinity-memory
Trinity v8.2.0: Memory Operating System — Multi-Agent Shared Memory, 50-Layer Guardian Chain, 129-Paper Brain-Inspired Alignment, GraphQL API, Raft Cluster, BM25+Jieba Chinese Retrieval. Runs locally from the trinity-memory Python package.