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.

DimensionCKBKnow your code. Change it safely. Ship with confidence.NPM Sentinel MCP ServerAI-powered NPM package analysis MCP server
FMRS43 / 100 · D79 / 100 · B
Reliability5 / 2012 / 20
Security and permissions8 / 2016 / 20
Maintenance6 / 2018 / 20
Documentation12 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • Developers using AI assistants who want them to have precise code awareness
  • Teams with large codebases needing efficient navigation
  • Anyone doing refactoring who wants to understand impact
  • Code reviewers who need the full picture of changes
  • Tech leads tracking architectural health over time
  • Developers auditing NPM dependencies within AI workflows
  • Teams performing supply chain security assessments
  • Users of Claude Desktop, Cursor, or VS Code
Not for
  • Dynamic dispatch or runtime behavior analysis (use a debugger)
  • Generated code that isn't indexed
  • Code generation, linting, or formatting
  • Cross-repo calls (use federation for this)
  • 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
  • Read access to codebase files and git history
  • Generate and maintain SCIP indexes (local files)
  • Execute the MCP server process via stdio
  • Optionally create API tokens for authentication when using the index server
  • Optional network access for HTTP API server
  • 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
  • SCIP indexes may become stale, leading to inaccurate references or impact analysis
  • Indexing large codebases can be time and disk intensive
  • Dynamic or reflective code may be misanalyzed
  • Requires installing SCIP indexers, and language support quality varies
  • Inputs are not sanitized, so verify outputs
  • 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, Claude Code, Cursor, Windsurf, VS Code, OpenCode, GrokClaude Desktop, VS Code, Cursor
Tools3919