Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Time Control icon

Time Control

A hand-curated chess-clock & time-control reference — formats, increments, etiquette and history

Unify Dynamics LLC

Documentation
Tools8read-only
Sign-inNoneno account, no key
Data keptNoneprocessed in memory
PriceFreeoptional Pro limits
StatusLiveMCP + REST
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

How long is a blitz chess game?
Tools called
format_info
What's a Bronstein delay and how is it different from an increment?
Tools called
increment_explainer
What does 'zeitnot' mean?
Tools called
term_glossary
What time control do elite classical tournaments typically use?
Tools called
tournament_time_control
Is it rude to slap the clock after moving?
Tools called
clock_etiquette
Compare rapid and classical time controls
Tools called
format_comparison
Who came up with the chess increment?
Tools called
history_note
What clock tips should a beginner know?
Tools called
beginner_tips

About

Timecontrol is a fully local, hand-curated chess-clock & time-control reference. format_info gives one speed format's (bullet, blitz, rapid, classical, correspondence) typical time range, description, common increment and how the idea carries over to other timed games; omit the name to list them all. increment_explainer covers how a time-replenishment system works — Fischer increment, Bronstein delay, simple delay, byoyomi, Canadian overtime, sudden death — with a worked example and pros/cons. term_glossary defines time-control terms (flag, zeitnot, delay, byoyomi period, adjournment, arbiter and more) or lists all of them. tournament_time_control describes the time controls typically used at a level of play — club, weekend Swiss, national championship, elite classical, online arena, correspondence, scholastic, and professional Go/Shogi for comparison — phrased qualitatively rather than as one fixed rule. clock_etiquette gives practical guidance on a clock-related courtesy or procedure, from pressing the clock to disputed flag-fall claims. format_comparison lines up two named formats' time range, increment and pace side by side. history_note gives a short history note on chess-clock and time-control evolution, or a general overview. beginner_tips gives a ranked shortlist of practical clock-management tips. This is a general reference, not the official rulebook of any federation or event. Keyless; fully local; zero upstream calls; nothing stored.

Sources: Hand-curated, original chess-clock and time-control reference content written for this connector as of build date; fully local, zero upstream calls

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.
Privacy policyTerms

What it can do

8 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Formats & Systems3 tools
  • Format infoOne speed format's (bullet, blitz, rapid, classical, correspondence) typical time range, description, common increment and how the idea carries…
  • Increment explainerHow a time-replenishment system works (Fischer increment, Bronstein delay, simple delay, byoyomi, Canadian overtime, sudden death): mechanism, a…
  • Format comparisonSide-by-side comparison of two named formats' typical time range, common increment and pace.
Practice & Reference3 tools
  • Tournament time controlTypical time controls used at a given level of play, phrased qualitatively rather than as one fixed rule — club & casual, weekend Swiss,…
  • Clock etiquettePractical guidance on a clock-related courtesy or procedure — pressing the clock, touch-move and the clock, calling an arbiter, using one hand,…
  • Term glossaryDefinitions of time-control terms — flag, flag fall, zeitnot, delay, byoyomi period, digital/analog clock, pre-move, adjournment, arbiter, and more.
History & Beginners2 tools
  • History noteA short history note on how chess clocks and time controls evolved — sandglasses, mechanical flag clocks, the move to digital, the Fischer…
  • Beginner tipsA ranked shortlist of practical clock-management tips for players new to playing on a clock — from learning your time control before you sit down…

Information

PublisherUnify Dynamics LLC
CategoryGames & entertainment · Reference
LanguagesEnglish
Built forGlobal
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://timecontrol.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide

More like this

Empire Build

A real, playable territory sim with genuine adjacency rules and a documented combat formula

Live · MCP + REST8 tools

Trade Routes

A real, playable trading-and-logistics sim with genuine supply/demand price formulas and real arbitrage

Live · MCP + REST9 tools

Resource Race

A real, playable resource-management economy sim with genuine production, starvation and growth formulas

Live · MCP + REST7 tools

Platform Mini

A real, playable platformer with genuine gravity, collision, and provably-solvable levels

Live · MCP + REST3 tools

Tower Defense

A real, playable tower-defense engine with genuine range, damage, and gold math

Live · MCP + REST4 tools

Breakout Sim

A real, playable brick-breaker with tick-by-tick physics and angle-reflection bounces

Live · MCP + REST4 tools

Documentation

Back to top

Timecontrol — connector documentation

  • MCP endpoint: https://timecontrol.connectorbay.com/mcp
  • REST API: POST https://timecontrol.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://timecontrol.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: none required. An optional Authorization: Bearer <key> raises rate limits.
  • Health: https://timecontrol.connectorbay.com/health · Tool schemas: https://timecontrol.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/timecontrol · agent@connectorbay.com

What Timecontrol is for

A hand-curated chess-clock & time-control reference — formats, increments, etiquette and history.

What it does

Timecontrol is a fully local, hand-curated chess-clock & time-control reference. format_info gives one speed format's (bullet, blitz, rapid, classical, correspondence) typical time range, description, common increment and how the idea carries over to other timed games; omit the name to list them all. increment_explainer covers how a time-replenishment system works — Fischer increment, Bronstein delay, simple delay, byoyomi, Canadian overtime, sudden death — with a worked example and pros/cons. term_glossary defines time-control terms (flag, zeitnot, delay, byoyomi period, adjournment, arbiter and more) or lists all of them. tournament_time_control describes the time controls typically used at a level of play — club, weekend Swiss, national championship, elite classical, online arena, correspondence, scholastic, and professional Go/Shogi for comparison — phrased qualitatively rather than as one fixed rule. clock_etiquette gives practical guidance on a clock-related courtesy or procedure, from pressing the clock to disputed flag-fall claims. format_comparison lines up two named formats' time range, increment and pace side by side. history_note gives a short history note on chess-clock and time-control evolution, or a general overview. beginner_tips gives a ranked shortlist of practical clock-management tips. This is a general reference, not the official rulebook of any federation or event. Keyless; fully local; zero upstream calls; nothing stored.

What it is not

Not an official product of, or affiliated with, any brand, league, publisher, or organization it may factually mention. Timecontrol is a hand-curated reference and design tool, not a substitute for an official rulebook, certified instruction, or professional advice. Fully local, zero upstream calls, nothing stored.

Tools

Formats & Systems

format_info — One speed format's (bullet, blitz, rapid, classical, correspondence) typical time range, description, common increment and how the idea carries over to other timed games. Omit name to list every format. Use for "how long is a blitz game", "what's classical time control". Args: name.

increment_explainer — How a time-replenishment system works (Fischer increment, Bronstein delay, simple delay, byoyomi, Canadian overtime, sudden death): mechanism, a worked example, typical games it's used in, and pros/cons. Omit system to list them all. Use for "what's a Bronstein delay", "how does byoyomi work". Args: system.

format_comparison — Side-by-side comparison of two named formats' typical time range, common increment and pace. Use for "compare rapid and classical", "blitz vs bullet". Args: a, b.

Practice & Reference

tournament_time_control — Typical time controls used at a given level of play, phrased qualitatively rather than as one fixed rule — club & casual, weekend Swiss, national/regional championship, elite classical, online arena, correspondence, scholastic/youth, and professional Go/Shogi for comparison. Omit event_type to list them all. Use for "what time control do elite tournaments use", "what's typical for a weekend chess tournament". Args: event_type.

clock_etiquette — Practical guidance on a clock-related courtesy or procedure — pressing the clock, touch-move and the clock, calling an arbiter, using one hand, disputed flag falls, adjusting pieces, digital-vs-analog courtesy, devices near the board, online pre-move/lag norms, correspondence deadlines. Omit topic to list them all. Use for "is it rude to slap the clock", "what do I do if I think my opponent's flag fell". Args: topic.

term_glossary — Definitions of time-control terms — flag, flag fall, zeitnot, delay, byoyomi period, digital/analog clock, pre-move, adjournment, arbiter, and more. Omit term to list them all. Use for "what does zeitnot mean", "what's a flag fall". Args: term.

History & Beginners

history_note — A short history note on how chess clocks and time controls evolved — sandglasses, mechanical flag clocks, the move to digital, the Fischer increment's origin, byoyomi's origin, correspondence chess and adjournments. Omit topic for a general overview. Use for "who invented the chess clock increment", "history of byoyomi". Args: topic.

beginner_tips — A ranked shortlist of practical clock-management tips for players new to playing on a clock — from learning your time control before you sit down to not losing a won game on time. Use for "clock tips for beginners", "how do I not lose on time in a winning position". Args: count.

Conventions

  • Read-only. Every tool reads public data or computes; nothing is written anywhere and nothing about the user is stored.
  • Result envelope. ok: true with data, or ok: false with a structured error (bad_input, not_found, upstream_error). degraded lists optional sources that were unreachable.
  • Rate limits. Free tier 60 tool calls/minute and 300/day per user (keyed on the user identifier supplied by the host agent, else client IP); Pro keys raise this. Over-limit calls return HTTP 429 with Retry-After. initialize and tools/list are never counted.

Support

agent@connectorbay.com · connectorbay.com/timecontrol/support

Privacy policy

Back to top

Timecontrol — Privacy Policy

Effective 25 September 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Timecontrol is. Timecontrol is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for a hand-curated chess-clock & time-control reference — formats, increments, etiquette and history. You interact with your assistant; the assistant sends us only the arguments needed for that one lookup.

What we receive. The arguments of each tool call, the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant, and a Pro API key if you have one), and standard server logs.

Everything is answered from a bundled, hand-curated reference file and nothing is stored. No request is forwarded to any third party — there is no upstream call at all, live or otherwise — and no query is logged in request bodies, recorded, or used to train anything.

What we do not receive or store. We do not receive your conversation with the assistant or your name, and we do not build a profile from your queries: each request is answered independently and nothing carries over between requests. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting-provider access logs, which contain IP addresses and request paths but not request bodies, are retained for up to 30 days for security and abuse prevention.

Sub-processors. None — the entire dataset is bundled with the server and answered locally. Hosting: Vercel (United States regions).

Legal bases and your rights. Our processing is necessary to provide the service you request through your assistant. Because we store no personal data beyond short-lived logs, requests to access, correct or delete personal data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. We do not sell or share personal information and do not use your data to train models.

Children. Timecontrol is a general-audience service operated by the adult using the assistant.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

Timecontrol — Terms of Service

Effective 25 September 2026. These terms govern use of the Timecontrol connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. Timecontrol is a fully local, hand-curated chess-clock & time-control reference.
  2. A reference, not professional advice. Timecontrol is an independent reference and hobby/game-design tool, not affiliated with or endorsed by any brand, organization, league, or publisher it may factually mention. It does not provide legal, financial, medical, or safety-certification advice, and is not a substitute for supervised instruction where real physical risk is involved.
  3. Content varies. Rules, terminology and conventions described here reflect commonly-cited general practice; local house rules, regional variants, and official governing-body rulebooks may differ.
  4. Acceptable use. Automated use within the published rate limits is welcome.
  5. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time.
  6. Data. Our Privacy Policy describes what we process. In short: your query is answered from a bundled reference file, and nothing is stored.
  7. Pro keys. Optional Pro API keys are issued at our discretion, are personal to the holder and may be revoked for abuse.
  8. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service. Our total liability is limited to US $100.
  9. Governing law. California law; venue in San Mateo County, California.
  10. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/timecontrol

Support

Back to top

Time Control support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Time Control never asks for them.

Get Time Control

Free · No sign-in · Read-only

Streamable HTTP, stateless, no authentication. Paste the endpoint into any MCP-capable agent.

https://timecontrol.connectorbay.com/mcp
{
  "mcpServers": {
    "timecontrol": {
      "type": "http",
      "url": "https://timecontrol.connectorbay.com/mcp"
    }
  }
}