# Docker Compose Validator MCP

## Overview
- **Category:** infrastructure
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_hKdNBGILYev8XoFgza7ajUbQQqHY0xCzQbMRppYf/mcp
- **Tags:** docker, compose, validation, devops, infrastructure

## Tools

### audit_dependency_graph
Detect circular startup chains and broken service references

### detect_network_collisions
Identify overlapping host port mappings

### validate_structure
yml file.

Validate the basic structural requirements of a Compose file

### verify_resource_integrity
Ensure services have valid sources and environment/volume references are sound

## Prompt Examples

**Prompt:** 
```
Check if this docker-compose file is valid: 'services:
  web:
    image: nginx
  db:
    image: postgres'
```

**Response:** 
```
The structure is valid. Both the web and db services are correctly defined with images.
```

**Prompt:** 
```
Are there any port conflicts in these services: {"web": {"ports": ["80:80"]}, "proxy": {"ports": ["80:80"]}}?
```

**Response:** 
```
Yes, a collision was detected on host port 80 between the web and proxy services.
```

**Prompt:** 
```
Check for broken dependencies in: {"web": ["db"], "db": ["redis"]}
```

**Response:** 
```
No circular paths or broken references were found in the dependency graph.
```

## Frequently Asked Questions

**What can this MCP server validate?**
It validates YAML structure, detects host port collisions, audits dependency graphs for circular loops, and verifies resource integrity like images and volumes.

**How do I check for port conflicts?**
You can use the `detect_network_collisions` tool by providing your service definitions as a JSON string.

**Can it detect circular dependencies?**
Yes, the `audit_dependency_graph` tool specifically identifies loops in your service dependency chains.