Claude Memory (maydali28) MCP Server
claude-memory-mcp
PyPI
v0.3.0
Published by maydali28 — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Persistent memory MCP server for Claude Code — never lose context again
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
low Shell/command execution in packaging/dev tooling (tests/unit/test_hooks.py)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/unit/test_hooks.py:16`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: None: result = subprocess.run( [sys.executable, str(HOOKS_DIR / "pre_compact_save.py")],
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server tests/unit/test_hooks.py
Tools 24
Each tool and what it can reach — statically extracted from the published source.
memcp_chunk_contextno sensitive capabilitymemcp_clear_contextno sensitive capabilitymemcp_consolidateno sensitive capabilitymemcp_consolidation_previewno sensitive capabilitymemcp_filter_contextno sensitive capabilitymemcp_forgetno sensitive capabilitymemcp_get_contextno sensitive capabilitymemcp_graph_statsno sensitive capabilitymemcp_inspect_contextno sensitive capabilitymemcp_list_contextsno sensitive capability
Show 14 more tools ↓
memcp_load_contextno sensitive capabilitymemcp_peek_chunkno sensitive capabilitymemcp_pingno sensitive capabilitymemcp_projectsno sensitive capabilitymemcp_recallno sensitive capabilitymemcp_reinforceno sensitive capabilitymemcp_relatedno sensitive capabilitymemcp_rememberno sensitive capabilitymemcp_restoreno sensitive capabilitymemcp_retention_previewno sensitive capabilitymemcp_retention_runno sensitive capabilitymemcp_searchno sensitive capabilitymemcp_sessionsno sensitive capabilitymemcp_statusno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (24 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.3.0 latest |
A 99/100 | 1 | 1.13.0 | 2026-08-25 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan claude-memory-mcp --online --registry pypiOther implementations of Claude Memory 4
Independent packages implementing the same tool, scanned with the same engine. Compare all 5 side by side →
Persistent memory system for Claude Code CLI using Obsidian-compatible markdown
MCP Server for syncing Claude Code memories across devices via GitHub
Enterprise-grade Claude Memory MCP Server - persistent, intelligent memory for Claude Code
Security scan results for the Claude Memory (npm) MCP server.
More in AI, Memory & Reasoning
FDA device & vehicle recall risk for AI agents: recall history, MAUDE trend, risk score.
Open-source MCP server exposing Agent402.Tools' catalog — 500+ strong: 400+ self-hostable tools + 100 multi-tool skill packs (security-audit, trend-analysis, structured-scrape, decode-blob, forecasting-bake-off) for AI agents — browser, web search & answe
Zero-dependency MCP server that gives AI agents a self-updating project memory in AGENTS.md. Returns merge instructions instead of mutating state, so every change is a reviewable diff.
MCP Apps UI resources and server helpers for n8n
MCP server providing comprehensive access to BookStack knowledge management system
MCP server for tracking achievements with STAR methodology