Skip to content
BEAD

Docker Compose Validator

Lint a docker-compose.yml — parse the YAML, walk the structure, and flag common mistakes.

DeveloperDiagnostics
✓ No issues found.
</>Use this tool programmaticallycurl · JavaScript · MCP

Same tool, callable from any HTTP client or from Claude (via MCP). Anonymous: 100 req/day per IP. Sign up for 1,000 req/day.

curl
curl https://api.b-e-a-d.com/tools/docker-compose-validator/run \
  -H "Content-Type: application/json" \
  -d '{
  "input": "your input here"
}'
JavaScript (fetch)
const res = await fetch("https://api.b-e-a-d.com/tools/docker-compose-validator/run", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
  "input": "your input here"
}),
});
const data = await res.json();
console.log(data.result);
MCP (Claude Desktop / Claude Code)
# In Claude Desktop / Claude Code, add to your MCP config:
{
  "mcpServers": {
    "bead": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.b-e-a-d.com"]
    }
  }
}

# Then ask Claude to call:
mcp__bead__bead_docker_compose_validator

Full reference: developer docs · OpenAPI spec

What this checks

  • Valid YAML (via js-yaml).
  • Top-level keys against the Compose spec (services / volumes / networks / configs / secrets / version / name / include).
  • Each service has at least image or build.
  • Restart policies are one of no | always | on-failure | unless-stopped.
  • Port mappings parse cleanly and don't clash across services on the host side.
  • depends_on targets exist.

You might also like