Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner MCP server
io.github.AnshumanAtrey · Updated
Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner
At a glance
Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner is an MCP server in the Dev Tools & Git category. It is hosted remotely and connects over HTTP, and needs Authorization. It scores B (74/100) on the MCP Skills Hub health score as of Oct 27, 2026.
One-click install
Opens your editor and pre-fills the config. Your editor will ask before adding it.
How to install Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner in your AI client
Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.
How to install Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner in Claude CodeAnthropic's agentic CLI
Add the server
bashclaude mcp add --transport http gitleaks-github-secret-scanner https://mcp.apify.com/?tools=anshumanatrey/gitleaks-github-secret-scanner --header 'Authorization: Bearer <YOUR_TOKEN>'Fill in your credentials
Replace Bearer <YOUR_TOKEN> with your real value. Keep secrets out of any config file you commit.
Verify it's connected
bashclaude mcp listSharing it with your team?
Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).
Use it in a session
Ask Claude to use the tools this server exposes. It discovers them automatically.
How to install Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner in Claude DesktopDesktop app (MCP config)
Open your MCP config
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json
Add this server
json{ "mcpServers": { "gitleaks-github-secret-scanner": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.apify.com/?tools=anshumanatrey/gitleaks-github-secret-scanner", "--header", "Authorization:${AUTH_HEADER}" ], "env": { "AUTH_HEADER": "Bearer <YOUR_TOKEN>" } } } }Fill in your credentials
Replace Bearer <YOUR_TOKEN> with your real value. Keep secrets out of any config file you commit.
Why the wrapper?
This is a remote (HTTP) server and Claude Desktop only launches local processes, so mcp-remote proxies the connection. It will open a browser window if the server needs OAuth.
Restart Claude Desktop
The tools appear under the 🔌 menu once the app reloads.
How to install Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner in CursorAI-first code editor
Create / edit .cursor/mcp.json in your project
json{ "mcpServers": { "gitleaks-github-secret-scanner": { "url": "https://mcp.apify.com/?tools=anshumanatrey/gitleaks-github-secret-scanner", "headers": { "Authorization": "Bearer <YOUR_TOKEN>" } } } }Fill in your credentials
Replace Bearer <YOUR_TOKEN> with your real value. Keep secrets out of any config file you commit.
Enable it
Cursor Settings → MCP → toggle the server on. Tools become available to the Composer/Agent.
How to install Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner in Codex CLIOpenAI coding agent
Add to ~/.codex/config.toml
toml[mcp_servers.gitleaks-github-secret-scanner] command = "npx" args = ["-y", "mcp-remote", "https://mcp.apify.com/?tools=anshumanatrey/gitleaks-github-secret-scanner", "--header", "Authorization:${AUTH_HEADER}"] env = { AUTH_HEADER = "Bearer <YOUR_TOKEN>" }Fill in your credentials
Replace Bearer <YOUR_TOKEN> with your real value. Keep secrets out of any config file you commit.
Why the wrapper?
Codex runs MCP servers as local processes, so mcp-remote bridges this HTTP endpoint to stdio.
Run Codex
Codex loads MCP servers from config.toml on startup and exposes their tools to the agent.
How to install Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner in WindsurfCodeium's agentic IDE
Edit ~/.codeium/windsurf/mcp_config.json
json{ "mcpServers": { "gitleaks-github-secret-scanner": { "serverUrl": "https://mcp.apify.com/?tools=anshumanatrey/gitleaks-github-secret-scanner", "headers": { "Authorization": "Bearer <YOUR_TOKEN>" } } } }Fill in your credentials
Replace Bearer <YOUR_TOKEN> with your real value. Keep secrets out of any config file you commit.
Reload
Windsurf → Cascade → refresh MCP servers. Cascade can now call the tools.
How to install Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner in ClineVS Code autonomous agent
Open Cline → MCP Servers → Configure
Adds to cline_mcp_settings.json.
Add the server
json{ "mcpServers": { "gitleaks-github-secret-scanner": { "type": "streamableHttp", "url": "https://mcp.apify.com/?tools=anshumanatrey/gitleaks-github-secret-scanner", "headers": { "Authorization": "Bearer <YOUR_TOKEN>" } } } }Fill in your credentials
Replace Bearer <YOUR_TOKEN> with your real value. Keep secrets out of any config file you commit.
How to install Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner in VS CodeCopilot / MCP support
Create .vscode/mcp.json
json{ "servers": { "gitleaks-github-secret-scanner": { "type": "http", "url": "https://mcp.apify.com/?tools=anshumanatrey/gitleaks-github-secret-scanner", "headers": { "Authorization": "Bearer <YOUR_TOKEN>" } } } }Fill in your credentials
Replace Bearer <YOUR_TOKEN> with your real value. Keep secrets out of any config file you commit.
Start it
VS Code shows a ▶ Start action above the server entry. Agent mode (Copilot Chat) can then use the tools.
What does Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner need from you?
Bearer token — Apify API token, as 'Bearer <apify-api-token>'. Runs bill to this account.
AuthorizationrequiredsecretHTTP headerApify API token, as 'Bearer <apify-api-token>'. Runs bill to this account.
What tools does Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner expose?
This server requires credentials before it will list its tools, so we cannot enumerate them here. Connect it in your client to see what it offers.
What the code can do
This is a remote server — nothing is installed or run on your machine, so there is no local code to analyze. What it can reach is described above: your requests go to the provider's host.
Before you install
Signals gathered from the source repo and package registry — not a safety verdict.
What it can reach
- Third-party hosted service — Your requests and any data in them are sent to mcp.apify.com.
- No local execution — Nothing is installed or run on your machine.
- Last commit 27 days ago — Actively maintained.
- 2 GitHub stars — Very little community usage so far.
Client compatibility
Health score
B · 74Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated
- Maintenance30%100%
Last commit 27 days ago.
- Adoption20%14%
2 stars.
- Transparency20%75%
3/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✗ discoverable tool list.
- Provenance15%75%
Links to its own repository; package linkage unverified.
- Packaging15%100%
Remote endpoint with documented authentication.
Documentation
Full READMEGitleaks Cloud - GitHub API Key Hunter & Secret Scanner
Cloud-hosted gitleaks for hunting leaked API keys, tokens, and credentials across GitHub - 30+ services including Indian fintech.
Available as an Apify Actor. Pay-per-event. The lightweight cheaper tier; sibling betterleaks-cloud adds live vendor-API validation.
What does it do?
Scans a GitHub user, org, or repo for leaked API keys and credentials across 30+ critical services: Razorpay, Stripe, AWS, OpenAI, Anthropic, Gemini, Supabase, Firebase, GitHub PATs, Twilio, SendGrid, Slack, Discord, Telegram, plus Indian fintech APIs (Cashfree, PayU, Surepass, Decentro, Karza, Attestr, Tartan). Smart key-secret pairing detects related credentials in the same file (e.g., Razorpay's two-part key_id + key_secret).
How is it different from running gitleaks CLI locally OR GitGuardian / Snyk Code subscriptions?
| | running gitleaks CLI locally OR GitGuardian / Snyk Code subscriptions | This actor | |---|---|---| | Setup | Local gitleaks install + GitHub API integration | Cloud, zero install | | Indian fintech detectors | Generic gitleaks: no specific Razorpay / Cashfree / PayU rules | Built-in detectors for Razorpay, Cashfree, PayU, Surepass, Decentro, Karza, Attestr, Tartan | | Key-secret pairing | Each finding standalone | Smart pairing in same file | | Cost | Free CLI but ops time; GitGuardian $5K+/year | Pay-per-event, no minimum | | Validation | None | Sibling betterleaks-cloud adds live vendor-API validation |
Tested on real Indian fintech repos: 47 razorpay-named GitHub repos scanned, 22 had leaks, 4 had production credentials in .env files including paired key_id + key_secret.
When should I use it?
- DevSecOps - scan your own org for accidental commits of secrets
- Bug bounty - hunt for live credentials in customer-facing public repos
- Pre-acquisition security audit - check target company's open-source posture
- Indian fintech compliance - sweep for Razorpay / Cashfree / PayU keys before regulator audit
- Cheap secret-scanner alternative to GitGuardian / Snyk for low-volume use
What does it cost?
Pay-per-event:
| Event | Price | When it fires | |---|---|---| | Actor start | $0.01 | Charged once per run for the lister + scan orchestration | | Per repo scanned | $0.02 | Charged once per repo successfully cloned and scanned. Unreachable repos are not charged |
Excerpt — the full document is on GitHub.
Alternatives to Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner
- Betterleaks Cloud - GitHub, Git, S3, Dir Secret ScannerB · 71Betterleaks Cloud - GitHub, Git, S3, Dir Secret Scanner
- pare-githubA · 88Pare GitHub ג€” Structured GitHub operations (PRs, issues, actions) as typed JSON.
- mcp-github-organization-signal-scannerB · 79Resolve a company domain to its GitHub organization with repo, language and activity signals.
- githubA · 88MCP server for GitHub operations (PRs, issues, actions) with structured, token-efficient output
Maintain Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner? Add a badge to your README
Shows its health grade, and links readers to install steps for every client.
[](https://mcp-skills-hub.vercel.app/mcps/io-github-anshumanatrey-gitleaks-github-secret-scanner)Catalog data refreshed . Something wrong? Report it.