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.

DimensionRepowiseCodebase intelligence layer: code health scores, auto-generated docs, git analytics, dead code detection, and architectural decisions for AI agents and humans.NPM Sentinel MCP ServerAI-powered NPM package analysis MCP server
FMRS66 / 100 · C79 / 100 · B
Reliability9 / 2012 / 20
Security and permissions13 / 2016 / 20
Maintenance15 / 2018 / 20
Documentation16 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Developers who want deep codebase insights locally without uploading code to the cloud.
  • Teams needing pre-merge change-risk scoring and code health metrics.
  • Those looking to provide structured context to AI coding agents to save tokens and improve accuracy.
  • Developers auditing NPM dependencies within AI workflows
  • Teams performing supply chain security assessments
  • Users of Claude Desktop, Cursor, or VS Code
Not for
  • Users wanting a fully managed cloud service without any local installation (use hosted repowise.dev).
  • Slow index times may be a concern for large repos (e.g., 366s for Django), so not ideal if you need instant setup.
  • Non-technical users unfamiliar with command-line tools and MCP configuration.
  • 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 the specified repository's file system (mandatory).
  • Optional: send code snippets to LLM providers for prose generation (if AI-generated docs enabled).
  • Optional: write access to Git or GitHub for PR bot comments if installed.
  • Read access to Git history for analysis.
  • 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
  • Privacy: while local-first, enabling LLM prose or using hosted versions sends code to third parties.
  • Performance: indexing large repositories can take minutes, slowing initial setup.
  • Reliance on Python environment and pip; potential dependency conflicts.
  • Accuracy: heuristic-based scores and generated docs may be imperfect, especially for less-supported languages.
  • 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, Codex, Cursor, VS CodeClaude Desktop, VS Code, Cursor
Tools1019