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/Vortx-AI/ememWrote 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/vortx-ai/emem/emem-emem)<a href="https://agentmods.dev/mcp/vortx-ai/emem/emem-emem"><img src="https://agentmods.dev/badge/mcp/vortx-ai/emem/emem-emem/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/vortx-ai/emem/emem-emem"><img src="https://agentmods.dev/badge/mcp/vortx-ai/emem/emem-emem.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
emem 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.
What it actually says
{
"emem": {
"type": "http",
"url": "https://emem.dev/mcp"
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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 · 6 lines scan A 1731bd3ce9b9
emem is an MCP server published in the GitHub repository Vortx-AI/emem (71 stars, last pushed yesterday), 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-09-17.
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.
veracium
Provenance-aware memory for AI agents. Runs locally from the veracium 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.
lain
High-performance knowledge graph MCP server for AI coding agents with semantic search. Runs locally from the @spuentesp/lain-mcp npm package.
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.
kiagent
Your mail, chats and documents indexed into a local SQLite corpus, served to AI clients over MCP. Remote server at {subdomain}.localkiagent.com.