# Docker Compose Security Audit (`unbearable_dev/docker-compose-audit`) Actor

Audits docker-compose.yml files for security misconfigurations. 25 checks across 9 categories with severity, remediation, and YAML fix snippets. Pay-per-event. MCP-native - call from Claude Desktop, Cursor, n8n, or any MCP client. Built by Unbearable Labs.

- **URL**: https://apify.com/unbearable\_dev/docker-compose-audit.md
- **Developed by:** [Noel Himer](https://apify.com/unbearable_dev) (community)
- **Categories:** Developer tools, Automation, MCP servers
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 docker compose audit calls

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Docker Compose Security Audit

> MCP server that audits  files for security misconfigurations. 25 checks across 9 categories, designed for AI agents — every finding ships with a severity rating, full remediation text, and a YAML fix snippet you can paste.

**Built by [Unbearable Labs](https://github.com/UnbearableDev). Free to use — bring your own Apify token.**

***

### Available on

- [Apify Actor Store](https://apify.com/unbearable_dev/docker-compose-audit) — primary
- [Smithery](https://smithery.ai/servers/unbearabledev/docker-compose-audit)

**Newsletter:** [Unbearable TechTips Weekly](https://unbearabletechtips.beehiiv.com) · **All Actors:** [github.com/UnbearableDev](https://github.com/UnbearableDev)

### What it does

Point any MCP-capable client (Claude Desktop, Cursor, n8n, Make, Zapier, custom agents) at this server, hand it the contents of a , and get back a structured report with:

- **Severity** — high / medium / low / info
- **Service** — which compose service the finding affects
- **Description** — what's wrong and why it matters
- **Remediation** — what to do about it
- **Fix snippet** — YAML you can paste directly into the file

### Tools

| Tool | Purpose |
|------|---------|
|  | Run all checks, return full report |
|  | Container privilege & capability issues only |
|  | Network exposure issues only |
|  | Volume mount & filesystem issues only |
|  | Secret hygiene issues only |
|  | Resource limit issues only |
|  | Image tag / registry / pinning issues only |
|  | Healthcheck / restart / init issues only |
|  | Logging driver / rotation issues only |
|  | Deprecated fields / Compose-spec hygiene only |
|  | Browse the full check catalog |

All audit-running tools accept the same input:

- (string) — paste the YAML content directly, **OR**
- (string) — public HTTPS URL to fetch (e.g. GitHub raw URL)

Provide exactly one.  defaults to  (drops  findings); set to  or  to filter further.

### Example

Input:

Output:

### Pricing

Free to use — hosted on Apify, bring your own Apify token.

### Check catalog (25 checks across 9 categories)

| Category | Live checks |
|----------|------------|
| **Privilege** | Root user (DCS-001), privileged mode (DCS-002), dangerous capabilities (DCS-003),  (DCS-004),  missing (DCS-005),  missing (DCS-006) |
| **Network** |  (DCS-010), port bound to 0.0.0.0 (DCS-011), SSH port exposed (DCS-013), DB port exposed (DCS-014) |
| **Filesystem** |  mount (DCS-018), host root mount (DCS-019), sensitive host paths (DCS-020) |
| **Secrets** | Hardcoded secret in env (DCS-026), secret-pattern env without Docker secrets (DCS-027) |
| **Resources** | No memory limit (DCS-032), no CPU limit (DCS-033), no PID limit (DCS-034) |
| **Image hygiene** | Unpinned /  image (DCS-037) |
| **Runtime lifecycle** | No healthcheck (DCS-043), no restart policy (DCS-044) |
| **Logging** | No log driver (DCS-048), no log rotation (DCS-049) |
| **Compose hygiene** | Deprecated  field (DCS-051),  without healthcheck condition (DCS-052) |

Use  to get the canonical, up-to-date catalog with IDs, severities, and titles.

### Connecting from Claude Desktop

Add to your MCP config:

### Limits

- **YAML size:** 1 MB cap per audit call
- **URL fetch:** 5-second timeout, max 3 redirects, HTTPS only
- **Session timeout:** 5 minutes of inactivity

### What's NOT covered (yet)

Pure static analysis of the compose file only. Out of scope for this version:

- Image vulnerability scanning (use Trivy / Grype for that)
- Live container inspection
- Kubernetes / Helm manifests (see [](https://apify.com/unbearable_dev/k8s-manifest-audit))
- Dockerfile-specific lint (see [](https://apify.com/unbearable_dev/dockerfile-audit))

### Source / contact

Issues, ideas, or false-positive reports: open an issue on the [GitHub repo](https://github.com/UnbearableDev) or email .

***

Built by Noel @ Unbearable Labs — more like this in the weekly newsletter: https://unbearabletechtips.beehiiv.com

# Actor input Schema

## Actor input object example

```json
{}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("unbearable_dev/docker-compose-audit").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("unbearable_dev/docker-compose-audit").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call unbearable_dev/docker-compose-audit --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,unbearable_dev/docker-compose-audit"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/iRMBeVHFL0EaEHC9T/builds/Lf4hc6AameRX5y5sn/openapi.json