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/woshilaohei/mindcore-memory-mcp/mindcore-memorygit clone --depth 1 https://github.com/woshilaohei/mindcore-memory-mcpWrote 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/woshilaohei/mindcore-memory-mcp/mindcore-memory)<a href="https://agentmods.dev/mcp/woshilaohei/mindcore-memory-mcp/mindcore-memory"><img src="https://agentmods.dev/badge/mcp/woshilaohei/mindcore-memory-mcp/mindcore-memory.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
mindcore-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 4d 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
{
"mindcore-memory": {
"command": "uvx",
"args": [
"mindcore-memory"
],
"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.
- 4d ago First seen · 9 lines scan A 8be900fff2de
mindcore-memory is an MCP server published in the GitHub repository woshilaohei/mindcore-memory-mcp (1 stars, last pushed 2mo 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
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.
deepmem
Mem0-compatible persistent memory for AI agents: write facts once, recall them semantically. Remote server at deepmem.dev.
inspeximus
The agent memory that takes it back: correct a fact once and the retired value stops coming back, by key, with no LLM in the loop. Long-term memory for AI agents in a zero-dependency single file + MCP server, with value-ranked recall, per-type decay, consolidation, revert, and tamper-evident erasure. Runs locally from…
pseudolife-memory
MCP server "pseudolife-memory" as configured in Pseudogiant-xr/Pseudolife-MCP. Launched with C:\path\to\Pseudolife-MCP\.venv\Scripts\pseudolife-mcp.exe. Needs 3 environment variables to run.
pseudolife-mcp
Pseudolife persistent long-term memory for MCP-compatible coding agents. Runs locally from the pseudolife-mcp Python package.
hmem-mcp
Persistent 5-level hierarchical memory for AI agents. SQLite-backed, lazy-loaded. Runs locally from the hmem-mcp npm package. Needs 1 environment variable to run.