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.

DimensionGitGuardian MCP ServerBring GitGuardian secret detection and incident management into your AI agentGitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS52 / 100 · D76 / 100 · B
Reliability8 / 2013 / 20
Security and permissions12 / 2014 / 20
Maintenance11 / 2018 / 20
Documentation13 / 2017 / 20
Setup experience8 / 2014 / 20
Best for
  • Teams already using GitGuardian SaaS (US/EU) or a self-hosted instance
  • Developers who want secret scanning, incident triage, and remediation inside their IDE or chat client
  • Teams that want to automate secret remediation via pull requests
  • Users of MCP clients that support type: http and can complete an OAuth flow
  • CI/CD, scripts, or airgapped environments that need local stdio with a PAT
  • 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 who do not use GitGuardian and do not want to connect to its API
  • Users limited to older MCP clients without type: http support who cannot use the local stdio fallback
  • Users expecting the server to work with no authentication or scope configuration
  • Hosted-service users who do not want requests to transit mcp.gitguardian.com (they should self-host instead)
  • 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 GitGuardian access token (OAuth or PAT); the exposed tool set is determined by the token's OAuth scopes
  • Local stdio mode uses the GITGUARDIAN_PERSONAL_ACCESS_TOKEN environment variable
  • Self-hosted OAuth proxy mode proxies /authorize, /token, and /register to your GitGuardian dashboard
  • PAT lifetime defaults to 30 days and is configurable via GITGUARDIAN_TOKEN_LIFETIME
  • The server defaults to read-only-leaning permissions
  • 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
  • MCP servers are an emerging technology; agents act on your behalf and under your responsibility
  • In hosted mode, requests transit mcp.gitguardian.com in addition to api.gitguardian.com
  • Token scopes determine which tools the agent can use; overly broad scopes increase blast radius
  • Code-fix automation opens pull requests, so agent actions should be reviewed
  • Browser-driven OAuth in stdio mode is deprecated and stores the PAT on disk; that code path will be removed in a future release
  • 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 clientsCursor, Claude Desktop, Claude.ai, Windsurf, ZedClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools415