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/SherryLi-vc/strata-memoryWrote 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/sherryli-vc/strata-memory/strata-memory-mcp)<a href="https://agentmods.dev/mcp/sherryli-vc/strata-memory/strata-memory-mcp"><img src="https://agentmods.dev/badge/mcp/sherryli-vc/strata-memory/strata-memory-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
strata-memory-mcp 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 6d 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
{ "strata-memory-mcp": { "command": "uvx", "args": [ "strata-memory-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.
- 6d ago First seen · 8 lines scan A e0214438710a
strata-memory-mcp is an MCP server published in the GitHub repository SherryLi-vc/strata-memory (0 stars, last pushed 27d 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
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.
mcp-server
Persistent memory and virtual filesystem MCP server for AI agents. Runs locally from the @memofs/mcp-server npm package. Needs 2 environment variables to run.
memento-context
MCP server "memento-context" as configured in FranBarInstance/memento-context. Runs locally from the memento-context Python package.
memory
MCP server "memory" as configured in blockmandev/ai-memory. Runs D:/(project-folders)/memory/memory-mcp-server.js with node. Needs 2 environment variables to run.
telemem
Long-term & multimodal memory for AI agents — character isolation, video pipeline, MCP server, mem0-compatible. Runs locally from the telemem Python package. Needs 3 environment variables to run.
ori-memory
Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search. Runs locally from the ori-memory npm package.