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.
npx agentmods add mcp/linggen/linggen-memory/linggen-ling-memgit clone --depth 1 https://github.com/linggen/linggen-memoryWrote 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/linggen/linggen-memory/linggen-ling-mem)<a href="https://agentmods.dev/mcp/linggen/linggen-memory/linggen-ling-mem"><img src="https://agentmods.dev/badge/mcp/linggen/linggen-memory/linggen-ling-mem.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
ling-mem 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 6d 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
{
"ling-mem": {
"type": "http",
"url": "http://${LING_MEM_HOST:-127.0.0.1}:${LING_MEM_PORT:-9528}/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.
- 6d ago First seen · 6 lines scan A c552250f18c0
ling-mem is an MCP server published in the GitHub repository linggen/linggen-memory (109 stars, last pushed 2d 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-30.
Other mcp servers, from other repositories
nexusmem
Local-first memory for AI coding agents: shell history with exit codes, git diffs, docs, MCP. Runs locally from the nexusmem npm package.
context-compress
MCP server "context-compress" as configured in Open330/context-compress. Runs ./dist/index.js with node.
lithium-kb
Fast, in-memory structured markdown knowledge base (.agent-kb/) with 2D neural graph visualization, live SSE activity stream, and MCP stdio integration. Runs locally from the @liulinnuha/lithium-kb npm package.
context-guardian-mcp
MCP server + proxy that cuts cloud LLM costs 36-42% by indexing context locally with Ollama and giving agents precision retrieval tools instead of raw dumps. Runs locally from the context-guardian-mcp npm package.
memorywhale
MCP server "memorywhale" as configured in wuisabel-gif/MemWhale. Launched with mw-mcp.
remem
Local-first automatic memory for Claude Code and Codex: capture, distill, recall from SQLite. Runs locally from the @remem-ai/remem npm package.