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/maxweb4u/mcp-memorybankWrote 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/maxweb4u/mcp-memorybank/memorybank)<a href="https://agentmods.dev/mcp/maxweb4u/mcp-memorybank/memorybank"><img src="https://agentmods.dev/badge/mcp/maxweb4u/mcp-memorybank/memorybank/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/maxweb4u/mcp-memorybank/memorybank"><img src="https://agentmods.dev/badge/mcp/maxweb4u/mcp-memorybank/memorybank.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
memorybank 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 yesterday.
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
{
"memorybank": {
"command": "npx",
"args": [
"-y",
"@maxweb4u/mcp-memorybank"
],
"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.
- yesterday First seen · 10 lines scan A 0b14800464f2
memorybank is an MCP server published in the GitHub repository maxweb4u/mcp-memorybank (0 stars, last pushed yesterday), 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
prism-coder
Session memory for coding agents: local-first recall, drift detection, on-device inference. Runs locally from the prism-mcp-server npm package. Needs 8 environment variables to run.
prism-mcp
Persistent session memory for AI coding agents that never leaves your machine — including the on-device model that reasons over it. Restores your prior decisions, open TODOs, and changed files across sessions; adds associative recall of related past work. Runs locally from the prism-mcp-server npm package. Needs 1…
inkwell-memory
MCP server "inkwell-memory" as configured in veronchenko/inkwell-memory. Runs in Docker (docker.io/foreigndmitryi/inkwell-memory:0.14.0). Needs 2 environment variables to run.
kioku
MCP server "kioku" as configured in sandovaldavid/kioku. Launched with kioku. Needs 3 environment variables to run.
mcp
Owned, portable working memory: a plain-files markdown brain any model can read and cite. Runs locally from the @br8n/mcp npm package.
second-brain-mcp
Read-only MCP server for any Obsidian/markdown vault. Index-first retrieval, hard page budget, path sandbox - the retrieval protocol enforced by the server, not requested in prose. Runs locally from the @nanthansr/second-brain-mcp npm package.