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/Tangtaizong-BUAA/ArgonMemoryWrote 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/tangtaizong-buaa/argonmemory/memory)<a href="https://agentmods.dev/mcp/tangtaizong-buaa/argonmemory/memory"><img src="https://agentmods.dev/badge/mcp/tangtaizong-buaa/argonmemory/memory/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/tangtaizong-buaa/argonmemory/memory"><img src="https://agentmods.dev/badge/mcp/tangtaizong-buaa/argonmemory/memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
memory 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 1mo 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
{ "memory": { "command": "npx", "args": [ "-y", "@argon-ai/memory" ] } }
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.
- 1mo ago First seen · 9 lines scan A 9f4e103d8bdf
memory is an MCP server published in the GitHub repository Tangtaizong-BUAA/ArgonMemory (1 stars, last pushed 7d 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-31.
Other mcp servers, from other repositories
fidelis-memory
Fidelis Memory: faithful agent memory with zero-LLM retrieval by default. By Hermes Labs. Runs locally from the fidelis-memory Python package. Needs 1 environment variable to run.
fidelis
Fidelis Memory: faithful agent memory with zero-LLM retrieval by default. By Hermes Labs. Runs locally from the fidelis-memory Python package.
veracium
Provenance-aware memory for AI agents. Runs locally from the veracium Python package. Needs 3 environment variables to run.
inspeximus
MCP server "inspeximus", hosted remotely at pypi.org, as configured in DanceNitra/inspeximus. Needs 1 environment variable to run.
knowit
Shared team memory for AI coding agents — MCP server and CLI for persistent, queryable knowledge across sessions and teammates. Runs locally from the knowit npm package.
agentbase
Shared knowledge base for AI agents. Semantic search across agents, no setup required — just a URL. Remote server at mcp.agentbase.tools.