GitGuardian MCP Server
Find leaked secrets, triage GitGuardian incidents and create honeytokens.
Officialby GitGuardianHosted or on your computerChecked October 18, 2026
GitGuardian's MCP server lets Claude scan files for hardcoded credentials with GitGuardian's 500 plus detectors, then list, assign, tag and resolve the incidents in your workspace. It can also create and list honeytokens and open pull requests that remove secrets from monitored repositories, with the available tools set by the scopes of your token.
Who it is for
- Developers who want a secrets check on AI-written code
- Security and DevSecOps teams
- Teams already monitoring secrets with GitGuardian
Prompts to try
Once it is connected, ask in plain words. Claude decides when to use the server and asks before it changes anything important.
Scan this codebase for leaked secrets or API keys before I push.Show the open secret incidents assigned to me and explain how to fix each one.Create a honeytoken called staging-db and suggest where to place it.How to connect it
In Claude Code
claude mcp add --transport http gitguardian https://mcp.gitguardian.com/mcp
In the Claude desktop app
Customize > Connectors > + Add > Add custom connector, URL: https://mcp.gitguardian.com/mcp
Hosted address: https://mcp.gitguardian.com/mcp
Good to know
EU workspaces use https://mcp.eu1.gitguardian.com/mcp. The local stdio server runs with uvx and a personal access token.
Unlock the setup steps
Free. Leave your email once to open the setup steps for all 150 servers, and get the best new connectors each month.
How we checked it
Checked the GitGuardian/ggmcp repo (MIT, release 0.7.3 in 2026-10) and its README for the hosted, self-hosted and local setups; the hosted endpoint answers with an OAuth challenge.
Source: github.com/GitGuardian/ggmcp