Ext Ops Panel
Open dashboard
Comparison

Docker Compose Audit vs io.github.caglarbozkurt/heimdall

Docker Compose Audit is an MCP server published by UnbearableDev. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.caglarbozkurt/heimdall is an MCP server published by caglarbozkurt. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
MarketplaceDocker Compose Auditio.github.caglarbozkurt/heimdall
Official MCP Registry Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.5.1
Downloads/month (npm): 186
Downloads/week (npm): 29
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

Docker Compose Audit vs io.github.caglarbozkurt/heimdall
FactDocker Compose Auditio.github.caglarbozkurt/heimdall
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (unbearable-dev--docker-compose-audit.apify.actor/mcp)On your machine (mcp-heimdall-scan)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/unbearabledev/docker-compose-auditgithub.com/caglarbozkurt/mcp-heimdall
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 3 days ago, requires a keyno remote endpoint we check

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

Docker Compose Audit

In its own words, on Official MCP Registry:

Security audit for docker-compose.yml — 25 checks: secrets, privileges, network, volumes, images.

io.github.caglarbozkurt/heimdall

In its own words, on Official MCP Registry:

Scan an MCP server or agent config for injection, exfiltration, and risky capabilities.

How to run each

Docker Compose Audit As a remote MCP server

Claude Code
claude mcp add --transport http docker-compose-audit https://unbearable-dev--docker-compose-audit.apify.actor/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

io.github.caglarbozkurt/heimdall As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio heimdall -- npx -y --package mcp-heimdall-scan heimdall-mcp mcp-heimdall-scan

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

Only Docker Compose 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

Neither one's marketplaces publish the settings it asks for.

What it can do: Docker Compose Audit · What it can do: io.github.caglarbozkurt/heimdall · 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.

Where the data comes from: how the catalog is built