
Docker Compose Audit
Run a structured security review on docker-compose.yml from the agent before you ship self-hosted or dockerized stacks.
Overview
io.github.UnbearableDev/docker-compose-audit is a Ship-phase MCP server that security-audits docker-compose.yml with 25 checks via an Apify streamable-http endpoint.
What is this MCP server?
- 25 automated checks across docker-compose.yml security topics
- Covers secrets, privileges, networking, volumes, and images
- Hosted streamable-http MCP on Apify actor infrastructure
- Requires Apify Bearer token in Authorization header
- 25 security checks
- docker-compose.yml scope
- Remote MCP v1.0.0 on Apify actor
What problem does it solve?
You are about to deploy from docker-compose but cannot quickly tell if secrets, privileges, or networks in the file are unsafe.
Who is it for?
Indie devs self-hosting with Docker Compose who want agent-driven static audits before merge or deploy.
Skip if: Kubernetes-only deployments, runtime intrusion testing, or teams without an Apify account and compose-based workflow.
What do I get? / Deliverables
After registering the Apify MCP remote with your API token, the agent can return a structured pass/fail style review across 25 compose security checks.
- Security audit results against 25 compose checks (secrets, privileges, network, volumes, images)
- Actionable findings the agent can turn into compose fixes before ship
Recommended MCP Servers
Journey fit
How it compares
Specialized docker-compose security audit MCP, not a general Dockerfile linter or infrastructure provisioning skill.
Common Questions / FAQ
Who is io.github.UnbearableDev/docker-compose-audit for?
Solo builders and small teams shipping Docker Compose stacks who want MCP-triggered security review from their coding agent.
When should I use io.github.UnbearableDev/docker-compose-audit?
Use it in Ship before production deploy or after meaningful compose edits affecting secrets, ports, volumes, or image sources.
How do I add io.github.UnbearableDev/docker-compose-audit to my agent?
Configure the Apify actor streamable-http MCP URL and set Authorization to Bearer plus your Apify API token from account integrations.