LeakRank Guard vs GitHub Actions Audit
LeakRank Guard is an MCP server published by ProtoTeemo. Marketplaces we read that list it: 1 (Official MCP Registry). GitHub Actions Audit is an MCP server published by UnbearableDev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  GitHub Actions Audit | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.3 Downloads/month (npm): 172 Downloads/week (npm): 17 Not marked · First seen |
Listed Version: 1.0.1 Forks (GitHub): 0 Stars (GitHub): 0 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 | LeakRank Guard | GitHub Actions Audit |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (leakrank-guard) | Remote server (unbearable-dev--github-actions-audit.apify.actor/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/unbearabledev/github-actions-audit |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 30 h ago, requires a key |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
LeakRank Guard
Scans code changes for leaked secrets and insecure config, with actionable fixes for AI agents.
GitHub Actions Audit
GitHub Actions workflow security audit - 21 checks: pinning, permissions, secrets, injection.
How to run each
LeakRank Guard As a local MCP server: npm package
claude mcp add --env "LEAKRANK_API_KEY=<YOUR_LEAKRANK_API_KEY>" --transport stdio leakrank-guard -- npx -y leakrank-guard mcpRequires: LEAKRANK_API_KEY (secret)
GitHub Actions Audit As a remote MCP server
claude mcp add --transport http github-actions-audit https://unbearable-dev--github-actions-audit.apify.actor/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only GitHub Actions Audit 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
The marketplaces of GitHub Actions Audit publish no settings it asks for, so we do not compare settings.
What it can do: LeakRank Guard · What it can do: GitHub Actions Audit · Compare two other plugins
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.