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.

DimensionMemory Journal MCP ServerPersistent memory and context handoff across AI sessions, with deep GitHub workflow integration.NPM Sentinel MCP ServerAI-powered NPM package analysis MCP server
FMRS70 / 100 · B79 / 100 · B
Reliability11 / 2012 / 20
Security and permissions15 / 2016 / 20
Maintenance13 / 2018 / 20
Documentation17 / 2018 / 20
Setup experience14 / 2015 / 20
Best for
  • Developers working on large projects who need persistent AI memory.
  • Teams want to integrate IDE agents and GitHub Copilot with shared context.
  • Engineers managing multiple repositories who need unified project intelligence.
  • Developers auditing NPM dependencies within AI workflows
  • Teams performing supply chain security assessments
  • Users of Claude Desktop, Cursor, or VS Code
Not for
  • Users who need only a trivial, stateless tool without any configuration.
  • Projects where persistent memory is explicitly not desired due to privacy concerns.
  • Environments that do not permit local file storage or database files.
  • 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 filesystem access limited by the `ALLOWED_IO_ROOTS` environment variable, used for import/export and Code Mode.
  • GitHub API access via the `GITHUB_TOKEN` to interact with issues, PRs, actions, etc.
  • Network access for remote HTTP/SSE transport, fetching embedding models, and OAuth token validation.
  • Read/write access to SQLite database files stored on the local machine.
  • 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
  • Misconfiguration of `ALLOWED_IO_ROOTS` could expose unintended file paths to the MCP tools.
  • A compromised GITHUB_TOKEN could allow unauthorized access to your repositories.
  • Code Mode executes sandboxed JavaScript, but there is always a risk if the sandbox is not perfectly isolated.
  • HTTP transport without proper authentication (e.g., OAuth or token) could allow unauthorized access.
  • Third-party embedding models may introduce supply chain risks.
  • 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 Desktop, CursorClaude Desktop, VS Code, Cursor
Tools6419