An astronaut overseeing a futuristic data hub

Connect Execution Circuit Breaker to ChatGPT and Claude

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 your agent from hitting broken endpoints repeatedly.

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 Execution Circuit Breaker.

  1. 01

    Record success

    This capability tells the circuit breaker that an operation worked. It resets the failure counter to zero so the agent can keep working normally.

  2. 02

    Record failure

    This capability reports a failed attempt to the circuit breaker. It increments the error count toward the threshold that trips the circuit.

  3. 03

    Get circuit status

    This capability checks if the circuit is currently allowing execution. It returns whether the agent is permitted to proceed or if the circuit is tripped.

Real work

What teams actually run

01

API Downtime Protection

Stop an agent from hammering a third-party API that is currently returning 500 errors.

02

Autonomous Loop Control

Ensure an agent doesn't get stuck in a loop trying to fix a bug that is actually a permission issue.

03

Resource Management

Limit the number of attempts an agent makes on a specific task before it stops and asks for help.

04

System Stability

Use the circuit breaker pattern to prevent a single failing capability from crashing the entire agentic process.

One connector, every AI

Execution Circuit Breaker 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 Execution Circuit Breaker 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

733ms average. Fast in production.

Execution Circuit Breaker is checked daily against the live service.

Daily averagePeak 1068ms
Oct 3Today
Fastest day
564ms
Slowest day
1068ms
14-day trend
Slowing+10%

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 Execution Circuit Breaker, so you can see the experience inside your AI.

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

Execution Circuit Breaker Connector

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

Connector linkhttps://edge.vinkius.com/vk_preview_tc18N6tcK58kxfIUS6HQRcmvWe8g1t4fxyqP2fej/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 — Execution Circuit Breaker capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "execution-circuit-breaker-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_tc18N6tcK58kxfIUS6HQRcmvWe8g1t4fxyqP2fej/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 Execution Circuit Breaker in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Execution Circuit Breaker owners hand off.

This is for developers building autonomous agents that interact with unstable or third-party APIs.

  • 01

    AI Engineer

    Building agentic workflows that need to handle external service downtime gracefully.

  • 02

    DevOps Engineer

    Monitoring and controlling the reliability of automated capability-calling loops.

  • 03

    Backend Developer

    Implementing stability patterns to protect downstream services from agent-driven retry storms.

FAQ

Questions Execution Circuit Breaker owners ask.

  • 01

    What is a circuit breaker in AI?

    It is a pattern that stops an agent from repeatedly trying an operation that is failing. It prevents the agent from wasting resources on broken processes.

  • 02

    How does this MCP prevent cascading failures?

    By monitoring consecutive errors and tripping the circuit to an OPEN state, it stops the agent from making more calls until the service is stable.

  • 03

    Which AI clients can use this MCP?

    You can use this with any MCP-compatible client including Claude, Cursor, Windsurf, and VS Code.

  • 04

    Does this MCP host the logic?

    Yes, Vinkius hosts the MCP, so you don't need to manage the execution or the state yourself.

  • 05

    How do I reset the failure count?

    You use the record_success capability to notify the MCP that an operation worked, which resets the consecutive failure tally.

  • 06

    What does it mean when the circuit is in an OPEN state?

    An OPEN state means the failure threshold has been reached, and all execution attempts are currently blocked to allow for a cooldown period.

  • 07

    How can I check if I am allowed to execute a task?

    You should use the get_circuit_status capability. It will return whether the state is CLOSED, OPEN, or HALF_OPEN and provide a shouldExecute flag.

  • 08

    Does this system use real-world time?

    No, the system uses a deterministic integer-based tick counter to ensure all state transitions are perfectly reproducible in testing environments.

Connect Execution Circuit Breaker to Claude, Cursor, ChatGPT & more