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/sovseal/coreWrote 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/sovseal/core/sovseal-memory)<a href="https://agentmods.dev/mcp/sovseal/core/sovseal-memory"><img src="https://agentmods.dev/badge/mcp/sovseal/core/sovseal-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/sovseal/core/sovseal-memory"><img src="https://agentmods.dev/badge/mcp/sovseal/core/sovseal-memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
sovseal-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.
Copies of this mod
1 near-identical copy found in the catalogue:
- sovseal-memory — 100% identical, 0 lines differ
What it actually says
{ "sovseal-memory": { "command": "npx", "args": [ "-y", "@sovseal/mcp-server" ], "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.
- 1mo ago First seen · 10 lines scan A 9bcf741afd54
sovseal-memory is an MCP server published in the GitHub repository sovseal/core (7 stars, last pushed 2mo 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
mcp-memory-server
Hosted memory for AI agents that learns from outcomes — one key across Claude, Cursor & ChatGPT. Runs locally from the @mnemoverse/mcp-memory-server npm package. Needs 2 environment variables to run.
local-memory-mcp
Persistent local AI memory. SQLite + FTS5 + vector search, knowledge graph. No cloud, no API keys. Runs locally from the @studiomeyer/local-memory-mcp npm package. Needs 4 environment variables to run.
alice
Alice: the continuity layer for AI agents. Local-first memory with provenance, open loops, resumption, and review-governed writes. Runs locally from the alice-memory Python package.
membrain
Self-hosted AI memory ledger. You and your agents share one memory store over MCP — one SQLite file, web UI, REST, works offline. Runs locally from the membrain-mcp npm package.
strata
Self-hosted AI memory server. Persistent memory on your hardware, not the cloud. Runs locally from the strata-mcp-server npm package. Needs 2 environment variables to run.
omega-obsidian
Persistent semantic memory MCP server for Obsidian vaults. Powered by OMEGA. Runs locally from the omega-obsidian Python package.