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 agentMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS52 / 100 · D79 / 100 · B
Reliability8 / 2012 / 20
Security and permissions12 / 2018 / 20
Maintenance11 / 2016 / 20
Documentation13 / 2018 / 20
Setup experience8 / 2015 / 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
  • Engineering teams scaling AI coding agents while controlling spend
  • Platform teams that need auditable, rollback-aware agent execution records
  • Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
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)
  • Developers who just want a simple code-completion helper without run governance
  • Teams unwilling to accept local JSONL run records with HMAC signing
  • Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
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
  • Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
  • Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
  • Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
  • Execution of user-configured verifier commands (e.g. npm test)
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
  • Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
  • Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
  • Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
  • Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
Supported clientsCursor, Claude Desktop, Claude.ai, Windsurf, ZedClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools40