github-secrets vs Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner
github-secrets is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑21.
github-secrets is a plugin bundle for AI coding tools published by gabrielkoerich. No marketplace we read lists it any more. Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner is an MCP server published by AnshumanAtrey. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner | |
|---|---|---|
| Community marketplace gabrielkoerich/skills | Removed on 2026-10-21 Version: not stated Forks (GitHub): 0 Stars (GitHub): 6 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.17.3 Forks (GitHub): 1 Stars (GitHub): 3 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | github-secretsno longer listed · | Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 6 | 3 |
| Forks (GitHub) (differs) | 0 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.apify.com) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/gabrielkoerich/skills | github.com/anshumanatrey/gitleaks-github-secret-scanner |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-19 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 days ago, requires a key |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of github-secrets
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Keep secrets, API keys, and tokens out of committed .env files by importing and mounting them as 1Password Developer Environments.
-
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
-
Audit GitHub Actions workflows for script injection, unpinned actions and missing permissions.
-
Drive Cliff from Claude Code: install, onboard credentials (GitHub PAT + AI provider key), run the full secure-this-repo loop (scan → plan → approve → PR → merge → close), or…
-
Inspect repositories, triage pull requests and issues, debug CI, and publish changes through a hybrid GitHub connector and CLI workflow.
-
The official GitGuardian plugin for AI coding agents. Detects 700+ hardcoded secret types across files, git history, Docker images, and PyPI packages via the ggshield CLI; plants…
What each says it does
github-secrets
Manage GitHub repository secrets via the GitHub API. Supports listing, adding, updating, and deleting repository and organization secrets. Use when user needs to manage GitHub Actions secrets, environment variables, or repository-level secrets securely.
Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner
Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner
How to run each
github-secrets
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: github-secrets · What it can do: Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.