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/4DA-Systems/4DAWrote 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/4da-systems/4da/memory)<a href="https://agentmods.dev/mcp/4da-systems/4da/memory"><img src="https://agentmods.dev/badge/mcp/4da-systems/4da/memory/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/4da-systems/4da/memory"><img src="https://agentmods.dev/badge/mcp/4da-systems/4da/memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
memory 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What else .mcp.json configures
This page is one entry in a file that holds 4. 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.
- 1mo ago First seen · 11 lines scan A f49eaef1d991
memory is an MCP server published in the GitHub repository 4DA-Systems/4DA (2 stars, last pushed today), with no licence file. 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
expo
MCP server "expo", hosted remotely at mcp.expo.dev, as configured in fastrepl/anarlog.
code-review-graph
MCP server "code-review-graph" as configured in varun29ankuS/shodh-memory. Runs code_review_graph with python.
ling-mem
MCP server "ling-mem", hosted remotely, as configured in linggen/linggen-memory.
remem
Local-first automatic memory for Claude Code and Codex: capture, distill, recall from SQLite. Runs locally from the @remem-ai/remem npm package.
mcp
Model Context Protocol server for Citadel: encrypted memory as MCP tools. Runs locally from the citadeldb-mcp Python package. Needs 1 environment variable to run.
context-server
Lightweight MCP server for semantic search over organizational markdown. Runs locally from the context-server Python package.