npm/@modelcontextprotocol/server-memory
graded version 2026.1.26 · litmus-v6 · 2026-06-24
Adoption 71/100 · 292K npm/mo · as of 2026-06-26
- C-01 Tool-output injection
- pass
- C-02 Permission / egress overreach
- pass
- C-03 Sensitive-data handling
- pass
- C-04 Adversarial-input handling
- pass
tool-defs fingerprint · 0x09eab2…30eb6
Why A: All four categories passed. No injection, no data leak, no egress overreach, and adversarial inputs were handled cleanly (A means no overreach, not no network).
Adoption signals
The 71 / 100 adoption score blends the raw signals below — downloads, stars, dependents and release velocity — normalized across every tracked server. It measures reach, not safety; the litmus grade is the safety verdict. See the methodology.
- npm downloads (30d)
- 291,675
- GitHub stars
- 87,726
- Forks
- 11,080
- Contributors
- 428
- Dependents (deps.dev)
- 11
- Last published
- 2026-01-27
Reproduce this grade
The harness is open and deterministic. Re-run it against the same server and compare the grade and fingerprint — a false grade is falsifiable, not merely disputable.
npx -p @polygraphso/litmus polygraphso-litmus npm/@modelcontextprotocol/server-memoryEmbed this badge
Drop it in a README, docs site, or package page. It always shows the current published grade and links back here.
[](https://polygraph.so/mcp/npm/@modelcontextprotocol/server-memory)<a href="https://polygraph.so/mcp/npm/@modelcontextprotocol/server-memory"><img src="https://polygraph.so/api/badge?server=npm/@modelcontextprotocol/server-memory" alt="polygraph grade"></a>[](https://polygraph.so/mcp/npm/@modelcontextprotocol/server-memory)