Empire Build
A real, playable territory sim with genuine adjacency rules and a documented combat formula
A hand-curated chess-clock & time-control reference — formats, increments, etiquette and history
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
format_infoincrement_explainerterm_glossarytournament_time_controlclock_etiquetteformat_comparisonhistory_notebeginner_tipsTimecontrol 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
The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.
8 tools, grouped by job. Every one is read-only or compute-only.
https://timecontrol.connectorbay.com/mcpThree ways in, the same 8 tools.
https://timecontrol.connectorbay.com/mcpPOST https://timecontrol.connectorbay.com/v1/tools/<tool>https://connectorbay.com/openai/timecontrol.jsonhttps://connectorbay.com/v1/chat/completions · how it worksTimecontrol is a fully local, hand-curated chess-clock & time-control reference. It is a hosted MCP server with 8 tools such as Format info, Increment explainer, Term glossary, Tournament time control, Clock etiquette, Format comparison, published by Unify Dynamics LLC. It is independent and not affiliated with Time Control.
Add the MCP endpoint https://timecontrol.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://timecontrol.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/timecontrol.json.
No. The connector needs no sign-in and no key. An optional Pro key only raises rate limits.
Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.
Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.
A real, playable territory sim with genuine adjacency rules and a documented combat formula
A real, playable trading-and-logistics sim with genuine supply/demand price formulas and real arbitrage
A real, playable resource-management economy sim with genuine production, starvation and growth formulas
A real, playable platformer with genuine gravity, collision, and provably-solvable levels
A real, playable tower-defense engine with genuine range, damage, and gold math
A real, playable brick-breaker with tick-by-tick physics and angle-reflection bounces
https://timecontrol.connectorbay.com/mcpPOST https://timecontrol.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://timecontrol.connectorbay.com/openapi.jsonAuthorization: Bearer <key> raises rate limits.https://timecontrol.connectorbay.com/health · Tool schemas: https://timecontrol.connectorbay.com/tools.jsonA hand-curated chess-clock & time-control reference — formats, increments, etiquette and history.
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.
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.
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.
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_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.
ok: true with data, or ok: false with a structured error (bad_input, not_found, upstream_error). degraded lists optional sources that were unreachable.Retry-After. initialize and tools/list are never counted.agent@connectorbay.com · connectorbay.com/timecontrol/support
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.
Effective 25 September 2026. These terms govern use of the Timecontrol connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://timecontrol.connectorbay.com/mcphttps://timecontrol.connectorbay.com/openapi.jsonWhen 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.