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/yogesh-joshi-0333/aimemWrote 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/yogesh-joshi-0333/aimem/aimem-mcp)<a href="https://agentmods.dev/mcp/yogesh-joshi-0333/aimem/aimem-mcp"><img src="https://agentmods.dev/badge/mcp/yogesh-joshi-0333/aimem/aimem-mcp/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/yogesh-joshi-0333/aimem/aimem-mcp"><img src="https://agentmods.dev/badge/mcp/yogesh-joshi-0333/aimem/aimem-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
aimem-mcp 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 9d 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
{ "aimem-mcp": { "command": "npx", "args": [ "-y", "aimem-mcp" ] } }
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.
- 9d ago First seen · 9 lines scan A 4a1ab3bdd655
aimem-mcp is an MCP server published in the GitHub repository yogesh-joshi-0333/aimem (0 stars, last pushed 8d 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
vestige
Local-first memory for AI agents that reaches backward to find a failure's root cause. Runs locally from the vestige-mcp-server npm package.
mnemon-memory
Universal long-term memory layer for AI agents via MCP. Runs locally from the mnemon-memory Python package.
norn
Norn MCP server with remember, recall, forget, and list tools over stdio. Runs locally from the @samad001z/norn-server npm package.
ultramemory
MCP server "ultramemory", hosted remotely at api.ultramemory.us, as configured in LogicLabsAI/ultramemory-mcp.
ultramemory-mcp
Cross-tool memory for your AI that recalls first every turn and admits when it doesn't know. Remote server at api.ultramemory.us.
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.