Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AILANG Docs

REMOTE · MCP.AILANG.SUNHOLO.COM

AILANG language reference, stdlib, examples and benchmarks for agents that write AILANG.

+2 this week 72 Trust /100

Last scanned (19 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Developer Tools

Trust breakdown (7 categories)

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 Security74
  • 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 is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability76
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 1404 tokens (~61/item across 23 items; 22 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability check failed: schema churn in the 9 days we've observed: 1 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage73
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 20% 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
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

Changelog

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.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17.

  • 18 Nov 26 0
    • Server version: 0.60.5 → 0.60.6 functional
  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10.

  • 16 Nov 26 0
    • Stability: 0.10 → fail ▼ security
    • Tool “benchmark_run” was removed ▼ security
    • Tool “benchmarks_compare” rewrote its description, which is the text the model reads security
    • Tool “design_doc” rewrote its description, which is the text the model reads security
    • Tool “example_get” rewrote its description, which is the text the model reads security
    • Tool “examples_list” rewrote its description, which is the text the model reads security
    • Tool “prompt_get” rewrote its description, which is the text the model reads security
    • Tool “roadmap” rewrote its description, which is the text the model reads security
    • Schema quality: 55 → 61 ▼ functional
    • “benchmarks_compare” dropped the required parameter “version” ▼ functional
    • Server version: 0.60.4 → 0.60.5 functional
  • 14 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.

  • 13 Nov 26 0
    • Tool “docs_nav” rewrote its description, which is the text the model reads security
    • Tool “docs_search” rewrote its description, which is the text the model reads security
    • Tool “onboarding_guide” rewrote its description, which is the text the model reads security
    • Tool “submit_feedback” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
    • Destructive annotations: pass → 100 functional
    • Server version: 0.60.2 → 0.60.4 functional
    • “submit_feedback” reworded the description of “auto_dispatch” cosmetic
    • “submit_feedback” reworded the description of “contact” cosmetic
    • “submit_feedback” reworded the description of “package” cosmetic
  • 12 Nov 26 69

    First indexed and scored.

Diagnostics

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.ailang.sunholo.com/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.ailang.sunholo.com CN=YR1,O=Let's Encrypt,C=US 20 Oct 2026 18 Jan 2027 RSA 2048 SHA256-RSA 67547b81c2f710a3efd712b4545fed40812
SANs: mcp.ailang.sunholo.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.ailang.sunholo.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
sunholo.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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.ailang.sunholo.com/mcp/ Verified 200
http (plaintext) http://mcp.ailang.sunholo.com/mcp/ HTTPS enforced 302 https://mcp.ailang.sunholo.com/mcp/
MCP tools · 22 exposed · ~1,385 tokens

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 →

Tool Tokens
ailang_versions ~21

List all AILANG versions the server can answer for.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

benchmarks_compare ~57

Two models side by side across every banked run: passes, runs, pass rate, cost and failures by category. Model names are as benchmarks_list gives them.

NameTypeReqDescription
modelAstringyes–
modelBstringyes–

No output schema declared.

No examples provided.

benchmarks_for_model ~52

Where does a given model pass/fail? Optional version filter. Output: {passes: [...], fails_by_category: {...}, total_cost}

NameTypeReqDescription
modelstringyes–
versionstringyes–

No output schema declared.

No examples provided.

benchmarks_list ~30

List benchmark suites and runs, optionally filtered to a since_version cutoff.

NameTypeReqDescription
sinceVersionstringyes–

No output schema declared.

No examples provided.

changelog_for_version ~33

What changed in a given release (added/changed/fixed/breaking).

NameTypeReqDescription
versionstringyes–

No output schema declared.

No examples provided.

design_doc ~56

Full design doc by slug (e.g. "m-agent-mcp-website"), as markdown. Long documents are cut at 30,000 characters and say so; url opens the whole one.

NameTypeReqDescription
slugstringyes–

No output schema declared.

No examples provided.

design_docs_list ~57

List planned/implemented/rejected design docs, optionally filtered by version. state = "planned" | "implemented" | "rejected" | ""; empty = all.

NameTypeReqDescription
statestringyes–
versionstringyes–

No output schema declared.

No examples provided.

docs_nav ~40

The AILANG docs site's navigation tree for a version, as JSON: section and page titles with their paths.

NameTypeReqDescription
forVersionstringyes–

No output schema declared.

No examples provided.

docs_search ~81

Full-text search of the AILANG documentation for a version (case-insensitive, on page titles and text). Returns the top 10 matches, docs pages before archived teaching prompts, each with its path, title, first 10 headings and an excerpt around the match.

NameTypeReqDescription
forVersionstringyes–
querystringyes–

No output schema declared.

No examples provided.

effects_catalog ~29

All declared effects with capability mapping and the version they appeared in.

NameTypeReqDescription
forVersionstringyes–

No output schema declared.

No examples provided.

example_for_concept ~57

Best-fit examples for a free-form concept query ("how do I use effects?"). Filters server-side on why + title; returns up to 5 matches.

NameTypeReqDescription
conceptstringyes–
forVersionstringyes–

No output schema declared.

No examples provided.

example_get ~60

Full source of one example by path (as examples_list gives it, e.g. "runnable/hello.ail"; a leading "examples/" is accepted), at the release.

NameTypeReqDescription
forVersionstringyes–
pathstringyes–

No output schema declared.

No examples provided.

examples_list ~110

Examples in the release's manifest (examples/manifest.json at its tag). features = comma-separated tags ("effects,records"); empty = no filter. status = "working" | "broken" | "aspirational" | "" ("passing" = working, "failing" = the other two); empty = working only. At most 50 are returned; total says how many matched.

NameTypeReqDescription
featuresstringyes–
forVersionstringyes–
statusstringyes–

No output schema declared.

No examples provided.

install_guide ~105

Harness-aware install instructions for AILANG. harness: "claude-code" | "gemini-cli" | "codex-cli" | "manual" | "build-from-source" | "" platform: only meaningful for "manual" (e.g. "darwin-arm64", "linux-amd64"); ignored otherwise Empty harness returns ALL harnesses + the remote_mcp config block.

NameTypeReqDescription
harnessstringyes–
platformstringyes–

No output schema declared.

No examples provided.

limitations_list ~38

Known limitations (Y-combinator, etc.) optionally filtered by category.

NameTypeReqDescription
categorystringyes–
forVersionstringyes–

No output schema declared.

No examples provided.

onboarding_guide ~72

Step-by-step guide to getting started with AILANG, for an AI coding agent and for a human developer. role: "agent" | "developer" | "" (both). The guide for both roles is returned whatever role says; pick the part you need.

NameTypeReqDescription
rolestringyes–

No output schema declared.

No examples provided.

prompt_get ~49

Fetch the canonical teaching prompt for a version. kind = "" (the full prompt) | "agent" | "devtools".

NameTypeReqDescription
forVersionstringyes–
kindstringyes–

No output schema declared.

No examples provided.

roadmap ~37

What's shipping next, what's been rejected and why: the roadmap page of the AILANG site, generated from the planned design docs, as markdown.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

stdlib_module ~34

Full module: exports + signatures + docstrings.

NameTypeReqDescription
forVersionstringyes–
namestringyes–

No output schema declared.

No examples provided.

stdlib_modules ~33

List stdlib modules available in this AILANG version with one-line summaries.

NameTypeReqDescription
forVersionstringyes–

No output schema declared.

No examples provided.

stdlib_search ~51

Find stdlib functions by name, signature, or keyword. Filters the pre-built search index server-side; returns top 20 matches.

NameTypeReqDescription
forVersionstringyes–
querystringyes–

No output schema declared.

No examples provided.

submit_feedback ~283

Send a bug report, feature request, documentation gap or limitation about AILANG to the AILANG team. Use it only when the user asks to report something, and leave out personal or confidential information. Categories: bug, feature, docs, limitation. Body up to 10 KB, snippet up to 4 KB. `contact` is optional, for a reply. `package` (vendor/name) sends the report to that AILANG package's maintainers instead. Returns a ticket ID.

NameTypeReqDescription
ailang_versionstringyesThe reporter's CLI version (free-form, used for triage)
auto_dispatchboolean–Let the package maintainers' automation act on the report before a person reads it. Only if the user asks. Default false: a person triages it first.
bodystringyesFull description (≤10 KB)
categorystringyesbug | feature | docs | limitation
contactstring–Optional address for a reply. Only if the user gives one
packagestring–Optional vendor/name (e.g. "sunholo/auth") to send the report to that package's maintainers. Empty = the AILANG team.
snippetstring–Optional code/error snippet (≤4 KB)
titlestringyesShort title for the report

No output schema declared.

No examples provided.

Install

How do I install the AILANG Docs MCP server?

AILANG Docs is a hosted endpoint at https://mcp.ailang.sunholo.com/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.ailang.sunholo.com

# add to Claude Code
claude mcp add --transport http sunholo-data-ailang-docs 'https://mcp.ailang.sunholo.com/mcp/'
Common questions

What is the AILANG Docs MCP server?

AILANG Docs is an MCP server listed in the public MCP registry as io.github.sunholo-data/ailang-docs. AILANG language reference, stdlib, examples and benchmarks for agents that write AILANG. This page covers its hosted endpoint (https://mcp.ailang.sunholo.com/mcp/).

Is the AILANG Docs MCP server safe to use?

AILANG Docs scores 72 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 AILANG Docs MCP server expose?

AILANG Docs exposes 22 tools: ailang_versions, benchmarks_compare, benchmarks_for_model, benchmarks_list, changelog_for_version, and 17 more. Their descriptions and schemas cost roughly 1,385 tokens of context every time the server is loaded.

Does the AILANG Docs MCP server require authentication?

No. We connected to AILANG Docs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AILANG Docs MCP server still maintained?

AILANG Docs 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 AILANG Docs MCP server?

VerifyMCP ran 13 checks on AILANG Docs, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.