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/LogicLabsAI/ultramemory-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/logiclabsai/ultramemory-mcp/ultramemory)<a href="https://agentmods.dev/mcp/logiclabsai/ultramemory-mcp/ultramemory"><img src="https://agentmods.dev/badge/mcp/logiclabsai/ultramemory-mcp/ultramemory/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/logiclabsai/ultramemory-mcp/ultramemory"><img src="https://agentmods.dev/badge/mcp/logiclabsai/ultramemory-mcp/ultramemory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ultramemory 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 12d 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
{
"ultramemory": {
"url": "https://api.ultramemory.us/mcp",
"headers": {
"Authorization": "Bearer um_YOUR_KEY"
}
}
}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.
- 12d ago First seen · 8 lines scan A 93e013af41c2
ultramemory is an MCP server published in the GitHub repository LogicLabsAI/ultramemory-mcp (1 stars, last pushed 1mo 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.
cmk
MCP server "cmk" as configured in LH8PPL/core-memory-kit. Launched with cmk mcp serve.
engram
MCP server "engram" as configured in rwnalds/engram. Runs in Docker (ghcr.io/rwnalds/engram:0.1.2).
aimem-mcp
Local-first, project-scoped MCP memory server for AI coding assistants. Runs locally from the aimem-mcp npm package.
krimto
Memory for AI coding agents — markdown in your own git, not a vendor database. Apache-2.0. Runs locally from the @krimto-labs/krimto npm package.
groundmemory
Persistent, semantic memory for AI agents - mcp-native, local-first, framework-agnostic, production-ready. Runs locally from the groundmemory Python package.