M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionClaude MemPersistent cross-session memory for Claude Code and other agentsNPM Sentinel MCP ServerAI-powered NPM package analysis MCP server
FMRS50 / 100 · D79 / 100 · B
Reliability6 / 2012 / 20
Security and permissions5 / 2016 / 20
Maintenance14 / 2018 / 20
Documentation15 / 2018 / 20
Setup experience10 / 2015 / 20
Best for
  • Developers working on long-running projects with Claude Code (or other supported agents) who want memory to persist across sessions
  • Teams that want automatic summarization of agent tool activity instead of manual note-taking
  • Developers auditing NPM dependencies within AI workflows
  • Teams performing supply chain security assessments
  • Users of Claude Desktop, Cursor, or VS Code
Not for
  • Privacy-sensitive workflows where agent activity shouldn't be logged/stored by default without manually excluding content via <private> tags
  • One-off, single-session tasks that don't need cross-session context
  • Environments where installing a background worker service (Bun) and a Python package manager (uv) is not permitted
  • Projects outside the NPM ecosystem (e.g., pure Python/Go)
  • Environments without network access to deps.dev, OSV.dev, and the npm registry
  • Scenarios requiring maintenance by an official upstream vendor
Required permissions
  • Local file system read/write access for session logs, the SQLite database, and configuration (~/.claude-mem)
  • Ability to run and manage a background worker process (Bun) and a Python package manager (uv)
  • Network access for AI-based summarization/compression calls and optional cloud sync to cmem.ai
  • Access to Claude Code (or other agent) lifecycle hooks and tool-use transcripts in order to capture observations
  • Network access to the NPM registry and external services (deps.dev, OSV.dev, OpenSSF, npms.io, GitHub)
  • Read access to workspace lockfiles (pnpm-lock.yaml, package-lock., yarn.lock) for cache invalidation
Risks and side effects
  • Captures and stores all tool-use activity from agent sessions by default; sensitive content must be manually excluded using <private> tags
  • Runs a local HTTP worker service with a web viewer, which exposes stored memory data on the local machine/network
  • Optional cloud sync transmits memory data to a third-party service (cmem.ai)
  • Auto-installs additional runtimes (Bun, uv) when missing, widening the trust/supply-chain surface
  • The project is associated with a third-party cryptocurrency token (CMEM) that is not part of the core software — a separate financial-risk consideration, not evidence of malicious code
  • Third-party READMEs and changelogs are untrusted external content; they are wrapped in tags with _meta flags but should still be handled cautiously
  • Depends on availability and accuracy of external services
  • Batch requests are capped at 25 packages to prevent registry enumeration; larger sets require batching
  • Third-party open source project, not officially maintained by NPM or Anthropic
Supported clientsClaude Code, OpenCode, OpenClaw, Codex, Gemini, GitHub CopilotClaude Desktop, VS Code, Cursor
Tools319