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-linggengit 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-linggen)<a href="https://agentmods.dev/mcp/linggen/linggen-memory/linggen-linggen"><img src="https://agentmods.dev/badge/mcp/linggen/linggen-memory/linggen-linggen.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
linggen 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
{
"linggen": {
"type": "http",
"url": "http://${LINGGEN_HOST:-127.0.0.1}:${LINGGEN_PORT:-9527}/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 1583a686e76e
linggen is an MCP server published in the GitHub repository linggen/linggen-memory (108 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.
densely
Lossless context compression for LLMs: 2x-8x fewer tokens, byte-exact reconstruction, sha256-verified. Runs locally from the densely Python package.
memshelf-mcp
Working-memory shelf for AI agents — offload closed topics to a docshelf shelf as digest-indexed episodes, recall by index. Runs locally from the memshelf-mcp Python package.
session-migrator
MCP server "session-migrator" as configured in liangyuan0219/session-migrator. Runs locally from the session-migrator Python package.
whats-loaded-mcp
What fills your agent's context window before a session starts: skill descriptions, memory files. Runs locally from the whats-loaded-mcp npm package.