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/SIDDHU123M/membrain-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/siddhu123m/membrain-mcp/membrain)<a href="https://agentmods.dev/mcp/siddhu123m/membrain-mcp/membrain"><img src="https://agentmods.dev/badge/mcp/siddhu123m/membrain-mcp/membrain.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
membrain 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
{
"membrain": {
"command": "npx",
"args": [
"-y",
"membrain-mcp"
],
"env": {}
}
}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 · 10 lines scan A 4eb2a5420f29
membrain is an MCP server published in the GitHub repository SIDDHU123M/membrain-mcp (1 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
plur
Open, local-first engram memory for AI agents: read, correct, delete; shared over MCP. Runs locally from the @plur-ai/mcp npm package.
perenna
A lightweight, Git-backed permanent memory for AI agents. Runs locally from the perenna Python package. Needs 4 environment variables to run.
inspeximus
MCP server "inspeximus" as configured in DanceNitra/inspeximus. Runs locally from the inspeximus[mcp] Python package. Needs 1 environment variable to run.
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.
sovseal-memory
Local-first, zero-knowledge AI memory across Claude, Cursor, and every MCP client. 0 RTT reads. Runs locally from the @sovseal/mcp-server npm package.
delx-memory
Local-first persistent memory MCP: shared SQLite key/value store, searchable, TTL-aware, secret-safe. Runs locally from the delx-memory npm package. Needs 5 environment variables to run.