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.

DimensionCtxlintLint your AI agent context files (CLAUDE.md, AGENTS.md, etc.) against your actual codebase.NPM Sentinel MCP ServerAI-powered NPM package analysis MCP server
FMRS57 / 100 · C79 / 100 · B
Reliability9 / 2012 / 20
Security and permissions11 / 2016 / 20
Maintenance9 / 2018 / 20
Documentation15 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Developers and teams using AI coding assistants (e.g., Claude Code, Cursor).
  • Projects with multiple context files and complex structure.
  • Teams that need to maintain accurate agent context.
  • Environments with strict security requirements for MCP configs (e.g., no hardcoded API keys).
  • Developers auditing NPM dependencies within AI workflows
  • Teams performing supply chain security assessments
  • Users of Claude Desktop, Cursor, or VS Code
Not for
  • Projects that don't use AI context files.
  • Simple, solo projects where files change infrequently (may be overkill).
  • Non-critical projects that don't require strict context maintenance.
  • 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 context and config files in the project directory (e.g., CLAUDE.md, .mcp.json).
  • Optionally reads user-level config files (e.g., ~/.claude/settings.json) and global MCP configs (with --mcp-global).
  • Optionally reads agent history and memory files in the user's home directory (e.g., ~/.claude/history.jsonl) when session or skill audits are enabled.
  • Optionally writes context files to fix broken paths when --fix is enabled.
  • 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
  • Auto-fix (--fix) may modify files unexpectedly; preview with --fix-dry-run and review changes.
  • Session audit accesses sensitive history files in the home directory; enable only in trusted environments.
  • The tool reads config and context files that may contain secrets (e.g., API keys); ensure access is controlled.
  • Redundancy checks may produce false positives as inferred content may vary by context.
  • 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, GitHub CopilotClaude Desktop, VS Code, Cursor
Tools719