Does this MCP check for general bugs or just structure?

It focuses strictly on architectural structure and dependency rules. It validates things like layer boundaries and circular references, not runtime logic bugs. It's a structural integrity check.

What is AST analysis, and why do I need it?

AST stands for Abstract Syntax Tree. It's a way of representing code structure that lets the MCP analyze the code's grammar and relationships, ensuring it follows the rules you set up.

Can I check the whole project at once?

Yes. You can use the project compliance summary capability to get a high-level, aggregate score and a list of all violations across the entire codebase.

Is this better than standard linting capabilities?

Linting checks syntax and style. This MCP goes deeper, checking the relationships between modules and ensuring the overall architecture remains sound, which is a higher level of validation.

How does the capability detect circular dependencies?

The capability builds a mathematical dependency graph from your source code and uses cycle detection algorithms to identify any loops where modules depend on each other.

Can I enforce specific naming conventions?

Yes, you can use the structural tier rules to enforce conventions like PascalCase for components or specific file-system organization.

What is the difference between the validation capabilities?

Use validate_file_compliance_tool for granular file checks, check_module_relationships_tool for testing a single dependency link, and get_project_compliance_summary_tool for a full project overview.

An astronaut overseeing a futuristic data hub

Download PDF Markdown Version

Connect Architectural Constraint Enforcer to your AI

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Keep your codebase structurally sound and dependency-free.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 3 capabilities

We ship only the actions that matter.

Capability set01 / 01

01-03

3 capabilities in this set.

Part of 3 available through Architectural Constraint Enforcer.

01
Get project compliance summary tool
Provides a high-level overview of the entire project's health against the defined constraints
02
Validate file compliance tool
Checks if a specific file or a set of changed files adheres to the provided architectural rules
03
Check module relationships tool
Answers if a specific relationship between two modules is permitted under the current architecture

Real work

What teams actually run

Pull Request Review

Before merging, ask your AI client to validate the changed files. It confirms the new code respects existing architectural rules.

Refactoring Large Modules

When restructuring a core service, use the MCP to check all module relationships to ensure no unintended dependencies are created.

Pre-Deployment Audit

Run the project compliance summary capability to get a final score and list any minor violations across the entire codebase.

Onboarding New Team Members

Use the MCP to quickly demonstrate the project's structural rules, giving new hires an immediate understanding of the architecture.

One connector, every AI

Architectural Constraint Enforcer works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put Architectural Constraint Enforcer to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

816ms average. Fast in production.

Architectural Constraint Enforcer is checked daily against the live service.

Daily averagePeak 1166ms

Oct 3Today

Fastest day: 665ms
Slowest day: 1166ms
14-day trend: Improving-12%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 3 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Architectural Constraint Enforcer, so you can see the experience inside your AI.

It does not authenticate your account with Architectural Constraint Enforcer. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Architectural Constraint Enforcer Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_ABN42UMDeFDMFiU7B07G2iOsvGJgfBjkHF0uHeMU/mcp

Claude Desktop

Follow the steps below to connect in seconds.

1In Claude Desktop, open Settings → Connectors.
2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
3Click Add and start a new chat — Architectural Constraint Enforcer capabilities are ready to use.

Configuration · claude_desktop_config.jsonCopy

{
  "mcpServers": {
    "architectural-constraint-enforcer-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_ABN42UMDeFDMFiU7B07G2iOsvGJgfBjkHF0uHeMU/mcp"
    }
  }
}

Claude
ChatGPT
Cursor
VS Code
Windsurf
Claude Code
JetBrains
Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Architectural Constraint Enforcer in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Architectural Constraint Enforcer owners hand off.

Software Architects and Senior Engineers use this MCP constantly. If you're responsible for maintaining a large, complex codebase, this capability is essential. It lets your AI client act as a tireless code reviewer, enforcing rules that would otherwise be missed during manual review.

01
Software Architect
Defines and enforces the structural rules that the AI uses to validate code changes.
02
Senior Developer
Uses the MCP to validate pull requests and ensure new features don't introduce dependency violations.
03
DevOps Engineer
Runs the compliance summary to check the overall health of the repository before major deployments.

FAQ

Questions Architectural Constraint Enforcer owners ask.

01
Does this MCP check for general bugs or just structure?
It focuses strictly on architectural structure and dependency rules. It validates things like layer boundaries and circular references, not runtime logic bugs. It's a structural integrity check.
02
What is AST analysis, and why do I need it?
AST stands for Abstract Syntax Tree. It's a way of representing code structure that lets the MCP analyze the code's grammar and relationships, ensuring it follows the rules you set up.
03
Can I check the whole project at once?
Yes. You can use the project compliance summary capability to get a high-level, aggregate score and a list of all violations across the entire codebase.
04
Is this better than standard linting capabilities?
Linting checks syntax and style. This MCP goes deeper, checking the relationships between modules and ensuring the overall architecture remains sound, which is a higher level of validation.
05
How does the capability detect circular dependencies?
The capability builds a mathematical dependency graph from your source code and uses cycle detection algorithms to identify any loops where modules depend on each other.
06
Can I enforce specific naming conventions?
Yes, you can use the structural tier rules to enforce conventions like PascalCase for components or specific file-system organization.
07
What is the difference between the validation capabilities?
Use validate_file_compliance_tool for granular file checks, check_module_relationships_tool for testing a single dependency link, and get_project_compliance_summary_tool for a full project overview.

Explore

More in Developer Tools

Connect Architectural Constraint Enforcer to Claude, Cursor, ChatGPT & more

Your AI does the work. We keep it safe and sound.

Each Connector runs inside its own sealed environment.

One switch stops every agent. Instantly.

Spending limits that pause instead of surprise.

We ship only the actions that matter.

01-03

Get project compliance summary tool

Validate file compliance tool

Check module relationships tool

What teams actually run

Pull Request Review

Refactoring Large Modules

Pre-Deployment Audit

Onboarding New Team Members

Building your own app? The connector is yours to use.

Architectural Constraint Enforcer Connector

Claude Desktop

Software Architect

Senior Developer

DevOps Engineer

Does this MCP check for general bugs or just structure?

What is AST analysis, and why do I need it?

Can I check the whole project at once?

Is this better than standard linting capabilities?

How does the capability detect circular dependencies?

Can I enforce specific naming conventions?

What is the difference between the validation capabilities?

Dependency Coupling Fitness Function AI Connector

Code Integrity Prover AI Connector

Circular Code Dependency Detector AI Connector

Dependency Resolution Engine AI Connector

Suggestions

Python Code Safety Linter AI Connector

Postgres Migration Dependency Resolver AI Connector

Task DAG Dependency Resolver AI Connector

CodeRabbit AI Connector