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/sylweriusz/mcp-neo4j-memory-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/sylweriusz/mcp-neo4j-memory-server/graph-memory)<a href="https://agentmods.dev/mcp/sylweriusz/mcp-neo4j-memory-server/graph-memory"><img src="https://agentmods.dev/badge/mcp/sylweriusz/mcp-neo4j-memory-server/graph-memory.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
graph-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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- graph-memory — 100% identical, 0 lines differ
What it actually says
{
"graph-memory": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"mcp-neo4j-memory"
],
"env": {
"NEO4J_URI": "bolt://localhost:7687",
"NEO4J_USERNAME": "neo4j",
"NEO4J_PASSWORD": "password",
"NEO4J_DATABASE": "neo4j"
}
}
}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.
- 8d ago First seen · 17 lines scan A e81fdd972d31
graph-memory is an MCP server published in the GitHub repository sylweriusz/mcp-neo4j-memory-server (31 stars, last pushed 1y 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
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-memory-sqlite
SQLite-based persistent memory tool for MCP with text search. Runs locally from the mcp-memory-sqlite npm package.
titen-memory
Evidence-grounded agent memory with mandatory provenance, on local SQLite or Cloudflare D1. Runs locally from the titen-memory npm package. Needs 2 environment variables to run.
acmi-mcp
Persistent agent memory via ACMI — Profile/Signals/Timeline. 16 tools on Upstash Redis. Runs locally from the @madezmedia/acmi-mcp npm package. Needs 2 environment variables to run.
amnesic
The MCP server with the most ironic name in the registry — persistent semantic memory for your SQL databases. Runs locally from the amnesic Python package.
claudedesktop-warnerco-schematica
MCP server "claudedesktop-warnerco-schematica" as configured in timothywarner-org/context-engineering. Runs locally from the warnerco-mcp Python package. Needs 1 environment variable to run.