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/memseekai/memseek/claude-code-memseekgit clone --depth 1 https://github.com/memseekai/memseekWrote 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/memseekai/memseek/claude-code-memseek)<a href="https://agentmods.dev/mcp/memseekai/memseek/claude-code-memseek"><img src="https://agentmods.dev/badge/mcp/memseekai/memseek/claude-code-memseek.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
memseek 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 5d 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
{
"memseek": {
"type": "http",
"url": "${user_config.MEMSEEK_URL}/mcp",
"headers": {
"Authorization": "Bearer ${user_config.MEMSEEK_API_KEY}"
},
"timeout": 180000
}
}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.
- 5d ago First seen · 10 lines scan A 642e89fe564b
memseek is an MCP server published in the GitHub repository memseekai/memseek (7 stars, last pushed 10d 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
groundmemory
Persistent, semantic memory for AI agents - mcp-native, local-first, framework-agnostic, production-ready. Runs locally from the groundmemory Python package.
honcho
Memory that reasons: continual learning for stateful agents. Better context, fewer tokens. Remote server at mcp.honcho.dev.
plur
Open, local-first engram memory for AI agents: read, correct, delete; shared over MCP. Runs locally from the @plur-ai/mcp npm package.
emulo
Mine your local AI coding session logs into a personal profile your agent loads before every task. Runs locally from the emulo Python package.
omega-memory
MCP server "omega-memory" as configured in omega-memory/omega-memory. Launched with python3.11 -m omega.server.mcp_server.
ori-memory
Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search. Runs locally from the ori-memory npm package.