Script Guide

Script Guide — connector documentation

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

What Lipi (Script Guide) is for

The question that comes up the moment more than one Indian script enters a conversation — is Gujarati's script really Devanagari without the head-line, does Assamese actually have letters Bengali lacks, what does "lakh" look like written in Tamil versus Odia — answered from one hand-curated, respectful reference, rather than piecing it together from scattered pages of uneven quality.

What it does

Full script profiles and alphabet charts for all 12 major regional languages named in India's constitution that this connector covers — Hindi, Bengali, Marathi, Telugu, Tamil, Gujarati, Urdu, Kannada, Odia, Malayalam, Punjabi and Assamese — each vowel and consonant (or, for Urdu, each letter) given with transliteration (alphabet_chart, script_info); a Brahmic-vs-Perso-Arabic classification explaining what those script families mean and how the 11 Brahmic scripts here relate to a shared ancient ancestor (script_family); each language's native numeral digit glyphs alongside a plain note on how often they're actually used versus Hindu-Arabic numerals in everyday text (numeral_glyphs); a side-by-side comparison tool showing one chosen word or number in all 12 scripts at once, every entry individually verified (compare_scripts); a plain-language explainer of practical romanization versus formal transliteration schemes like IAST and ISO 15919 (transliteration_scheme_explainer); the full language list (language_list); and a glossary of script and linguistics terms (lipi_glossary).

What it is not

Not a language-learning course, and not a claim that any one script, language or region is more standard, prestigious or "correct" than another. Every one of these languages is spoken across multiple faiths and regions — none is treated here as belonging to a single community. Assamese is verified separately from Bengali rather than assumed to be identical (it isn't: ৰ and ৱ are genuinely distinct Assamese letters), and Indian Punjabi (Gurmukhi) is kept separate from Pakistani Punjabi (Shahmukhi), which this connector does not cover. Every alphabet entry, digit glyph and comparison word was checked against an authoritative source before inclusion; an entry that couldn't be verified was left out rather than guessed, and depth is kept consistent across all 12 languages rather than letting better-documented languages crowd out the others. Fully local, zero upstream calls, nothing stored.

Tools

Script Lookup

script_info — One language's script profile: script name, script family (Brahmic or Perso-Arabic), writing direction, letter type, a distinguishing visual/structural feature, and a brief region note. Use for "what script does Odia use", "is Gujarati's script related to Hindi's". Args: language.

alphabet_chart — Full vowel and consonant (or, for Urdu, letter) inventory for one language's script, each with its romanized transliteration. Use for "show me the Devanagari vowels", "what are the Tamil consonants", "list the Urdu alphabet". Args: language.

script_family — Classifies all 12 covered languages into Brahmic-derived scripts (11 of them) vs. the one Perso-Arabic-derived script (Urdu), and explains what those families mean. Use for "which of these scripts come from the same family", "is Urdu's script different from the others".

Numerals & Comparison

numeral_glyphs — A language's native numeral digit glyphs (0-9), plus a note on how native digits are actually used today compared to the Hindu-Arabic digits (0-9) common in most running text. Use for "what do Bengali numerals look like", "does Tamil have its own digit shapes". Args: language.

compare_scripts — Shows one chosen word or number written in all 12 covered scripts side by side, each with native script, transliteration, and (implicitly) its meaning — every entry individually verified per language. Use compare_scripts to see available concepts if the given one isn't found. Use for "show me 'crore' in every script", "how do you write 'five' across all 12 languages". Args: concept.

Reference

transliteration_scheme_explainer — Plain-language explanation of practical/informal romanization (how most people actually spell Indic words in Latin letters day to day) versus formal academic transliteration schemes like IAST and ISO 15919. Use for "what's the difference between IAST and just spelling it out", "why do I see so many diacritics in academic transliterations".

language_list — Every one of the 12 covered languages with its script name and script family. Use for "which languages does this cover", "list every script family here".

lipi_glossary — Definitions of script and linguistics terms used throughout this reference — abugida, abjad, matra, virama, conjunct consonant, shirorekha, akshara, Nastaliq, Brahmi script, IAST, ISO 15919, anusvara, diacritic, schwa syncope. Use for "what's a matra", "what does abugida mean". 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/lipi/support

Lipi (Script Guide) — Privacy Policy

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

What Lipi (Script Guide) is. Lipi is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for a hand-curated pan-India script reference: alphabet charts, script-family classification, numeral glyphs, and a side-by-side script comparison tool across 12 Indian languages. 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 language name, a word/number concept, 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. Lipi (Script Guide) is a general-audience service operated by the adult using the assistant.

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

Lipi (Script Guide) — Terms of Service

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

1. The Service. Lipi returns a hand-curated pan-India script reference — script profiles, alphabet charts, script-family classification, native numeral glyphs, a side-by-side script comparison tool, and a transliteration-scheme explainer — across Hindi, Bengali, Marathi, Telugu, Tamil, Gujarati, Urdu, Kannada, Odia, Malayalam, Punjabi and Assamese, from data curated and verified as of the build date stated in its own data. It is accessed through an AI assistant or directly over MCP or HTTP.
2. A reference, not a lesson or a claim of authority. Lipi is an independent reference tool, not affiliated with or endorsed by any government, institution, or organization. It is not a substitute for a language course or a linguistics textbook, and no script or language described here is presented as more standard, prestigious or "correct" than another.
3. Languages span communities. Every language covered here is spoken across multiple faiths and regions; this Service does not treat any of them as belonging to one community, and describes commonly-documented script features rather than asserting a rule for every writer or every era.
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/lipi

Script Guide support

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

• MCP endpoint: https://lipi.connectorbay.com/mcp
• REST API: https://lipi.connectorbay.com/openapi.json
• Live status: https://lipi.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. Script Guide never asks for them.