iLang
REMOTE · MCP.ILANG.AI
iLang runtime for any AI: load the protocol, validate iLang text, look up verbs, SOUL, Source Book.
Available components
Last scanned (16 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1369 tokens (~91/item across 15 items; 9 tools + 6 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 13 Nov 26 68
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://mcp.ilang.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ilang.ai | CN=WE1,O=Google Trust Services,C=US | 1 Nov 2026 | 30 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | c2c1a4478d8fb48e137da272fe673fe1 |
| SANs: ilang.ai, mcp.ilang.ai, *.mcp.ilang.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.ilang.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| ilang.ai. | DS published | 2371 | 13 | Verified |
| mcp.ilang.ai. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.ilang.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.ilang.ai/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ilang_book_check Check an engineering book ~135
[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 ::ILANG::v5.0::ENGINEERING_BOOK marker (exactly two such lines), and A2, the canon grammar validator reports zero errors and zero warnings (strict). Returns pass or fail per item with the validator's findings. For an agent that has no shell to run ilang_grammar_validator.py; same validator, same result.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The full text of BOOK.md |
No output schema declared.
No examples provided.
ilang_faq iLang FAQ ~75
[GET:@FAQ|whr=q=question]=>[Ω] Return the published ilang.ai FAQ entries closest to a question about the protocol (what it is, MCP/A2A comparison, prompt compression, versions, judgment layer, SOUL, the Source Book). Includes source_url.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | yes | – |
No output schema declared.
No examples provided.
ilang_full Read the full iLang text ~63
Return a section of the full specification that the core runtime leaves out, found by its heading (for example "Declaration Grammar" or "Boundary Cases"), or the whole full text when no heading is given.
| Name | Type | Req | Description |
|---|---|---|---|
| section | string | – | A heading, or part of one |
No output schema declared.
No examples provided.
ilang_lookup iLang dictionary lookup ~97
[GET:@DICT|whr=q=term]=>[Ω] Look up an iLang verb, modifier, entity or declaration by name, alias or meaning. Returns type, name, alias, category, meaning, values and source_url. not_found=true when nothing matches; never invent terms.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | yes | Term, alias or keyword, e.g. XLAT, lng, @PREV, BUDGET |
No output schema declared.
No examples provided.
ilang_runtime Load iLang ~114
iLang is a specification between humans and AI: before the AI acts, it defines what that action is authorized to become; after, code checks whether it was done right. Return the official iLang runtime, the working text of the specification (about 18,600 tokens), verified against the canon's sha256. Load it once per conversation, then use iLang internally. media=true adds the image, video and audio extension (about 18,000 tokens more).
| Name | Type | Req | Description |
|---|---|---|---|
| media | boolean | – | Add the media extension |
No output schema declared.
No examples provided.
ilang_runtime_lite Load iLang (syntax and vocabulary) ~127
Return iLang runtime lite: the two syntaxes, the verb table (88 verbs with their 13 Greek aliases), the 29 modifiers, the error codes, the declaration body forms, the registry of 32 declarations and the entity registry (25 entities), taken word for word from the canon's full runtime and checked against its sha256. About 18,000 characters, where ilang_runtime returns about 93,000. Enough to write iLang and check it with ilang_validate; it leaves out the execution and judgment layers, so load ilang_runtime when a task needs them.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ilang_soul SOUL 2.0 ~138
[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 default persona. The text comes back as the file on ilang.ai/soul/ (about 2,000 characters), followed by a JSON line with version, date, license, DOI, file url and the sha256 of the text served. Paste the text where the AI reads its instructions. form=iml returns the IML 0.5 form instead.
| Name | Type | Req | Description |
|---|---|---|---|
| form | string | – | ilang (default) or iml |
No output schema declared.
No examples provided.
ilang_source_book Source Book 2.9 ~164
[GET:@SOURCE_BOOK|whr=form]=>[Ω] Return Source Book 2.9, the engineering book every iLang engineering book is anchored to: pasted into an agent app that has a shell, files and the web, and given a tutorial, the agent confirms the tutorial's numbers against official sources and writes BOOK.md, an English iLang book any agent can carry out. The text comes back as the file on ilang.ai/source-book/ (about 7,600 characters), followed by a JSON line with version, date, license, DOI, file url and the sha256 of the text served. form=iml returns the IML 0.5 form instead.
| Name | Type | Req | Description |
|---|---|---|---|
| form | string | – | ilang (default) or iml |
No output schema declared.
No examples provided.
ilang_validate Validate iLang ~96
Check iLang text with the canon grammar and registry validator. Returns error, warning and info counts and each finding with its line, code and message. An E302 finding (unknown modifier) may also carry did_you_mean, the registered modifier this server suggests for the key; the suggestion is added here and is not part of the canon validator's output.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | iLang, or Markdown that carries iLang blocks |
No output schema declared.
No examples provided.
How do I install the iLang MCP server?
iLang is a hosted endpoint at https://mcp.ilang.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.ilang.ai
claude mcp add --transport http ai-ilang-mcp 'https://mcp.ilang.ai/mcp'
What is the iLang MCP server?
iLang is an MCP server listed in the public MCP registry as ai.ilang/mcp. iLang runtime for any AI: load the protocol, validate iLang text, look up verbs, SOUL, Source Book. This page covers its hosted endpoint (https://mcp.ilang.ai/mcp).
Is the iLang MCP server safe to use?
iLang scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the iLang MCP server expose?
iLang exposes 9 tools: ilang_runtime, ilang_runtime_lite, ilang_full, ilang_validate, ilang_lookup, and 4 more. Their descriptions and schemas cost roughly 1,009 tokens of context every time the server is loaded.
Does the iLang MCP server require authentication?
No. We connected to iLang without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the iLang MCP server still maintained?
iLang is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the iLang MCP server?
VerifyMCP ran 12 checks on iLang, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about iLang: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.