Ext Ops Panel
Open dashboard
Comparison

Beagle Security vs Website Audit Tools

Beagle Security is an MCP server published by beaglesecurity. Marketplaces we read that list it: 1 (Docker MCP Catalog). Website Audit Tools is an MCP server published by gptshopltd.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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 SecurityWebsite Audit Tools
Docker MCP Catalog Listed
Version: sha256:4be5e4ae4369
Forks (GitHub): 0
Pulls (Docker Hub): 35 252
Stars (Docker Hub): 1
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
No figure published
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 Website Audit Tools
FactBeagle SecurityWebsite Audit Tools
Marketplaces that list it11
Stars (GitHub) (differs)1No figure on GitHub
Pulls (Docker Hub) (differs)35 252No figure on Docker Hub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/beagle-security-mcp-server)Remote server (mcp.apify.com)
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-serverNot stated
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-15
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-24

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.

Website Audit Tools

In its own words, on Official MCP Registry:

SEO, broken links, Lighthouse, sitemaps, Open Graph tags and SSL expiry for any list of URLs.

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)

Website Audit Tools

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

Only Website Audit Tools has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Website Audit Tools publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Website Audit Tools publish no settings it asks for, so we do not compare settings.

What it can do: Beagle Security · What it can do: Website Audit Tools · 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