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/majiayu000/rememWrote 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/majiayu000/remem/remem)<a href="https://agentmods.dev/mcp/majiayu000/remem/remem"><img src="https://agentmods.dev/badge/mcp/majiayu000/remem/remem/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/majiayu000/remem/remem"><img src="https://agentmods.dev/badge/mcp/majiayu000/remem/remem.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
remem 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
{
"remem": {
"command": "npx",
"args": [
"-y",
"@remem-ai/remem"
],
"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.
- 1mo ago First seen · 10 lines scan A 006e72bc75ab
remem is an MCP server published in the GitHub repository majiayu000/remem (34 stars, last pushed yesterday), 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-30.
Other mcp servers, from other repositories
mcp-memory-sqlite
SQLite-based persistent memory tool for MCP with text search. Runs locally from the mcp-memory-sqlite npm package.
vulcanus
A validated Markdown memory vault your coding agent can recall, project by project. Runs locally from the @sunsato/vulcanus npm package.
ai-memory
Turn editor chat history (Cursor, Claude Code, Windsurf, Copilot) into typed Markdown decisions + AGENTS.md rules — local-first, git-trackable, zero remember() calls. Runs locally from the ai-memory-cli npm package.
ai-journal-mcp
Journal engine and MCP server: capture, structure, and ask questions of your work journals. Runs locally from the ai-journal-mcp Python package.
seeklink
Local semantic search CLI and optional MCP stdio server for Markdown vaults. BM25 + vector + wikilink graph + metadata via RRF. Native CJK. Runs locally from the seeklink Python package.
memorywhale
MCP server "memorywhale" as configured in wuisabel-gif/MemWhale. Launched with mw-mcp.