Categories › AI & Agents › Multi-agent, orchestration & workflows
iLang runtime for any AI: load the protocol, validate iLang text, look up verbs, SOUL, Source Book.
Remote server: your requests and data go to mcp.ilang.ai. Claude Code: claude mcp add --transport http ilang https://mcp.ilang.ai/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
ilang_runtime — iLang is a specification between humans and AI: before the AI acts, it defines what that action is authorized to become; after, code checks ilang_runtime_lite — Return iLang runtime lite: the two syntaxes, the verb table (88 verbs with their 13 Greek aliases), the 29 modifiers, the error codes, the dilang_full — Return a section of the full specification that the core runtime leaves out, found by its heading (for example "Declaration Grammar" or "Bouilang_validate — Check iLang text with the canon grammar and registry validator. Returns error, warning and info counts and each finding with its line, code ilang_lookup — [GET:@DICT|whr=q=term]=>[Ω] Look up an iLang verb, modifier, entity or declaration by name, alias or meaning. Returns type, name, alias, catilang_faq — [GET:@FAQ|whr=q=question]=>[Ω] Return the published ilang.ai FAQ entries closest to a question about the protocol (what it is, MCP/A2A compailang_soul — [GET:@SOUL|whr=form]=>[Ω] Return SOUL 2.0, the published iLang document that sets how an AI behaves by default: a judgment layer for its defilang_source_book — [GET:@SOURCE_BOOK|whr=form]=>[Ω] Return Source Book 2.9, the engineering book every iLang engineering book is anchored to: pasted into an agilang_book_check — [CHEK:@BOOK|whr=rubric_A1_A2]=>[Ω] Run the Source Book's two code checks on an engineering book: A1, the text opens and closes with the ::ILNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.