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

Trading Card

A generic, cross-game reference for CCG/TCG mechanics, rarity tiers, deck rules and formats

Unify Dynamics LLC

Documentation
Tools9read-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.

What's a mana curve?
Tools called
mechanic_info
What mechanics involve card advantage?
Tools called
mechanic_search
What do you cover?
Tools called
category_list
What's a secret rare?
Tools called
rarity_tier_explainer
How many cards go in a singleton constructed deck?
Tools called
deck_construction_rule
What's booster draft?
Tools called
tournament_format_info
What tournament format works for a 4-player group?
Tools called
find_format_for_group
What does netdecking mean?
Tools called
term_glossary
Which real games use a resource system like Magic's lands?
Tools called
game_examples

About

Tradingcard is a fully local, hand-curated, original cross-game reference for CCG/TCG mechanics. mechanic_info gives one mechanic's full detail — a resource system, a card type, a core gameplay mechanic, or a deck archetype; mechanic_search searches by keyword; category_list gives an overview with counts. rarity_tier_explainer walks through a named rarity-tier system tier by tier. deck_construction_rule explains a construction format's deck-size and copy limits. tournament_format_info explains a tournament format's structure and player-count fit; find_format_for_group suggests formats for a given group size. term_glossary defines common player jargon. game_examples names real games that illustrate a mechanic in practice, referenced factually and never as a card database. Keyless; fully local; zero upstream calls; nothing stored.

Sources: Hand-curated, original cross-game CCG/TCG mechanics reference as of build date; real games referenced factually as examples only; 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

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

OpenAPI
Mechanics3 tools
  • Mechanic infoFull detail for one generic CCG/TCG mechanic — a resource system, a card type, a core gameplay mechanic, or a deck archetype: its summary, how it…
  • Mechanic searchKeyword search across every mechanic's name, category, summary, details and related terms.
  • Category listAn overview of everything this connector covers: mechanic categories with counts (Resource Systems, Card Types, Core Mechanics, Deck Archetypes),…
Rules & Formats4 tools
  • Rarity tier explainerExplains a named rarity-tier system tier by tier: the tiered common/uncommon/rare/mythic symbol system, the numbered-parallel/insert system used…
  • Deck construction ruleExplains one deck-construction format's rules: deck size limits, per-card copy limits, and any extra card pools (sideboard, extra deck).
  • Tournament format infoExplains one tournament format: its structure, typical player-count range, typical round length, and what it's good for.
  • Find format for groupSuggests tournament formats whose typical player-count range fits a given group size, from 2-player constructed matches up to large multiplayer…
Reference2 tools
  • Term glossaryDefinitions of common CCG/TCG player jargon — topdeck, curve, meta/metagame, netdecking, tech choice, power creep, mana screw, flood, Swiss…
  • Game examplesNames real games that illustrate a given generic mechanic in practice — for example, which real games use an automatic-growth resource system…

Information

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

More like this

Bluff

How bluffing and bidding mechanics actually work, across dice, auctions, hidden roles and cards

Live · MCP + REST8 tools

Deduction

How elimination-deduction games work — mechanics, logic-grid puzzles, and how to design your own

Live · MCP + REST8 tools

Bingo

A hand-curated numbers-calling game reference — 75/90/80-ball Bingo, Housie/Tambola, Keno

Live · MCP + REST9 tools

Icebreaker

A hand-curated icebreaker & team-building game reference — how to run them, for how many, and how long they take

Live · MCP + REST8 tools

Riddle

A hand-curated riddle and brain-teaser reference — wordplay, logic, lateral thinking and math

Live · MCP + REST8 tools

Quizmaster

A hand-curated trivia-night hosting and format reference — round formats, scoring, tiebreakers and planning

Live · MCP + REST8 tools

Documentation

Back to top

Tradingcard — connector documentation

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

What Tradingcard is for

"What's a mana curve?", "how does rarity work in trading card games?", "how many cards go in a constructed deck?", "what's booster draft?", "what does netdecking mean?" — a generic, cross-game reference for how collectible/trading card games (CCG/TCG) are commonly designed and played, answered in original language rather than any one game's proprietary rulebook text.

What it does

mechanic_info gives one mechanic's full detail — a resource system, a card type (creature, spell, land- equivalent, equipment, aura, persistent hero, reactive trap), a core gameplay mechanic, or a deck archetype — for 32 mechanics in all. mechanic_search searches by keyword across every mechanic; category_list gives an overview of every collection this connector covers, with counts. rarity_tier_explainer walks through a named rarity-tier system tier by tier. deck_construction_rule explains one construction format's deck-size limits, copy-per-card limits, and extra card pools. tournament_format_info explains a tournament format's structure, typical player counts, and what it's good for. find_format_for_group suggests formats that fit a given player count. term_glossary defines common player jargon. game_examples names real games that illustrate a given mechanic in practice, referenced factually and never as a card database.

What it is not

Not a database of any single game's proprietary card pool, exact current rules text, errata, or banned/restricted list. This is a reference for understanding the concepts and vocabulary that recur across the genre; always check a specific game's current official rules before a real tournament.

Tools

Mechanics

mechanic_info — Full detail for one generic CCG/TCG mechanic: its summary, how it works, design purpose, and related terms. Use for "what's a mana curve", "explain the aggro archetype". Args: name.

mechanic_search — Keyword search across every mechanic's name, category, summary, details and related terms. Use for "mechanics about card advantage". Args: query.

category_list — An overview of everything this connector covers: mechanic categories with counts, plus how many rarity systems, deck-construction formats, tournament formats and glossary terms are available.

Rules & Formats

rarity_tier_explainer — Explains a named rarity-tier system tier by tier. Use for "what's a secret rare". Args: system.

deck_construction_rule — Explains one deck-construction format's rules: deck size, copy limits, extra pools. Use for "how many cards in a constructed deck". Args: format.

tournament_format_info — Explains one tournament format's structure, player counts, and best use. Use for "what's booster draft". Args: name.

find_format_for_group — Suggests tournament formats that fit a given player count. Args: player_count.

Reference

term_glossary — Definitions of common CCG/TCG player jargon; omit term to list all. Args: term (optional).

game_examples — Real games that illustrate a given mechanic in practice, referenced factually. Args: mechanic.

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). 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/tradingcard/support

Privacy policy

Back to top

Tradingcard — Privacy Policy

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

What Tradingcard is. Tradingcard is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for a hand-curated, fully local, generic cross-game reference to collectible/trading card game (CCG/TCG) mechanics — resource systems, card types, core mechanics, deck archetypes, rarity-tier systems, deck-construction rules, tournament formats, a jargon glossary, and factual real-game cross-references. 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 — a mechanic name, a search keyword, a rarity-system name, a deck-construction or tournament-format name, a player count, or a glossary term — 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. Tradingcard 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

Tradingcard — Terms of Service

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

  1. The Service. Tradingcard returns a hand-curated, fully local, generic cross-game reference to collectible/ trading card game (CCG/TCG) mechanics — resource systems, card types, core mechanics, deck archetypes, rarity-tier systems, deck-construction rules, tournament formats, a jargon glossary, and factual real-game cross-references. It is accessed through an AI assistant or directly over MCP or HTTP.
  2. Original reference, not a rules engine. Tradingcard is an independent, original reference for understanding concepts and vocabulary shared across the CCG/TCG genre. It is not a database of any specific game's proprietary card pool, current rules text, errata, or banned/restricted list, and does not enforce or adjudicate any real game's rules. Real games are named only as factual illustrative examples.
  3. Reference, not current official rules. Content reflects general, widely observed CCG/TCG design practice as of the build date stated in the Service's own data. Specific games change their rules, formats, and card pools constantly — always verify against a game's current official rules and organized-play policy before a real tournament.
  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, injury, or damage arising from use of, or reliance on, the Service — including reliance on it for a real tournament's rules or eligibility. 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/tradingcard

Support

Back to top

Trading Card 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. Trading Card never asks for them.

Get Trading Card

Free · No sign-in · Read-only

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

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