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.

DimensionRemem MCP ServerLocal-first persistent memory for coding agents: automatic capture, distillation, and recall.NPM Sentinel MCP ServerAI-powered NPM package analysis MCP server
FMRS66 / 100 · C79 / 100 · B
Reliability9 / 2012 / 20
Security and permissions12 / 2016 / 20
Maintenance14 / 2018 / 20
Documentation18 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Developers using Claude Code or Codex CLI long-term
  • Teams needing searchable, auditable, project-scoped memory
  • Users who want data to stay local (SQLite/SQLCipher)
  • Developers auditing NPM dependencies within AI workflows
  • Teams performing supply chain security assessments
  • Users of Claude Desktop, Cursor, or VS Code
Not for
  • Cursor users (v1 lacks session-init injection and automatic capture)
  • Anyone needing hosted or team-shared memory services
  • Users wanting a zero-install, no-local-binary solution
  • 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
  • Reads/writes the ~/.remem/ data directory and encrypted database
  • Modifies Claude Code / Codex / Cursor config files to register hooks and the MCP server
  • Calls the configured LLM API in the background for summarization and distillation (incur token costs)
  • Optional local REST API binds only to 127.0.0.1 and requires Bearer token auth
  • 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
  • Background memory summarization via external LLMs incurs ongoing token costs
  • Cursor integration is v1: automatic capture and session-init are not enabled, and config updates are not cross-file atomic
  • Stores project and user context; accidental secret-like content relies on built-in redaction scans and suppression tooling
  • Command enforcement (block mode) is Claude Code only; explicitly unsupported on Codex
  • 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, OpenAI Codex CLI, CursorClaude Desktop, VS Code, Cursor
Tools619