Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner MCP Server

by anshumanatrey Your server? Claim it

answering

Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner is answering right now. Last checked 9 min ago. Last commit 30 Sep 2026.

Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner

Uptime history 18 days of history · worst day 99%

18 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

311 ms

Response time

average over 24h

Stars

last commit 30 Sep 2026

What the code does

We read the source, 6 d ago · rules ccca72095570

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Image runs as root Dockerfile:2

# Install git + gitleaks (the scanner binary)
USER root

Sends data to a third-party sink rules/slack-webhook.toml:6

search_keywords = ["slack", "SLACK_WEBHOOK_URL", "hooks.slack.com"]

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add gitleaks-github-secret-scanner --transport http https://mcp.apify.com/?tools=anshumanatrey/gitleaks-github-secret-scanner

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "gitleaks-github-secret-scanner": {
      "url": "https://mcp.apify.com/?tools=anshumanatrey/gitleaks-github-secret-scanner"
    }
  }
}

~/.codex/config.toml

[mcp_servers.gitleaks-github-secret-scanner]
url = "https://mcp.apify.com/?tools=anshumanatrey/gitleaks-github-secret-scanner"

.cursor/mcp.json

{
  "mcpServers": {
    "gitleaks-github-secret-scanner": {
      "url": "https://mcp.apify.com/?tools=anshumanatrey/gitleaks-github-secret-scanner"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "gitleaks-github-secret-scanner": {
      "url": "https://mcp.apify.com/?tools=anshumanatrey/gitleaks-github-secret-scanner"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but you need an API key from its owner to call it.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.apify.com/?tools=anshumanatrey/gitleaks-github-secret-scanner	streamable-http	needs key	301 ms	9 min ago

Alternatives to Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner

same job, measured the same way

Betterleaks Cloud - GitHub, Git, S3, Dir Secret Scanner

by anshumanatrey

Betterleaks Cloud - GitHub, Git, S3, Dir Secret Scanner

answering

N0s1 MCP

by spark1security

Secret scanner for Slack, Jira, Confluence, Asana, Wrike, Linear, Zendesk, GitHub and GitLab

171 installs/wk local only

Secrets Audit MCP

by eltociear

Detects leaked secrets & API keys: 32+ provider rules (AWS, GitHub, Stripe, OpenAI…), zero deps.

local only

Appveyor MCP

by mrfentmen

CI pipeline monitoring for GitLab and GitHub - no API key.

60 installs/wk local only

AI Scanner

by aakashbhardwaj27

Scan codebases for LLM/AI SDK usage, exposed API tokens, and hardcoded secrets.

39 installs/wk local only

Secretguard MCP

by vladimirbakalov

Scans code for hardcoded secrets (AWS, Stripe, GitHub, JWTs) before an AI agent commits it.

local only

XploitScan

by bgage72590

Security scanner for AI-generated code. 30 free rules; all 223 with a paid-plan API key.

710 installs/wk local only

Git MCP Server

by ray0907

MCP server for GitLab and GitHub

42 installs/wk local only

Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner — questions

Answers built from our own checks of this server.

Why is there no tool list for Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 311 ms. The bar chart above shows every period we have measured.

How do I connect Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key: it refuses anonymous clients.

Does Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner need an API key?

Yes. Every time we knock, Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner?

It answers our handshake in 311 ms on average, which is faster than 46% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner open source?

Yes — it is published under the MIT licence, written in Python and 3 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.