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/axrbarsic/verifiable-memory-bankWrote 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/axrbarsic/verifiable-memory-bank/verifiable-memory-bank-verifiable-memory-bank)<a href="https://agentmods.dev/mcp/axrbarsic/verifiable-memory-bank/verifiable-memory-bank-verifiable-memory-bank"><img src="https://agentmods.dev/badge/mcp/axrbarsic/verifiable-memory-bank/verifiable-memory-bank-verifiable-memory-bank/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/axrbarsic/verifiable-memory-bank/verifiable-memory-bank-verifiable-memory-bank"><img src="https://agentmods.dev/badge/mcp/axrbarsic/verifiable-memory-bank/verifiable-memory-bank-verifiable-memory-bank.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
verifiable-memory-bank 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 11d 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
{
"verifiable-memory-bank": {
"command": "memory-bank-mcp"
}
}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.
- 11d ago First seen · 5 lines scan A f7825bddf988
verifiable-memory-bank is an MCP server published in the GitHub repository axrbarsic/verifiable-memory-bank (0 stars, last pushed 1mo ago), licensed 0BSD. 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
callosium
One shared memory for every AI you use, in plain Markdown files you own. Runs locally from the callosium npm package. Needs 1 environment variable to run.
memory
MCP server "memory" as configured in Tangtaizong-BUAA/ArgonMemory. Runs locally from the @argon-ai/memory npm package.
mcp
Owned, portable working memory: a plain-files markdown brain any model can read and cite. Runs locally from the @br8n/mcp npm package.
ori-memory
Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search. Runs locally from the ori-memory npm package.
memory
MCP server "memory" as configured in Yupcha/memXT. Launched with ${HOME}/.memxt/bin/memxt mcp. Needs 2 environment variables to run.
lorg-mcp-server
Shared, peer-validated knowledge archive for AI agents — search, contribute, and validate via MCP. Runs locally from the lorg-mcp-server npm package. Needs 1 environment variable to run.