Is Memory safe and trustworthy?

tashan scores Memory on public evidence — tashan score 96.0/100, it is currently active, no known advisories against the current release. 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?

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

Who maintains Memory?

30 GitHub contributors, published by Anthropic, source: modelcontextprotocol/servers.

‹ The Index

Memory

npm ✓ Anthropic · official

MCP server for enabling memory for Claude through a knowledge graph

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: Files & Memory — see all ranked ›

Work: Knowledge management

Who it is for: Operations · Researcher

Install (Claude Code):

claude mcp add memory -- npx -y @modelcontextprotocol/server-memory

Not graded: shares its documentation with 3 other capabilities. A grade read off another project’s document would borrow its credit, or its blame.

tashan score: 96.0
Adoption: 152k/wk
Upkeep: 93.0
Freshness: 95.0
Evidence coverage: 100% of the inputs this score can use
Health: active
GitHub stars: 88,810
Contributors: 30
License: NOASSERTION

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 2026.8.31 — and the 92 packages it installs

No access inferred from declared dependenciesnothing it depends on reaches files, shell or network. This reads declarations only — built-in APIs are invisible to it, so absence of a declaration is not absence of access

Signed build provenancepublished from public CI with an attestation

What changed recently

2026-09-13 the tashan score for @modelcontextprotocol/server-memory rose to 96.0, from 91.0 Upkeep, freshness or adoption moved enough to change how this measures.
2026-09-13 @modelcontextprotocol/server-memory published 2026.8.31, was 2026.7.4 A new release is available.

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 2 changes to Memory 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-modelcontextprotocol-server-memory.svg)](https://tashan.sh/capability/pkg-modelcontextprotocol-server-memory.html)

npm ↗ · source ↗ · pkg:@modelcontextprotocol/server-memory

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?