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/YeomYuJun/remote-memory-mcp-serverWrote 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/yeomyujun/remote-memory-mcp-server/remote-memory-mcp)<a href="https://agentmods.dev/mcp/yeomyujun/remote-memory-mcp-server/remote-memory-mcp"><img src="https://agentmods.dev/badge/mcp/yeomyujun/remote-memory-mcp-server/remote-memory-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/yeomyujun/remote-memory-mcp-server/remote-memory-mcp"><img src="https://agentmods.dev/badge/mcp/yeomyujun/remote-memory-mcp-server/remote-memory-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
remote-memory-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 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
{ "remote-memory-mcp": { "command": "npx", "args": [ "-y", "remote-memory-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.
- 1mo ago First seen · 9 lines scan A 8fe0e8de1a98
remote-memory-mcp is an MCP server published in the GitHub repository YeomYuJun/remote-memory-mcp-server (0 stars, last pushed 5mo 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
agent-memory-mcp-server
Persistent memory for AI agents — store, retrieve, search knowledge across sessions. Runs locally from the @aiagentkarl/agent-memory-mcp-server npm package.
memlab
MCP server "memlab" as configured in facebook/memlab. Runs packages/mcp-server/bin/memlab-mcp.js with node. Needs 1 environment variable to run.
memorix
Local-first project memory with legacy MCP and 2026 discovery compatibility. Runs locally from the memorix npm package.
prism-mcp
Persistent session memory for AI coding agents that never leaves your machine — including the on-device model that reasons over it. Restores your prior decisions, open TODOs, and changed files across sessions; adds associative recall of related past work. Runs locally from the prism-mcp-server npm package. Needs 1…
hypermnesia-mcp
Scientifically-grounded memory system based on computational neuroscience research. Runs locally from the hypermnesia-mcp Python package.
ai-memory
MCP server "ai-memory" as configured in alphaonedev/ai-memory-mcp. Runs in Docker (ghcr.io/alphaonedev/ai-memory:0.5.1). Needs 1 environment variable to run.