GitGuardian MCP. Automate Breach Detection and Incident Response.

Q: Can GitGuardian MCP manage my team's security roles?

Yes, you use tools like listteams or listmembers to see who is in the system. You can then use assignsecretincident to assign ownership of a breach to specific team members.

Q: Is GitGuardian MCP better than just looking at audit logs?

Theoretically, yes. While you can use listauditlogs to see general activity, this MCP connects that log data directly to specific secret incidents and team responsibilities, giving context.

Q: How do I clean up old or false positive leaks with GitGuardian MCP?

First, you check the details using getsecretincident. Once confirmed as benign or fixed, you use ignoresecretincident to mark it in the system, keeping your active incident list clean.

GitGuardian connects your workspace to any AI agent, letting you manage secret leaks and audit security without leaving your flow. Use it to scan code snippets, list active incidents, deploy decoy credentials (honeytokens), and check compliance logs instantly via natural conversation.

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

See Vinkius in Action

Give Claude and any AI agent real-world access

Scan Code for Secrets

You feed the MCP code snippets or documents and it finds sensitive data like private keys, tokens, and passwords.

Manage Breaches and Incidents

You can list active leaks, get full details on a specific secret incident, and resolve them when remediation is complete.

Deploy Decoy Credentials

The MCP allows you to create honeytokens—fake credentials placed in your system that alert you if they are ever used by an unauthorized party.

Audit Compliance and Activity

You retrieve detailed logs of workspace activity, track who did what, and ensure the environment meets security policy requirements.

Organize Security Teams

The MCP helps you manage team memberships and API tokens to coordinate security efforts across different groups in your company.

Ask an AI about this

Waiting for input…

AI Agent

What AI agents can do with GitGuardian: 49 Tools for Code Security

These tools allow you to perform every level of security operations—from listing team members to scanning content for secrets—all through natural language conversation.

Make your AI actually useful.

Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.

Start using GitGuardian MCP

Assign Secret Incident

This tool lets you assign ownership of an existing secret leak incident to a specific team member.

Bulk Prefix Lookup

It performs a bulk lookup for common honeytoken hashes, helping confirm if a decoy...

Create Custom Tag

You create specific tags to categorize or label security findings within your...

Create Honeytoken Note

This tool allows you to attach contextual notes directly to a honeytoken for...

Create Honeytoken

You deploy new decoy credentials (honeytokens) into your system, increasing...

Create Honeytoken With Context

This lets you create a honeytoken and simultaneously add specific contextual information to it.

Create Team

You establish new teams within your GitGuardian account for grouping users with shared security responsibilities.

Delete Custom Tag

This removes a custom tag you previously created, cleaning up unnecessary labels.

Delete Custom Tags Key

You delete an entire key of custom tags when they are no longer needed.

Get Custom Tag

This retrieves the details for a specific, existing custom tag by its name or ID.

Get Health

You check the overall API health status of your connected GitGuardian account to...

Get Honeytoken

This retrieves all stored details for a single honeytoken, letting you review its setup and usage history.

Get Quotas

You view an overview of your current API usage quotas to prevent service interruptions.

Get Secret Incident

This tool retrieves all historical and current details related to a specific secret...

Get Self Api Token

You pull the full details of the API token currently being used by your agent client.

Ignore Secret Incident

If a leak is false positive or benign, you can mark it as ignored to clear up...

List Api Tokens

You get a list of all API tokens associated with your workspace for auditing...

List Audit Log Event Names

This lists every type of event that can be tracked and audited within your workspace history.

List Audit Logs

You view a comprehensive list of all activity logs, showing who did what and when in the workspace.

List Custom Tags

This retrieves an overview of every custom tag you have set up for organization.

List Health Check History

You view a record of past health checks to track stability over time for a specific...

List Health Checks

This lists the current and recent health check records available for your monitored...

List Honeytoken Events

You retrieve a list of all events triggered by any honeytoken, showing detection...

List Honeytoken Notes

This shows you all the documentation notes that have been attached to your honeytokens.

List Honeytoken Sources

You see a list of sources where any given honeytoken has appeared, pinpointing potential intrusion points.

List Honeytokens

This provides an overview and list of all currently active decoy credentials...

List Ip Allowlist

You view the current rules defining which IP addresses are permitted access to your...

List Ips

This lists all official and monitored IP address ranges belonging to GitGuardian's...

List Members

You view a roster of all user accounts who have access to the workspace.

List Scim Groups

This lists groups that are synced or managed via SCIM protocols, helping with identity management.

List Scim Users

You view a list of users who have been imported into the workspace using SCIM standards.

List Secret Incidents

This retrieves a comprehensive list and summary of all detected secret leaks in your...

List Sources

You view every source type (e.g., GitHub, GitLab) that is currently connected and...

List Team Memberships

This shows which specific users belong to which security teams within your...

List Teams

You get an overview and list of all defined security teams in the workspace.

Multiscan Content

This tool allows you to scan multiple large files or documents simultaneously for patterns indicating secrets.

Reset Honeytoken

If a decoy credential is compromised, this resets it so that you can redeploy a fresh copy immediately.

Resolve Secret Incident

When a security issue has been fixed and verified, you use this to formally close...

Revoke Honeytoken

You deactivate a honeytoken, preventing it from being triggered or reported on...

Revoke Self Api Token

This immediately cancels and revokes the specific API token your agent is currently...

Scan And Create Incidents

You run a scan on new content, and if secrets are found, this automatically...

Scan Content

This scans a single provided piece of content or code snippet to immediately check for any sensitive data patterns.

Trigger Health Check

You force the system to run an immediate health check on your monitored environment, verifying uptime and connectivity status.

Trigger Source Scans

This manually kicks off scans across all connected sources (like repositories) to...

Update Custom Tag Full

You perform a complete, full replacement of the details associated with an existing...

Update Custom Tag Partial

This modifies only specific fields of an existing custom tag without affecting its...

Update Custom Tags Key

You update the key definition for a group of custom tags when their purpose changes.

Update Honeytoken

If an existing decoy credential needs modification (like changing its name), this updates its details while keeping it active.

Update Secret Incident

You modify the status or assigned personnel of a secret incident after initial detection.

Security and governance baked right in.

Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.

GitGuardian MCP is compatible with Claude

Claude AI

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.

Start a conversation

Open a new chat. The GitGuardian integration is available immediately — no restart needed.

Antigravity

Configure Agent Environment

Open your Antigravity agent's workspace configuration or mcp-servers.json file.

Bind the Endpoint

Add the Vinkius endpoint URL to your agent's MCP connections list:

"mcp_servers": {
  "gitguardian": {
    "serverUrl": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
  }
}

Provide your secure token in place of [YOUR_TOKEN_HERE] to ensure your agent requests are authenticated.

Execute

Start your Antigravity session. The agent will autonomously discover and utilize the GitGuardian tools with full Vinkius guardrails applied.

GitGuardian MCP is compatible with VS Code

VS Code Copilot

⚡

One-Click Install (Recommended)

In your Vinkius Dashboard, simply click the Add to VS Code button for this server. We'll automatically configure your local workspace.

Or configure manually

Open MCP Settings

Open VS Code, press Ctrl/Cmd + Shift + P, and search for GitHub Copilot: MCP Servers.

Add Server Config

Add the Vinkius endpoint configuration to your mcp-servers.json file:

"gitguardian": {
  "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}

Ensure you replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.

LangChain

Install Dependencies

Install the LangChain MCP adapters for your environment:

pip install langchain-mcp-adapters

Connect the Server

Use the SSEClient in LangChain to connect to the Vinkius managed endpoint:

from langchain_mcp_adapters.client import SSEClient

# Connect to Vinkius
client = SSEClient(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
tools = client.get_tools()

CrewAI

Define the Tool

Load the Vinkius MCP tools into your CrewAI agents:

from crewai import Agent
from mcp_crewai import MCPTool

# Connect securely to Vinkius
vinkius_tools = MCPTool(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")

# Assign to Agent
researcher = Agent(
    role='Data Researcher',
    tools=vinkius_tools.get_all()
)

Execute Task

Run your CrewAI process. The agent will autonomously route tasks to the Vinkius managed server.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

Import from OpenAPI, Swagger, or YAML specs
Create Agent Skills with progressive disclosure
Deploy to edge with MCPFusion framework
Built in DLP, auth, and compliance on each call
Real time usage dashboard and cost metering
Publish to catalog or keep private

Start building

Make Your AI Do More

Start with GitGuardian, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.

Use this MCP plus 5,200+ others, all in one place
Add new capabilities to your AI anytime you want
Connections are secured and governed automatically
Track usage and costs across all your servers
Works with Claude, ChatGPT, Cursor, and more
New servers added to the catalog weekly

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by GitGuardian. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS CLOUD

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on each call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

Your data is protected. See how we built it.

The Security Dashboard Maze

Today, finding out what went wrong with your code is a multi-tab nightmare. You have to click over to the GitGuardian dashboard, filter by date, manually review incident summaries, and then copy details into a separate ticketing system just to assign ownership or update the status. It’s slow, it's painful, and you spend more time clicking than securing.

With this MCP, that entire manual process collapses into a single conversation. You simply ask your agent about the leaks. It retrieves all necessary information—from listing secret incidents to checking audit logs—and presents it instantly, letting you take action without leaving your current workflow.

Incident Management and Audit Visibility

Manual incident management requires people to remember which keys were leaked, who owns the remediation plan, and what steps have already been taken. You waste time cross-referencing `list_secret_incidents` data with team directories and change logs.

Now you can ask your agent to handle it all. It pulls up the incident details, shows the responsible team via `list_team_memberships`, and lets you confirm remediation status using `resolve_secret_incident`. The entire security lifecycle moves from a manual series of clicks into one conversation.

Support 24/7 support@vinkius.com ↗

Security Vinkius Trust Center ↗

SLA Service Level Agreement ↗

Report Listing Send Report ↗

secret-detection

vulnerability-scanning

incident-response

cybersecurity

honeytokens

code-security

What GitGuardian MCP does for your AI

This MCP lets you strengthen your organization's security by automating the detection of leaked secrets. You talk to your agent, and it handles the heavy lifting—scanning code for hardcoded API keys or AWS credentials before they cause a breach. If an incident is already active, you don't have to log into multiple dashboards; you can ask your agent to list secret incidents, assign them to specific team members, or even update their status right away.

You can also build detection layers by creating and managing decoy honeytokens that flag unauthorized access attempts across your private infrastructure. Because Vinkius hosts this MCP, your agent gets instant access to all the security tools needed, allowing you to operate as a 24/7 Security Operations Center assistant directly from your IDE or terminal.

Built · Hosted · Managed by Vinkius GitGuardian MCP - Detect Secrets and Manage Incidents

Server ID 019e389f-238f-717f-8dba-ee0217ad21b1

Vinkius Inspector

Compliance Grade F

Score 3.6/100

Report View Report ↗

Benefits of connecting GitGuardian MCP

You stop guessing about security. By using the scan_content tool, your agent instantly checks any code snippet you provide for sensitive data before it ever makes it into a commit.

Incident response is faster. Instead of manually checking dashboards, you ask to list secret incidents and then use assign_secret_incident or update_secret_incident to manage the fix status right in your chat interface.

You build better defenses with honeytokens. Running create_honeytoken lets you deploy fake keys across your infrastructure, and if they trigger an event (which you can list using list_honeytoken_events), you know exactly where an intruder is looking.

Compliance checks get automated. You can ask the MCP to run a full audit by listing all audit logs or checking the IP allowlist rules without logging into separate compliance portals.

Your team coordination improves. The MCP lets you manage teams via create_team and track who has access using tools like list_members, keeping your security operations organized.

GitGuardian MCP use cases

01 01

Preventing Accidental Key Commits

A developer is about to push a new feature branch. Instead of running local checks, they ask their agent: 'Scan this file for secrets.' The agent uses scan_content and immediately flags an exposed Stripe key, allowing the developer to fix it before committing.

02 02

Responding to Suspected Breaches

A security analyst notices strange activity. They ask the agent to list all honeytokens events. The agent uses list_honeytoken_events, which shows that a decoy AWS key was used in an unexpected region, guiding the investigation immediately.

03 03

Auditing Team Access

A manager needs to know who has access rights across environments. They ask the agent to list all workspace members and then use list_team_memberships to verify if a departed employee still belongs to critical groups.

04 04

Maintaining Compliance Records

During an audit, you need proof of security controls. You ask the agent to list audit logs for the last quarter. The MCP uses list_audit_logs and provides a structured report showing all critical actions taken.

GitGuardian MCP tradeoffs

What to watch out for, and the recommended way to handle each one.

Treating it like a simple log viewer

Avoid

Just asking the agent to 'show me what happened.' This only gives you passive data and doesn't help you fix or prevent things from happening again.

Instead

To actively manage an issue, first use list_secret_incidents to identify the leak, then use assign_secret_incident to hand off ownership, followed by update_secret_incident once it’s resolved.

Ignoring decoy credentials

Avoid

Seeing a honeytoken event pop up but dismissing it as 'just noise.' This is how real attackers operate; they test decoys first.

Instead

If you see an alert, use list_honeytoken_sources to pinpoint exactly where the unauthorized access originated. Then use get_secret_incident to determine if that location has other vulnerabilities.

Manual workflow updates

Avoid

Having to jump between a ticketing system, GitHub dashboard, and GitGuardian web UI just to update status.

Instead

Use update_secret_incident directly in your chat interface. This single action records the change, updating both your ticket and the security record instantly.

When to use GitGuardian MCP

You need this MCP if your primary pain point is managing leaked credentials or ensuring code remains clean of secrets. If you just want to track general system usage (e.g., who logged in), a basic log viewer might suffice. But when the threat involves highly sensitive data like API keys, access tokens, or private project identifiers, GitGuardian is necessary. Use it if your workflow requires actions like creating decoys (create_honeytoken), triaging incidents (list_secret_incidents), and automating compliance checks across multiple systems. Don't use this MCP just to list teams; for simple user management, a dedicated directory tool works better. However, if you need the audit log alongside team structure details, this MCP connects all those dots.

Frequently asked questions about GitGuardian MCP

How do I use GitGuardian MCP to find leaked API keys? +

You ask your agent to scan specific code snippets using the scan_content tool. It immediately checks that content against known patterns for secrets and reports any findings, telling you which key was exposed.

Can GitGuardian MCP manage my team's security roles? +

Yes, you use tools like list_teams or list_members to see who is in the system. You can then use assign_secret_incident to assign ownership of a breach to specific team members.

What are honeytokens and how does GitGuardian MCP help? +

Honeytokens are fake credentials that act as tripwires. The MCP lets you deploy them using create_honeytoken. If they get used, the system alerts you via list_honeytoken_events, showing exactly where an intruder went.

Is GitGuardian MCP better than just looking at audit logs? +

Theoretically, yes. While you can use list_audit_logs to see general activity, this MCP connects that log data directly to specific secret incidents and team responsibilities, giving context.

How do I clean up old or false positive leaks with GitGuardian MCP? +

First, you check the details using get_secret_incident. Once confirmed as benign or fixed, you use ignore_secret_incident to mark it in the system, keeping your active incident list clean.

View all recipes →

MCP Workflow for Catching Leaked Secrets Fast

A leaked API key and a suspicious endpoint event happened 4 minutes apart , your agent connects the dots before you do

Crowdstrike Falcon Gitguardian Discord

View all recipes