Docker Compose Audit MCP Server

Security audit for docker-compose.yml — 25 checks: secrets, privileges, network, volumes, images. The docker compose audit mcp server wraps that behind the Model Context Protocol, so an assistant can use it rather than through you.

What it actually does

Point any MCP-capable client (Claude Desktop, Cursor, n8n, Make, Zapier, custom agents) at this server, hand it the contents of a docker-compose.yml, 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

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

When to reach for it

This sits in the cloud and infrastructure group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by UnbearableDev; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the docker compose audit mcp server does with a few real requests.