What is a zombie execution?

A zombie execution is when an agent gets stuck in an infinite loop or a repetitive cycle, consuming resources without making progress.

How does this MCP calculate token budgets?

It looks at the remaining time available and the current throughput of the model to suggest a maximum token limit.

Can I use this with AutoGen or CrewAI?

Yes, this MCP is specifically designed to provide guardrails for multi-agent frameworks like those.

Does this MCP work with Claude?

Yes, you can connect this MCP to any MCP-compatible client including Claude.

How does the safety margin work?

The MCP monitors the remaining time and triggers a termination if the task enters a zone that would violate your safety threshold.

How does this prevent agent hang-ups?

It uses check_execution_status to monitor the time remaining until the global deadline. If the time left is less than or equal to the safety margin, it signals for immediate termination.

What is the purpose of the token budget?

The calculate_token_budget capability predicts how many tokens an LLM can generate within the remaining time, preventing the model from starting a response it cannot complete.

Can I use a single capability for both checks?

Yes, evaluate_task_safety is a unified capability that checks the safety margin and provides the suggested token budget in one call.

An astronaut overseeing a futuristic data hub

Download PDF Markdown Version

Connect Deterministic Timeout Enforcer 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 infinite loops and wasted tokens in your agent workflows.

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 Deterministic Timeout Enforcer.

01
Calculate token budget
This capability suggests a maximum token limit for your next LLM call. It uses current throughput to ensure the model stays within your remaining time window.
02
Check execution status
This capability checks if your current task has entered a danger zone. It determines if the agent must stop immediately to respect your safety margin.
03
Evaluate task safety
This is a unified capability that handles two jobs at once. It checks if a task should terminate and provides the specific token budget for the next step.

Real work

What teams actually run

Multi-Agent Loop Control

Stop agents in frameworks like CrewAI from looping between the same two tasks forever.

Cost Management

Limit the size of LLM responses to stay within a specific token budget.

Real-time Execution Monitoring

Check if an autonomous agent is still within its allowed time window during a long run.

Predictable Agent Behavior

Ensure agents terminate gracefully before hitting system-level timeouts.

One connector, every AI

Deterministic Timeout 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 Deterministic Timeout 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

878ms average. Fast in production.

Deterministic Timeout Enforcer is checked daily against the live service.

Daily averagePeak 1014ms

Oct 3Today

Fastest day: 653ms
Slowest day: 1014ms
14-day trend: Stable0%

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 Deterministic Timeout Enforcer, so you can see the experience inside your AI.

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

Deterministic Timeout Enforcer Connector

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

Connector linkhttps://edge.vinkius.com/vk_preview_TjR6dvLKjHOYH4GEv5Sys65NLcQkEQQfQfbIfK1a/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 — Deterministic Timeout Enforcer capabilities are ready to use.

Configuration · claude_desktop_config.jsonCopy

{
  "mcpServers": {
    "deterministic-timeout-enforcer-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_TjR6dvLKjHOYH4GEv5Sys65NLcQkEQQfQfbIfK1a/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 Deterministic Timeout Enforcer in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Deterministic Timeout Enforcer owners hand off.

This MCP is built for developers and engineers running complex, autonomous agentic workflows.

01
AI Engineer
Builds multi-agent systems that need strict execution boundaries.
02
LLM Developer
Manages token costs and prevents runaway model calls.
03
Automation Architect
Designs reliable agent workflows that won't hang indefinitely.

FAQ

Questions Deterministic Timeout Enforcer owners ask.

01
What is a zombie execution?
A zombie execution is when an agent gets stuck in an infinite loop or a repetitive cycle, consuming resources without making progress.
02
How does this MCP calculate token budgets?
It looks at the remaining time available and the current throughput of the model to suggest a maximum token limit.
03
Can I use this with AutoGen or CrewAI?
Yes, this MCP is specifically designed to provide guardrails for multi-agent frameworks like those.
04
Does this MCP work with Claude?
Yes, you can connect this MCP to any MCP-compatible client including Claude.
05
How does the safety margin work?
The MCP monitors the remaining time and triggers a termination if the task enters a zone that would violate your safety threshold.
06
How does this prevent agent hang-ups?
It uses check_execution_status to monitor the time remaining until the global deadline. If the time left is less than or equal to the safety margin, it signals for immediate termination.
07
What is the purpose of the token budget?
The calculate_token_budget capability predicts how many tokens an LLM can generate within the remaining time, preventing the model from starting a response it cannot complete.
08
Can I use a single capability for both checks?
Yes, evaluate_task_safety is a unified capability that checks the safety margin and provides the suggested token budget in one call.

Explore

More in Reliability

Connect Deterministic Timeout 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

Calculate token budget

Check execution status

Evaluate task safety

What teams actually run

Multi-Agent Loop Control

Cost Management

Real-time Execution Monitoring

Predictable Agent Behavior

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

Deterministic Timeout Enforcer Connector

Claude Desktop

AI Engineer

LLM Developer

Automation Architect

What is a zombie execution?

How does this MCP calculate token budgets?

Can I use this with AutoGen or CrewAI?

Does this MCP work with Claude?

How does the safety margin work?

How does this prevent agent hang-ups?

What is the purpose of the token budget?

Can I use a single capability for both checks?

Token Counter and Budget Enforcer AI Connector

Token Budget Allocator AI Connector

Agent Token Budget Allocator AI Connector

Token Budget Allocation Optimizer AI Connector

Suggestions

Deterministic 50/30/20 Budget Engine AI Connector

Token Budget Remaining Calculator AI Connector

Natural Tokenizer Engine AI Connector

LLM Context Window Budgeter AI Connector