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.

DimensionCodeInspectus MCP ServerLocal-first MCP security scanner for AI-generated appsGitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS75 / 100 · B76 / 100 · B
Reliability11 / 2013 / 20
Security and permissions18 / 2014 / 20
Maintenance13 / 2018 / 20
Documentation19 / 2017 / 20
Setup experience14 / 2014 / 20
Best for
  • Security-conscious developers building apps with AI agents like Claude Code, Cursor, or Codex
  • Individuals and small teams who want fully offline, local code scanning with no source upload
  • Teams mapping CWE-keyed findings to code-visible compliance controls
  • Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
  • Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
Not for
  • Teams seeking full compliance certification or runtime security proof (the tool explicitly does neither)
  • Deep audits requiring cross-file/whole-program dataflow or runtime mobile testing
  • Restricted environments that cannot run Node.js ≥22 or install cosign and engine binaries
  • Essential Eight assessments (only ~1 of 8 mitigations is code-evidenced)
  • Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
  • Environments with strict network isolation for private repos that can't reach the official remote endpoint
Required permissions
  • Reads project source and repository files (read-only; never edits or deletes your code)
  • Stores engine data and scan history under ~/.codeinspectus
  • Optionally writes one SBOM file (managed directory by default, or a chosen path)
  • Runs SHA-verified Opengrep/Gitleaks/Trivy binaries as local subprocesses
  • Reads git state for a git-safety recommendation; git operations require user approval and the tool never runs them itself
  • A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
  • Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
Risks and side effects
  • Prompt-injection detection is heuristic and immature; findings are worded "potential …" at medium confidence
  • Fixes are applied by your AI agent and need human review; the tool only reports and never edits code
  • Native rule coverage is deliberately narrow (mostly intrafile analysis); do not infer broader coverage than executed packs report
  • Compliance mappings are AI-drafted and maintainer-reviewed with 0 of 96 community-verified — not an audit
  • Engine binaries carry supply-chain risk, mitigated via SHA pinning, though setup/repair still downloads over the network
  • Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
  • In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
Supported clientsClaude Code, Cursor, VS Code, Codex, Windsurf, Cline, AiderClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools615