Kite Fight

Kitefight — connector documentation

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

What Kitefight is for

Kite-fighting traditions, kite types and festivals — with genuine, prominent safety coverage.

What it does

Kitefight is a fully local, hand-curated reference on competitive kite-flying and kite-fighting. tradition_info covers real traditions — South Asian patang/manjha dueling, Afghan gudiparan bazi, Thai chula-pakpao, Japanese rokkaku battles, Brazilian pipa/cerol flying, Korean yeonnalligi, Chinese display-kite culture, and modern sport-kite competition — described factually and respectfully. kite_type_info covers 15 kite types from fighter kites to box kites and quad-line sport kites. festival_info covers real kite-flying festivals (Makar Sankranti/Uttarayan, Hamamatsu, Weifang, Bali and more) including festival-specific safety notes. term_glossary defines terms across traditions (manjha, dhil dena, gudiparan bazi, chula, rokkaku, cerol, bridle). find_kite_for_purpose suggests kite types for a stated goal. beginner_tips gives a safety-forward starter shortlist. safety_consideration is genuine, prominent safety content: glass-/abrasive-coated cutting line has caused serious injuries and deaths to bystanders and motorcyclists, injures and kills birds, and can cut the flyer's own hands — plus safer uncoated-line alternatives. regulation_note gives factual, hedged notes on where such line or kite flying itself has been restricted or banned (India, Pakistan/Punjab, Brazil, generic airspace rules) — not legal advice. 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. Kitefight 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

Culture & Reference

tradition_info — Full, respectful detail on one real kite-fighting/flying tradition: overview, cultural context, typical kites, related festivals and terms, and a safety notice when the tradition uses cutting line. Omit name to list every tradition covered. Use for "tell me about Afghan kite fighting", "what is patangbazi", "how does Thai chula-pakpao work". Args: name.

kite_type_info — Full detail on one kite type: origin, structure/build, typical purpose, and difficulty. Omit name to list every kite type covered. Use for "what is a rokkaku kite", "what's a good beginner kite", "how is a chula kite built". Args: name.

festival_info — Full detail on one real kite-flying festival: region, timing, description, and a festival-specific safety note where relevant. Omit name to list every festival covered. Use for "when is Uttarayan", "what happens at the Hamamatsu Kite Festival", "is Basant still celebrated with kites". Args: name.

term_glossary — Definitions of kite-flying and kite-fighting terms across traditions — manjha, patang, dhil dena, gudiparan bazi, tar, chula, pakpao, rokkaku, cerol, bridle, spine and spar, tail, and more. Use for "what does manjha mean", "what's the difference between chula and pakpao", "what is a bridle". Args: term.

Get Recommendations

find_kite_for_purpose — Suggests 1-4 suitable kite types for a stated purpose, keyword-matched against each kite type's tagged purposes. Use for "what kite should a beginner fly", "best kite for dueling", "what kite is stable in strong wind". Args: purpose.

beginner_tips — A curated, safety-forward shortlist of tips for someone new to kite flying, ordered from most to least essential. Use for "how do I start kite flying safely", "tips for a first-time kite flyer". Args: count.

Safety & Regulation

safety_consideration — Genuine, prominent safety information on kite-fighting hazards — above all, glass-/abrasive-coated cutting line (manjha, tar, cerol), which has caused serious injuries and deaths to bystanders and motorcyclists, severely injures and kills birds, and can cut the flyer's own hands. Also covers power lines, traffic, rooftops, severe weather, line disposal, and safer uncoated-line alternatives. Omit topic to list every topic covered. Use for "is manjha dangerous", "what are the risks of kite fighting", "is there a safer kite line". Args: topic.

regulation_note — Factual, hedged notes on where glass-/abrasive-coated kite line or kite flying itself has been restricted or banned (India, Pakistan/Punjab, Brazil) plus generic airspace/altitude rules — not legal advice, and rules change over time. Omit topic to list every topic covered. Use for "is manjha legal in India", "was kite flying banned in Pakistan", "can I fly a kite near an airport". Args: topic.

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

Kitefight — Privacy Policy

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

What Kitefight is. Kitefight is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for kite-fighting traditions, kite types and festivals — with genuine, prominent safety coverage. 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. Kitefight is a general-audience service operated by the adult using the assistant.

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

Kitefight — Terms of Service

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

1. The Service. Kitefight is a fully local, hand-curated reference on competitive kite-flying and kite-fighting.
2. A reference, not professional advice. Kitefight 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/kitefight

Kite Fight support

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

• MCP endpoint: https://kitefight.connectorbay.com/mcp
• REST API: https://kitefight.connectorbay.com/openapi.json
• Live status: https://kitefight.connectorbay.com/health

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. Kite Fight never asks for them.