4,000+ servers built on vurb.ts
Vinkius
CursorIDE
GitGuardian MCP Server

Bring Secret Detection
to Cursor

Learn how to connect GitGuardian to Cursor and start using 49 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Assign Secret IncidentBulk Prefix LookupCreate Custom TagCreate HoneytokenCreate Honeytoken NoteCreate Honeytoken With ContextCreate TeamDelete Custom TagDelete Custom Tags KeyGet Custom TagGet HealthGet HoneytokenGet QuotasGet Secret IncidentGet Self Api TokenIgnore Secret IncidentList Api TokensList Audit Log Event NamesList Audit LogsList Custom TagsList Health Check HistoryList Health ChecksList Honeytoken EventsList Honeytoken NotesList Honeytoken SourcesList HoneytokensList Ip AllowlistList IpsList MembersList Scim GroupsList Scim UsersList Secret IncidentsList SourcesList Team MembershipsList TeamsMultiscan ContentReset HoneytokenResolve Secret IncidentRevoke HoneytokenRevoke Self Api TokenScan And Create IncidentsScan ContentTrigger Health CheckTrigger Source ScansUpdate Custom Tag FullUpdate Custom Tag PartialUpdate Custom Tags KeyUpdate HoneytokenUpdate Secret Incident

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
GitGuardian

What is the GitGuardian MCP Server?

Connect your GitGuardian workspace to any AI agent to strengthen your security posture and manage secret leaks through natural conversation.

What you can do

  • Incident Management — List, retrieve, and resolve secret incidents. Assign team members to leaks and track remediation progress.
  • Honeytokens — Create and manage decoy credentials (honeytokens) to detect unauthorized access to your private infrastructure.
  • Security Scanning — Scan code snippets or content for secrets and sensitive data in real-time to prevent leaks before they happen.
  • Audit & Compliance — Access detailed audit logs to monitor workspace activity and ensure compliance with security policies.
  • Team Collaboration — Manage teams, members, and API tokens to orchestrate security operations across your organization.

How it works

  1. Subscribe to this server
  2. Enter your GitGuardian API Key
  3. Start monitoring and securing your code from Claude, Cursor, or any MCP-compatible client

Your AI acts as a 24/7 Security Operations Center (SOC) assistant, helping you triage alerts and deploy defenses without leaving your workflow.

Who is this for?

  • Security Engineers — quickly triage secret incidents and manage honeytoken deployments across multiple environments.
  • DevOps & SREs — automate security audits and monitor workspace health checks directly from the terminal or IDE.
  • Developers — scan code for secrets before committing and check incident statuses without switching to the GitGuardian dashboard.

Built-in capabilities (49)

assign_secret_incident

Assign a secret incident

bulk_prefix_lookup

Bulk lookup for honeytoken HMSL hashes

create_custom_tag

Create a custom tag

create_honeytoken

Create a honeytoken

create_honeytoken_note

Create a honeytoken note

create_honeytoken_with_context

Create a honeytoken within a context

create_team

Create a team

delete_custom_tag

Delete a custom tag

delete_custom_tags_key

Delete a custom tags key

get_custom_tag

Retrieve a custom tag

get_health

Check API health status

get_honeytoken

Retrieve a honeytoken

get_quotas

Retrieve quota overview

get_secret_incident

Retrieve secret incident details

get_self_api_token

Retrieve current API token details

ignore_secret_incident

Ignore a secret incident

list_api_tokens

List API tokens

list_audit_log_event_names

List all existing event names for audit logs

list_audit_logs

List audit logs for your workspace

list_custom_tags

List custom tags

list_health_check_history

List health check history for an instance

list_health_checks

List health checks

list_honeytoken_events

List all honeytokens events

list_honeytoken_notes

List honeytoken notes

list_honeytoken_sources

List sources where a honeytoken appears

list_honeytokens

List honeytokens

list_ip_allowlist

List IP allowlist rules

list_ips

List GitGuardian's own IP addresses

list_members

List workspace members

list_scim_groups

List groups via SCIM

list_scim_users

List members via SCIM

list_secret_incidents

List secret incidents

list_sources

List all sources

list_team_memberships

List team members

list_teams

List teams

multiscan_content

Scan multiple contents for secrets

reset_honeytoken

Reset a honeytoken

resolve_secret_incident

Resolve a secret incident

revoke_honeytoken

Revoke a honeytoken

revoke_self_api_token

Revoke current API token

scan_and_create_incidents

Scan content and create incidents automatically

scan_content

Scan content for secrets

trigger_health_check

Trigger a health check

trigger_source_scans

Trigger scans on sources

update_custom_tag_full

Full update of a custom tag

update_custom_tag_partial

Partial update of a custom tag

update_custom_tags_key

Update a custom tags key

update_honeytoken

Update a honeytoken

update_secret_incident

Update a secret incident

Why Cursor?

Cursor's Agent mode turns GitGuardian into an in-editor superpower. Ask Cursor to generate code using live data from GitGuardian and it fetches, processes, and writes. all in a single agentic loop. 49 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

  • Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

  • Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

  • MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

  • VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

See it in action

GitGuardian in Cursor

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

GitGuardian and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect GitGuardian to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for GitGuardian in Cursor

The GitGuardian MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 49 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

GitGuardian
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures GitGuardian for Cursor

Every tool call from Cursor to the GitGuardian MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Can I resolve a secret incident directly through the AI?

Yes. You can use the resolve_secret_incident tool by providing the incident ID. You can also use assign_secret_incident to delegate the fix to a specific team member.

02

How do I create a decoy credential to catch attackers?

Use the create_honeytoken tool. You can specify the type and name of the honeytoken, and GitGuardian will generate a decoy that alerts you if it's ever used.

03

Is it possible to scan a text block for secrets before I commit it?

Absolutely. Use the scan_content tool. Provide the document content and a filename, and the AI will return any detected secrets or policy violations found by GitGuardian's engine.

04

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.

05

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.

06

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.

07

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.

08

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.

09

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

Explore More MCP Servers

View all →