Dependency Coupling Fitness Function

Dependency Coupling Fitness Function MCP Connector for Claude

A+

Enforce clean architecture boundaries by validating dependency directions.

3 tools Official Updated Oct 1, 2026 Official Vinkius Partner

This MCP server acts as an architectural guardrail for your codebase. It allows AI agents to perform automated audits of software dependencies using tools like audit_imports and identify_layer. By defining prohibited relationships between layers (e.g., 'presentation cannot depend on data'), you can prevent architectural erosion and ensure that your project adheres to clean architecture principles. The server maps file paths to logical layers and checks every import statement against your specified rules.

clean-architecturedependency-validationsoftware-designcode-qualityarchitectural-fitness

3 tools expose this connector's capabilities to your AI agent.

audit_imports

Performs a full architectural audit on a file by checking all its imports

check_rule_compliance

Validates whether a dependency from one specific layer to another is permitted

identify_layer

Determines which architectural layer a specific file belongs to based on its path

See how to talk to your AI agent using Dependency Coupling Fitness Function.

Check if my current file violates any architecture rules.

The audit of `src/presentation/controller.ts` is complete. No violations were found; all imports comply with your defined architectural boundaries.

What layer does 'src/data/repository.ts' belong to?

The file `src/data/repository.ts` has been identified as belonging to the 'data' layer.

Verify if a dependency from presentation to data is allowed.

The rule check returned that this connection is not allowed under your current architecture rules.

The `identify_layer` tool parses the file path and looks for specific directory markers to determine which layer (e.g., domain, data, or presentation) the file belongs to.

Related Connectors