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.

DimensionCodacy MCP ServerQuery Codacy's code quality, security, and coverage analysis via MCP.NPM Sentinel MCP ServerAI-powered NPM package analysis MCP server
FMRS56 / 100 · C79 / 100 · B
Reliability8 / 2012 / 20
Security and permissions10 / 2016 / 20
Maintenance10 / 2018 / 20
Documentation15 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Teams already using the Codacy platform for code quality and security management
  • Developers who want Codacy analysis results directly inside Cursor, Windsurf, VS Code Copilot, or Claude Desktop
  • Teams that want to check pull request issues and coverage as part of an AI coding assistant workflow
  • Developers auditing NPM dependencies within AI workflows
  • Teams performing supply chain security assessments
  • Users of Claude Desktop, Cursor, or VS Code
Not for
  • Users without a Codacy account, or who don't intend to register repositories with Codacy
  • Scenarios requiring generic static analysis or security scanning independent of the Codacy platform
  • Restricted environments where Node.js/npx or the Codacy CLI cannot be installed
  • 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
  • Accesses organizations and repositories the user has permission to on Codacy, via the CODACY_ACCOUNT_TOKEN personal account token
  • Reads repository analysis results, issues, coverage, security findings, and pull request data
  • Executes the Codacy CLI locally to analyze code on the filesystem (attempts automatic installation of the CLI)
  • 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
  • CODACY_ACCOUNT_TOKEN is a sensitive credential; if leaked it could grant access to all Codacy organizations and repositories tied to the account
  • codacy_cli_analyze installs and runs the Codacy CLI locally, which involves executing a third-party binary
  • Security-related tools (SRM items) surface repository vulnerability and secret-scanning results, so access and downstream handling should be controlled
  • The server depends on network access to the Codacy API; misconfigured credentials could expose data to unintended clients
  • 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, Cursor, Windsurf, GitHub CopilotClaude Desktop, VS Code, Cursor
Tools2319