Is Memory Graph safe and trustworthy?

tashan scores Memory Graph on public evidence — tashan score 50.0/100, it is currently active, note: a single primary maintainer (bus-factor risk), no known advisories against the current release, its declared dependencies reach: database. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Memory Graph?

In Claude Code: run `claude mcp add memory-graph -- npx -y mcp-memory-graph`. In Cursor / Claude Desktop, add it to mcp.json / claude_desktop_config.json.

Who maintains Memory Graph?

source: YonasValentin/mcp-memory-graph.

‹ The Index

Memory Graph

npm

Local-first memory MCP server for Claude Code and any MCP client: hybrid vector + knowledge-graph search, bi-temporal recall, Obsidian sync. Runs 100% on your machine, $0/token.

Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code (installable)
installable: each client documents how to load an MCP server of this type — that is the client's promise, not a claim verified against this capability

Category: AI & Agents — see all ranked ›

Work: Knowledge management · Retrieval systems

Who it is for: Operations · Researcher · AI engineer

Install (Claude Code):

claude mcp add memory-graph -- npx -y mcp-memory-graph

deep

“49 tools documented (memory_store, memory_search, memory_get…); 26 worked examples; setup and auth covered; states a limit — “The trade-off is honest: a single-process…”; read with 1 linked doc(s)”

This grade is wrong ›

tashan score: 50.0
Instruction depth: 99.0 (deep — documents every tool, with worked examples, setup and a stated limitation)
Adoption: 141/wk
Upkeep: 65.0
Freshness: 78.0
Evidence coverage: 100% of the inputs this score can use
Health: active
License: PolyForm-Noncommercial-1.0.0

Security audit

Every finding is shown in full — which advisory, the version that fixes it, and the exact command run at install time. Nothing in this audit is behind a licence.

No known advisoriesclearchecked against OSV for 2.10.3 — this package, not its dependency tree

Connects to databasesfrom declared dependencies

Signed build provenancepublished from public CI with an attestation

What changed recently

2026-08-10 mcp-memory-graph now reaches database Its declared dependencies reach further into your machine than they did before.

You are reading this because you came looking. tashan Pro gives tashan doctor the history behind it, so a run over your own config says which of YOURS moved.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

We recorded 1 change to Memory Graph in the last 45 days. Pro tells you on the day — for the servers in your own config, not the ones you thought to look up.

The whole series behind any row, back to the first day we measured it
The replacement, named — not just the news that something died
tashan doctor over your own config, on your own machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/pkg-mcp-memory-graph.svg)](https://tashan.sh/capability/pkg-mcp-memory-graph.html)

npm ↗ · source ↗ · pkg:mcp-memory-graph

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-09-13 · scorer s5 · how · something wrong here?