← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionBugsy MCP ServerAutomatically analyze and remediate code vulnerabilitiesGitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS48 / 100 · D76 / 100 · B
Reliability7 / 2013 / 20
Security and permissions7 / 2014 / 20
Maintenance8 / 2018 / 20
Documentation14 / 2017 / 20
Setup experience12 / 2014 / 20
Best for
  • Developers using local Git repositories and AI coding assistants
  • Teams that want rapid review of modified, added, or staged files
  • Users seeking automated remediation suggestions through Mobb
  • 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
  • Users needing standalone vulnerability detection
  • Users without a Mobb API key or local Git repository
  • Users needing unrestricted, long-term analysis of private repositories
  • 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
  • Requires a Mobb API_KEY
  • Requires access to the specified local Git repository and changed files
  • Uploads changed files for analysis
  • Can use API_URL to target a custom Mobb service URL
  • 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
  • Code changes are uploaded to Mobb for analysis
  • When automatic fixing is enabled, fixes may be applied automatically and should be reviewed before committing
  • The community edition primarily analyzes public GitHub repositories, with private repository access limited in time
  • Results depend on upstream SAST findings; Bugsy does not detect vulnerabilities itself
  • 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, CursorClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools115