Beagle Security vs repo-forensics
Beagle Security is an MCP server published by beaglesecurity. Marketplaces we read that list it: 1 (Docker MCP Catalog). repo-forensics is a plugin bundle for AI coding tools published by Alex Greenshpun. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-20. 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 |   Beagle Security | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:4be5e4ae4369 Forks (GitHub): 0 Pulls (Docker Hub): 35 086 Stars (Docker Hub): 1 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Community marketplace alexgreensh/repo-forensics | Not listed | Listed Version: 2.14.15 Forks (GitHub): 29 Stars (GitHub): 194 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 | Beagle Security | repo-forensics |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (worse) | 194 (better) |
| Pulls (Docker Hub) (differs) | 35 086 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 0 (worse) | 29 (better) |
| Last release (differs) | Not published | 2026-10-16 |
| Where it runs (differs) | On your machine (mcp/beagle-security-mcp-server) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 17 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Hooks it runs (differs) | Not published | 4 |
| Parts of the bundle (differs) | Not a bundle | 5 |
| Licence (differs) | MIT | PolyForm-Noncommercial-1.0.0 |
| Repository (differs) | github.com/beaglesecurity/beagle-security-mcp-server | github.com/alexgreensh/repo-forensics |
| Changes in the last 7 days (differs) | 0 | 3 |
| First seen (differs) | 2026-10-11 | 2026-10-15 |
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
Beagle Security
Connects with the Beagle Security backend using a user token to manage applications, run automated security tests, track vulnerabilities across environments, and gain intelligence from Application and API vulnerability data.
repo-forensics
Offline security scanner for AI-agent repos, skills, plugins, and MCP servers. 26 scanners detect prompt injection, MCP tool poisoning, credential exposure, malicious lifecycle hooks, package IOCs, CVEs, CISA KEV exposure, and post-incident traces. Zero dependencies. Zero telemetry.
How to run each
Beagle Security As a local MCP server: Docker image
claude mcp add --env "BEAGLE_SECURITY_API_TOKEN=<YOUR_BEAGLE_SECURITY_API_TOKEN>" --transport stdio beagle-security -- docker run -i --rm -e BEAGLE_SECURITY_API_TOKEN mcp/beagle-security-mcp-serverRequires: BEAGLE_SECURITY_API_TOKEN (secret)
repo-forensics As a Claude Code plugin
/plugin marketplace add alexgreensh/repo-forensics
/plugin install repo-forensics@alexgreensh-repo-forensicsCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of repo-forensics publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of repo-forensics publish no settings it asks for, so we do not compare settings.
What it can do: Beagle Security · What it can do: repo-forensics · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.