Memanto is a companion memory agent that manages what other AI agents remember, including durable facts, preferences, conflicts, stale information, and which agents should receive updates. It is for teams running multiple agents that need coordinated memory across conversations, platforms, and storage systems.
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/moorcheh-ai/memantoWrote 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/moorcheh-ai/memanto/mcp-memanto)<a href="https://agentmods.dev/mcp/moorcheh-ai/memanto/mcp-memanto"><img src="https://agentmods.dev/badge/mcp/moorcheh-ai/memanto/mcp-memanto/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/moorcheh-ai/memanto/mcp-memanto"><img src="https://agentmods.dev/badge/mcp/moorcheh-ai/memanto/mcp-memanto.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
memanto 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
{
"memanto": {
"command": "uvx",
"args": [
"memanto-mcp"
],
"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 81219aff2e7c
memanto is an MCP server published in the GitHub repository moorcheh-ai/memanto (2,344 stars, last pushed today), 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-10-27.
Other mcp servers, from other repositories
zenbrain
Agent memory: working, episodic, semantic, procedural and core layers. Local SQLite, no account. Runs locally from the @zensation/mcp npm package. Needs 2 environment variables to run.
veracium
Provenance-aware memory for AI agents. Runs locally from the veracium Python package. Needs 3 environment variables to run.
goodmem
GoodMem MCP server — exposes GoodMem API as MCP tools. Runs locally from the @pairsystems/goodmem-mcp npm package.
deepmem
Mem0-compatible persistent memory for AI agents: write facts once, recall them semantically. Remote server at deepmem.dev.
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.
memoweft
Portable AI memory as MCP tools: five reads and three controlled writes. Runs locally from the @memoweft/mcp-server npm package. Needs 1 environment variable to run.