An astronaut overseeing a futuristic data hub

Connect Circular Code Dependency Detector 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. Stop runtime errors by finding import loops in your code.

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.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

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.

A futuristic MCP client docking bay
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 Circular Code Dependency Detector.

  1. 01

    Compute coupling metrics

    This capability calculates coupling metrics for a specific module. It uses in-degree and out-degree analysis to show how much a module relies on others or how many others rely on it.

  2. 02

    Detect cycles

    This capability finds circular dependency loops within your dependency map. It identifies the specific path, such as A to B to C and back to A, that causes the cycle.

  3. 03

    Scan dependencies

    This capability crawls a directory to build a complete dependency map. It identifies how files and modules import one another across your project.

Real work

What teams actually run

01

Debugging Initialization Failures

When a service fails to start due to an import loop, your agent finds the cycle path immediately.

02

Refactoring Monoliths

Use coupling metrics to find highly interdependent modules that need to be split apart.

03

Codebase Auditing

Run a full scan to see the health of your project's dependency graph.

04

Architecture Planning

Analyze in-degree and out-degree to ensure new modules don't create bottlenecks.

One connector, every AI

Circular Code Dependency Detector 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 Circular Code Dependency Detector 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

723ms average. Fast in production.

Circular Code Dependency Detector is checked daily against the live service.

Daily averagePeak 879ms
Oct 3Today
Fastest day
575ms
Slowest day
879ms
14-day trend
Slowing+7%

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 Circular Code Dependency Detector, so you can see the experience inside your AI.

It does not authenticate your account with Circular Code Dependency Detector. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Circular Code Dependency Detector Connector

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

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

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Circular Code Dependency Detector capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "circular-code-dependency-detector-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_V2TywrXk4ZedJ9OsuD67krBjloqkZ6H14wDHFEBh/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 Circular Code Dependency Detector in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Circular Code Dependency Detector owners hand off.

Software engineers and architects who need to maintain clean codebases. You hand off the heavy lifting of dependency tracing to your AI client.

  • 01

    Backend Engineers

    They use the MCP to prevent initialization errors in Python services.

  • 02

    Frontend Developers

    They use it to manage complex import trees in TypeScript and JavaScript projects.

  • 03

    Software Architects

    They use coupling metrics to identify and refactor bottleneck modules.

FAQ

Questions Circular Code Dependency Detector owners ask.

  • 01

    What programming languages does this MCP support?

    This MCP is built for JavaScript, TypeScript, and Python projects.

  • 02

    How does it find circular dependencies?

    It uses the scan_dependencies capability to map the project and then uses detect_cycles to find the specific paths where imports loop back on themselves.

  • 03

    What are coupling metrics?

    Coupling metrics use in-degree and out-degree analysis to measure how much a module is connected to the rest of the codebase.

  • 04

    Can I use this with Cursor or VS Code?

    Yes, you can connect this MCP to any MCP-compatible client including Cursor, VS Code, Windsurf, and Claude.

  • 05

    Does this MCP host the data?

    Yes, Vinkius hosts and manages the MCP so it is ready to use immediately after you connect your client.

  • 06

    How do I start detecting cycles in my project?

    First, use the scan_dependencies capability on your project directory to generate a dependency map. Then, pass that map into detect_cycles to see all identified loops.

  • 07

    Can I analyze Python projects?

    Yes, the scanner supports python syntax alongside javascript and typescript.

Connect Circular Code Dependency Detector to Claude, Cursor, ChatGPT & more