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

Ancient Games

A hand-curated ancient board games reference — Senet, Ur, Petteia, Latrunculi, Tafl, Patolli, Liubo

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 was Senet actually played?
Tools called
game_info
rule_lookup
What do we actually know about the Royal Game of Ur versus what's guessed?
Tools called
reconstruction_note
What's the difference between Petteia and Latrunculi?
Tools called
game_info
rule_lookup
What ancient board games come from Mesopotamia?
Tools called
games_by_region
What ancient games were played during the Viking Age?
Tools called
games_by_era
What's the oldest board game in this reference?
Tools called
timeline_overview
What's a rosette square?
Tools called
term_glossary
Give me beginner tips for Hnefatafl.
Tools called
beginner_tips

About

Ancientgames is a fully local, hand-curated historical/archaeological reference for seven ancient board games. game_info gives one game's region, era, players, equipment, objective and a plain-language summary. rule_lookup explains a specific rule or mechanic within a named game, tagged confirmed, reconstructed, or debated — genuine scholarly uncertainty runs through most of this topic, and only the Royal Game of Ur has a surviving ancient rules text. term_glossary defines shared terms like custodian capture, rosette square, TLV pattern, and dux. games_by_region and games_by_era browse the collection by place or period. reconstruction_note lays out exactly what's archaeologically confirmed versus reconstructed or debated for one game, with key evidence. timeline_overview orders every game from oldest to most recent attested evidence. beginner_tips gives a curated shortlist for trying a game's modern reconstructed rules. Keyless; fully local; zero upstream calls; nothing stored.

Sources: Hand-curated, original explanations of widely documented archaeology and historiography of ancient board games 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
Look Up a Game3 tools
  • Game infoFull overview of one ancient board game: region, era/date range, player count, equipment, objective, a plain-language summary, and its overall…
  • Rule lookupExplains one specific rule or mechanic within a named ancient game — movement, capture, special squares, the randomizer, winning conditions, and…
  • Beginner tipsA curated, ordered shortlist of tips for someone trying a named game's modern reconstructed rules for the first time, from most to least essential.
Browse by Region & Era3 tools
  • Games by regionEvery ancient game associated with a named region — Egypt, Mesopotamia, Greece, Rome, Scandinavia & Northern Europe, Mesoamerica, China, and their…
  • Games by eraEvery ancient game associated with a named era or historical period tag — Bronze Age, Classical Antiquity, Viking Age, Han Dynasty, Post-Classic…
  • Timeline overviewEvery game in this reference ordered from oldest to most recent attested evidence, each with its human-readable approximate date range (not a…
What's Actually Known2 tools
  • Reconstruction noteThe honesty tool: for one named game, lays out exactly what's archaeologically confirmed (finds, dates, findspots) versus what's scholarly…
  • Term glossaryDefines a term shared across these ancient games — custodian capture, race game, rosette square, boustrophedon path, TLV pattern, dux, hnefatafl,…

Information

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

More like this

Esport

A hand-curated esports reference — genres, tournament formats, team roles, terms and history

Live · MCP + REST8 tools

Cartridge

A hand-curated retro console & collecting reference — generations, grading, preservation and repair

Live · MCP + REST9 tools

Nimber

A hand-curated Nim & combinatorial game theory reference — genuine nim-sum math, winning moves, and the theory behind them

Live · MCP + REST8 tools

Lockbox

A hand-curated escape-room puzzle-design reference — mechanisms, puzzle types, hint systems, and real capacity-planning logic

Live · MCP + REST8 tools

Cryptex

A general puzzle-solving technique reference — sudoku, cryptic crosswords, logic grids, nonograms and more

Live · MCP + REST8 tools

Speedcube

A hand-curated speedcubing reference — notation, methods, puzzle types, terms and competition formats

Live · MCP + REST8 tools

Documentation

Back to top

Ancientgames — connector documentation

  • MCP endpoint: https://ancientgames.connectorbay.com/mcp
  • REST API: POST https://ancientgames.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://ancientgames.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://ancientgames.connectorbay.com/health · Tool schemas: https://ancientgames.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/ancientgames · agent@connectorbay.com

What Ancientgames is for

A hand-curated ancient board games reference — Senet, Ur, Petteia, Latrunculi, Tafl, Patolli, Liubo.

What it does

Ancientgames is a fully local, hand-curated historical/archaeological reference for seven ancient board games. game_info gives one game's region, era, players, equipment, objective and a plain-language summary. rule_lookup explains a specific rule or mechanic within a named game, tagged confirmed, reconstructed, or debated — genuine scholarly uncertainty runs through most of this topic, and only the Royal Game of Ur has a surviving ancient rules text. term_glossary defines shared terms like custodian capture, rosette square, TLV pattern, and dux. games_by_region and games_by_era browse the collection by place or period. reconstruction_note lays out exactly what's archaeologically confirmed versus reconstructed or debated for one game, with key evidence. timeline_overview orders every game from oldest to most recent attested evidence. beginner_tips gives a curated shortlist for trying a game's modern reconstructed rules. 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. Ancientgames 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

Look Up a Game

game_info — Full overview of one ancient board game: region, era/date range, player count, equipment, objective, a plain-language summary, and its overall archaeological status (how well its rules are actually known). Use for "what is senet", "tell me about the Royal Game of Ur", "what is liubo". Args: name.

rule_lookup — Explains one specific rule or mechanic within a named ancient game — movement, capture, special squares, the randomizer, winning conditions, and more — each explicitly tagged with how certain it is: confirmed by archaeology/text, scholarly reconstruction, or actively debated. Rules for several of these games are only partially known, reconstructed from archaeology and scattered literary references rather than a surviving rulebook — this tool says so explicitly per rule rather than presenting a reconstruction as settled fact. Use for "how does capture work in Latrunculi", "what's the movement rule in the Royal Game of Ur", "is the tafl capture rule confirmed or guessed". Args: game, topic.

beginner_tips — A curated, ordered shortlist of tips for someone trying a named game's modern reconstructed rules for the first time, from most to least essential. Use for "give me tips for playing senet", "how should a beginner approach hnefatafl", "tips for the Royal Game of Ur". Args: game, count.

Browse by Region & Era

games_by_region — Every ancient game associated with a named region — Egypt, Mesopotamia, Greece, Rome, Scandinavia & Northern Europe, Mesoamerica, China, and their common regional aliases (e.g. Viking, Near East, Aztec Empire). Use for "what board games are from ancient Egypt", "any games from the Viking world", "what's the Chinese game in this reference". Args: region.

games_by_era — Every ancient game associated with a named era or historical period tag — Bronze Age, Classical Antiquity, Viking Age, Han Dynasty, Post-Classic Mesoamerica, and more. Use for "what games are from the Bronze Age", "any ancient games from the Viking Age", "what was played during the Han Dynasty". Args: era.

timeline_overview — Every game in this reference ordered from oldest to most recent attested evidence, each with its human-readable approximate date range (not a falsely precise single year), region, and archaeological status. Use for "what's the oldest board game here", "put these ancient games in chronological order", "timeline of ancient board games".

What's Actually Known

reconstruction_note — The honesty tool: for one named game, lays out exactly what's archaeologically confirmed (finds, dates, findspots) versus what's scholarly reconstruction or actively debated among historians, plus the key evidence behind each. Use this before treating any 'how to play' ruleset as historically certain. Use for "what do we actually know about how senet was played", "is the tafl ruleset confirmed", "how reliable is the Royal Game of Ur reconstruction". Args: game.

term_glossary — Defines a term shared across these ancient games — custodian capture, race game, rosette square, boustrophedon path, TLV pattern, dux, hnefatafl, tablut, macuilxochitl, provenance, and more — or lists every term in the glossary when none is given. Use for "what's a rosette square", "what does 'dux' mean", "what's custodian capture", "list ancient game terms". Args: term.

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/ancientgames/support

Privacy policy

Back to top

Ancientgames — Privacy Policy

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

What Ancientgames is. Ancientgames is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for a hand-curated ancient board games reference — Senet, Ur, Petteia, Latrunculi, Tafl, Patolli, Liubo. 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. Ancientgames 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

Ancientgames — Terms of Service

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

  1. The Service. Ancientgames is a fully local, hand-curated historical/archaeological reference for seven ancient board games.
  2. A reference, not professional advice. Ancientgames 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/ancientgames

Support

Back to top

Ancient Games 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. Ancient Games never asks for them.

Get Ancient Games

Free · No sign-in · Read-only

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

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