Fleet Battle
A real, playable grid-based naval fleet-hunting game with a random-then-hunt AI opponent
How bluffing and bidding mechanics actually work, across dice, auctions, hidden roles and cards
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
mechanic_infomechanic_infoterm_glossarygame_examplestell_reading_tipdesign_tipfind_game_for_groupcategory_listbeginner_tipsBluff is a fully local, hand-curated reference for bluffing and bidding game mechanics. mechanic_info gives full detail on one named mechanic — how it works step by step, its psychological tension, risk shape, typical player counts, generic tell signals, real game examples and design notes — or lists every mechanic in a category if the name matches one instead, or falls back to keyword search. term_glossary defines a bluffing/bidding term or lists all 25. game_examples gives the real, factually-cited games that use a named mechanic, without reproducing any game's proprietary rules text. tell_reading_tip gives general psychological/behavioral tips for a stated context (dice bidding, auctions, hidden-role games, card-passing, remote play, or general), framed as a table-game skill, never real-money gambling advice. design_tip gives advice for designing your own bluffing or bidding game, by topic. find_game_for_group suggests which mechanics suit a given player count. category_list lists every mechanic category with its count. beginner_tips gives an ordered shortlist of starting advice for someone new to bluffing games. Keyless; fully local; zero upstream calls; nothing stored.
Sources: Original, hand-curated descriptions of widely known bluffing/bidding game mechanics as of build date; real game names cited only as factual examples, never reproduced rules text; 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://bluff.connectorbay.com/mcpA real, playable grid-based naval fleet-hunting game with a random-then-hunt AI opponent
A real, playable anagram word game — scrambled letters, real dictionary, score by length
Malayalam riddles and tongue twisters — real script, answers and wordplay explained
37 hand-curated Kannada folk riddles and tongue twisters, in real script
39 hand-verified Urdu paheliyan plus tongue twisters, in real Nastaliq script with answers
A hand-curated press-your-luck game-design reference — mechanics, real games, and genuine bust-probability math
https://bluff.connectorbay.com/mcpPOST https://bluff.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://bluff.connectorbay.com/openapi.jsonAuthorization: Bearer <key> raises rate limits.https://bluff.connectorbay.com/health · Tool schemas: https://bluff.connectorbay.com/tools.jsonHow bluffing and bidding mechanics actually work, across dice, auctions, hidden roles and cards.
Bluff is a fully local, hand-curated reference for bluffing and bidding game mechanics. mechanic_info gives full detail on one named mechanic — how it works step by step, its psychological tension, risk shape, typical player counts, generic tell signals, real game examples and design notes — or lists every mechanic in a category if the name matches one instead, or falls back to keyword search. term_glossary defines a bluffing/bidding term or lists all 25. game_examples gives the real, factually-cited games that use a named mechanic, without reproducing any game's proprietary rules text. tell_reading_tip gives general psychological/behavioral tips for a stated context (dice bidding, auctions, hidden-role games, card-passing, remote play, or general), framed as a table-game skill, never real-money gambling advice. design_tip gives advice for designing your own bluffing or bidding game, by topic. find_game_for_group suggests which mechanics suit a given player count. category_list lists every mechanic category with its count. beginner_tips gives an ordered shortlist of starting advice for someone new to bluffing games. 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. Bluff 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.
mechanic_info — Full detail for one named bluffing/bidding mechanic: how it works step by step, the psychological tension driving it, its risk shape, typical player counts, generic behavioral tell signals, real game examples, and design notes. If the name matches a category instead, lists every mechanic in it. If neither matches, falls back to a keyword search. Use for "how does the Skull bidding mechanic work", "what is an all-pay auction". Args: name.
term_glossary — Defines a bluffing/bidding term — bluff, tell, sealed bid, all-pay auction, semi-bluff, double bluff, brinkmanship, information asymmetry, and more. Omit term to get the full glossary. Use for "what's a semi-bluff", "what does brinkmanship mean in a game". Args: term.
game_examples — Real game names cited as factual examples of one named mechanic, each with a one-line factual note — never a reproduction of any game's proprietary rules text. Use for "what real games use a claim-and-challenge mechanic", "name a game built around sealed bidding". Args: mechanic.
category_list — Every bluffing/bidding mechanic category with how many mechanics are filed under it. Use for "what categories of bluffing mechanics do you cover".
tell_reading_tip — General psychological/behavioral tips for reading bluffs in a stated context, framed as a table-game skill — never real-money gambling or betting advice. Omit context for general-purpose tips that apply to any bluffing game. Use for "how do I read a bluff in a hidden-role game", "tips for spotting a bluff over voice chat". Args: context.
design_tip — Advice for designing your own bluffing or bidding game, by topic — sizing the cost of a wrong challenge, balancing public vs. private information, catch-up mechanics, escalation pacing, and more. Omit topic to list every design tip. Use for "how do I balance a bluffing game", "tips for designing a hidden-role game's faction size". Args: topic.
beginner_tips — A curated, ordered shortlist of the most useful starting advice for someone new to bluffing games in general, most essential first. Use for "what should a beginner know about bluffing games", "give me tips before I play a bluffing game for the first time". Args: count.
find_game_for_group — Suggests which bluffing/bidding mechanics suit a given player count, ranked by fit, plus a general sizing note for that group size. Use for "what bluffing games work for 8 people", "best mechanic for just 2 players". Args: player_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/bluff/support
Effective 25 September 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What Bluff is. Bluff is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for how bluffing and bidding mechanics actually work, across dice, auctions, hidden roles and cards. 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. Bluff 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 Bluff connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://bluff.connectorbay.com/mcphttps://bluff.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. Bluff never asks for them.