MCP Observatory
npm analyzed 13.6.1

claude-mem

v13.6.1
npm

Memory compression system for Claude Code - persist context across sessions

maintainer
thedotmack
license
Apache-2.0
first seen
2026-05-22
last seen
2026-06-17
releases · 30d
12
short id
risk 54/100 · heuristic grade
C elevated
  • capability exposureinferred+35
  • inherited (deps)attested+15
  • tool safetyinferred+12
  • trust mitigatorsmixed−8

attestedinferredmixed

The A–E grade is our heuristic synthesis — a "review this" prompt, not a verdict. Each factor is tagged by what backs it: attested (a verifiable record), reported (a third party's claim), or inferred (our own heuristic, e.g. permissions). See methodology.

graded 14m ago · see ecosystem CVEs →

risk trajectory 1 movements
  • C · 41 → C · 54
capability exposure grade factor +35
Inferred surface — each links to servers holding it:
vulnerabilities 0 CVEs

No known CVEs for this server.

inherited (deps) · grade factor +15

inherited via dependencies 3
HIGH
@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse via @modelcontextprotocol/sdk · 1 hop CVE-2026-25536 fixed in 1.26.0
HIGH
Anthropic's MCP TypeScript SDK has a ReDoS vulnerability via @modelcontextprotocol/sdk · 1 hop CVE-2026-0621 fixed in 1.25.2
HIGH
Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default via @modelcontextprotocol/sdk · 1 hop CVE-2025-66414 fixed in 1.24.0
tool safety 1 findings · grade factor +12
  1. highdangerous code

    suspicious bundled script in 1 file(s)

skills & danger signals npm-tarball
prompt-surface shipped agent-instruction files + hidden-content / dangerous-code findings — quoted from the analyzed source

analyzed v13.6.1 · analyzer v18 · 10h ago

skills & prompt files 17

danger signals2

embed badge readme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/npm:claude-mem/badge.svg)](https://mcpobservatory.com/servers/npm:claude-mem/security)

Heuristic, inferred signals — false positives (legitimately powerful tools, forks, language ports) are expected. Treat each as "review this", not a verdict. See the ecosystem-wide picture on the security hub, or the fleet security of thedotmack.