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.
npx agentmods add mcp/thezenmonster/agentmem/agentmemgit clone --depth 1 https://github.com/Thezenmonster/agentmemGrade A, and why
agentmem 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 2d 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
{
"agentmem": {
"command": "uvx",
"args": [
"quilmem"
],
"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.
- 2d ago First seen · 9 lines scan A 7f70b3d4e572
agentmem is an MCP server published in the GitHub repository Thezenmonster/agentmem (3 stars, last pushed 4mo 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
perseus-vault
MCP server "perseus-vault" as configured in Perseus-Computing-LLC/perseus-vault. Runs in Docker (ghcr.io/perseus-computing-llc/perseus-vault:2.23.2).
memx
MCP server "memx" as configured in NeoLi00/memX. Runs ${CLAUDE_PLUGIN_ROOT}/dist/.runtime/src/bin/memx-mcp.mjs with node. Needs 3 environment variables to run.
growmos
MCP server "growmos" as configured in codician-team/growmos. Launched with growmos mcp.
agent-memory-os
Local-first, MCP-native memory engine for AI agents with RAM cache and context-budgeted recall. Runs locally from the agent-memory-os Python package. Needs 2 environment variables to run.
global-agent-memory
Local-first, project-aware durable memory through a versioned MCP interface. Runs locally from the global-memory-mcp Python package.
wappmcp
TypeScript stdio MCP server and CLI for WhatsApp Web. Runs locally from the wappmcp npm package.