Ext Ops Panel
Open dashboard
Comparison

Beagle Security vs GitHub Actions Security Audit

Beagle Security is an MCP server published by beaglesecurity. Marketplaces we read that list it: 1 (Docker MCP Catalog). GitHub Actions Security Audit is an MCP server published by tylerscomic-lab. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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

Where each is published
MarketplaceBeagle SecurityGitHub Actions Security Audit
Docker MCP Catalog Listed
Version: sha256:4be5e4ae4369
Forks (GitHub): 0
Pulls (Docker Hub): 35 028
Stars (Docker Hub): 1
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
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

Beagle Security vs GitHub Actions Security Audit
FactBeagle SecurityGitHub Actions Security Audit
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Pulls (Docker Hub) (differs)35 028No figure on Docker Hub
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/beagle-security-mcp-server)Remote server (github-actions-audit-mcp.mcpize.run/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)17Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/beaglesecurity/beagle-security-mcp-servergithub.com/tylerscomic-lab/github-actions-audit-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 days 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

Beagle Security

In its own words, on Docker MCP Catalog:

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.

GitHub Actions Security Audit

In its own words, on Official MCP Registry:

Audit GitHub Actions workflows for script injection, unpinned actions and missing permissions.

How to run each

Beagle Security As a local MCP server: Docker image

Claude Code
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-server

Requires: BEAGLE_SECURITY_API_TOKEN (secret)

GitHub Actions Security Audit As a remote MCP server

Claude Code
claude mcp add --transport http github-actions-audit-mcp https://github-actions-audit-mcp.mcpize.run/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only GitHub Actions Security Audit has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of GitHub Actions Security Audit publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of GitHub Actions Security Audit publish no settings it asks for, so we do not compare settings.

What it can do: Beagle Security · What it can do: GitHub Actions Security Audit · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.

Where the data comes from: how the catalog is built