AILANG Parse
REMOTE · DOCPARSE.AILANG.SUNHOLO.COM · 3 COMPONENTS · SCANNED SEP 20
Deterministic DOCX/PPTX/XLSX/PDF parser: track changes, comments, headers, footers, merged cells.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- 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
- Context-footprint check failed: tool/resource definitions use about 1286 tokens (~116/item across 11 items; 10 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management31
- Stability check failed: schema churn in the 30 days we've observed: 22 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage76
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 28% 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 10 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
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the AILANG Parse MCP server?
AILANG Parse is a hosted endpoint at https://docparse.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 · docparse.ailang.sunholo.com
claude mcp add --transport http sunholo-data-parse 'https://docparse.ailang.sunholo.com/mcp/'
{
"mcpServers": {
"sunholo-data-parse": {
"url": "https://docparse.ailang.sunholo.com/mcp/"
}
}
} {
"servers": {
"sunholo-data-parse": {
"type": "http",
"url": "https://docparse.ailang.sunholo.com/mcp/"
}
}
} [mcp_servers.sunholo-data-parse] url = "https://docparse.ailang.sunholo.com/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sunholo-data-parse": {
"type": "remote",
"url": "https://docparse.ailang.sunholo.com/mcp/",
"enabled": true
}
}
} openclaw mcp add sunholo-data-parse --url 'https://docparse.ailang.sunholo.com/mcp/' --transport streamable-http
mcp_servers:
sunholo-data-parse:
url: "https://docparse.ailang.sunholo.com/mcp/" {
"McpServers": {
"sunholo-data-parse": {
"Transport": "http",
"Url": "https://docparse.ailang.sunholo.com/mcp/"
}
}
} assistant mcp add sunholo-data-parse -t streamable-http -u 'https://docparse.ailang.sunholo.com/mcp/'
{
"mcpServers": {
"sunholo-data-parse": {
"type": "http",
"url": "https://docparse.ailang.sunholo.com/mcp/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 11 Sept 26 −1
No change was recorded against any check on this day. Stability & Change Management went from 32 to 31.
- 1 Sept 26 0
- Tool “mcpFormats” rewrote its description, which is the text the model reads security
- 26 Aug 26 −8
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Aug 26 0
- Tool “mcpConvert” rewrote its description, which is the text the model reads security
- 12 Aug 26 0
- Schema quality: pass → fail ▼ functional
- New tool “convertDocument” functional
- 11 Aug 26 0
- Schema quality: fair → good functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 20 Sept 2026 · Probed https://docparse.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=docparse.ailang.sunholo.com | CN=YR2,O=Let's Encrypt,C=US | 26 Jul 2026 | 24 Oct 2026 | RSA 2048 | SHA256-RSA | 6385294ac375c852f2ba2346b9fed170605 |
| SANs: docparse.ailang.sunholo.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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 docparse.ailang.sunholo.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| sunholo.com. | absent | 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://docparse.ailang.sunholo.com/mcp/ | Verified | 200 | |
| http (plaintext) | http://docparse.ailang.sunholo.com/mcp/ | HTTPS enforced | 302 | https://docparse.ailang.sunholo.com/mcp/ |
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 →
editDocument ~192
Parse a document, apply JSON edit deltas, and return the modified blocks as JSON (same format as POST /api/v1/parse with outputFormat=blocks). filepath: uploaded file path (multipart upload). deltas: JSON array of edit operations — see edit_apply.ail for format. Empty array or "" → round-trip (parse + return unchanged blocks). apiKey: dp_ API key. Response: modified blocks JSON. Use the AILANG SDK or CLI to generate a file from the returned blocks (e.g. ailang run ... --convert output.docx). Only deterministic office formats are supported (docx, pptx, xlsx, odt, odp, ods). AI-required formats (pdf, image, audio, video) are rejected.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | yes | – |
| deltas | string | yes | – |
| filepath | string | yes | – |
No output schema declared.
No examples provided.
getUploadUrl ~95
Request a pre-authenticated GCS upload URL for direct file upload. Business tier only. The returned URL allows the client to PUT file content directly to GCS, bypassing the 32MB Cloud Run request limit. After upload, pass the gcs_ref to POST /api/v1/parse.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | yes | – |
| filename | string | yes | – |
| mimeType | string | yes | – |
No output schema declared.
No examples provided.
mcpAccount ~108
View account info, pricing, entitlements, or list keys. Actions: "status" (default) → tier, quota, usage from /me/entitlements "pricing" → public pricing tiers (no auth required) "keys" → list user's API keys with per-key usage "usage" → alias for "keys" (per-key usage is shown there)
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| apiKey | string | yes | – |
No output schema declared.
No examples provided.
mcpAuth ~82
Start device authorization to get an API key. Returns device_code, user_code, and verification URL. The agent should display the verification URL to the user, who signs in and approves the code. Then call mcpAuthPoll with the device_code. MCP wrappers don't have HTTP request headers, so provenance is empty here.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | yes | – |
No output schema declared.
No examples provided.
mcpAuthPoll ~58
Poll for device authorization completion. Returns "pending" (keep polling every 5s), "approved" (with api_key and tier), or "expired" (start over with mcpAuth).
| Name | Type | Req | Description |
|---|---|---|---|
| deviceCode | string | yes | – |
No output schema declared.
No examples provided.
mcpConvert ~157
Convert a document to another format. Targets: html, md, qmd, docx, pptx, xlsx, odt, odp, ods. `input` is a file path, a sample_id, an https:// URL, or a gs:// ref (Business tier). The converted file comes back as base64 in the JSON response rather than written to disk, so decode `content` to get the bytes. `outputPath` is accepted but ignored; it stays in the signature because removing it would change the auto-generated MCP tool schema for existing clients.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | yes | – |
| input | string | yes | – |
| outputFormat | string | yes | – |
| outputPath | string | yes | – |
No output schema declared.
No examples provided.
mcpEstimate ~46
Estimate cost and latency for parsing a document. Accepts a file path or sample_id. No auth required.
| Name | Type | Req | Description |
|---|---|---|---|
| filepath | string | yes | – |
| outputFormat | string | yes | – |
No output schema declared.
No examples provided.
mcpFormats ~99
Supported formats, samples, and service capabilities. No auth required. Delegates to package implementation. Single source of truth lives in pkg/sunholo/ailang_parse/services/mcp/tools — since ailang_parse 0.39.x the response carries a runtime capability block (state, not intent), which is why this is no longer pure: it reads env and probes the runtime (Process).
| Name | Type | Req | Description |
|---|---|---|---|
| _ | string | yes | – |
No output schema declared.
No examples provided.
mcpParse ~105
Parse a document. Accepts a file path or sample_id (e.g. "sample_docx_formatting"). The hosted server requires a valid dp_ API key — get one via mcpAuth. Output formats: blocks (default), markdown, html, a2ui. requestId is reserved for future replay support.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | yes | – |
| filepath | string | yes | – |
| outputFormat | string | yes | – |
| requestId | string | yes | – |
No output schema declared.
No examples provided.
submit_feedback ~325
Anonymous bug report / feature request / docs gap, queued for human review. Default routing: `public-feedback` inbox (general AILANG). Pass `package="vendor/name"` (e.g. "sunholo/auth") to route to that package's `pkg:vendor/name` inbox where its autonomous agent watches. Categories: bug, feature, docs, limitation. Body limit 10KB, snippet limit 4KB. Optional contact field for follow-up; opaque to the server. Set `auto_dispatch=true` to authorize the package agent to act on your submission immediately (default false — files for human triage; pkg-feedback agent template lands in a separate sprint).
| Name | Type | Req | Description |
|---|---|---|---|
| ailang_version | string | yes | The reporter's CLI version (free-form, used for triage) |
| auto_dispatch | boolean | – | Authorize the receiving package's autonomous agent to act on this submission. Default false (files for human triage). Tagged on the Pub/Sub notification as category=auto:<original> for coordinator fi… |
| body | string | yes | Full description (≤10 KB) |
| category | string | yes | bug | feature | docs | limitation |
| contact | string | – | Optional follow-up address (free-form, opaque to the server) |
| package | string | – | Optional vendor/name (e.g. "sunholo/auth") to route to that package's pkg:vendor/name inbox. Empty = general AILANG feedback. |
| snippet | string | – | Optional code/error snippet (≤4 KB) |
| title | string | yes | Short title for the report |
No output schema declared.
No examples provided.
What is the AILANG Parse MCP server?
AILANG Parse is an MCP server listed in the public MCP registry as io.github.sunholo-data/parse. Deterministic DOCX/PPTX/XLSX/PDF parser: track changes, comments, headers, footers, merged cells. This page covers its hosted endpoint (https://docparse.ailang.sunholo.com/mcp/).
Is the AILANG Parse MCP server safe to use?
AILANG Parse scores 67 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 Parse MCP server expose?
AILANG Parse exposes 10 tools: editDocument, getUploadUrl, mcpAccount, mcpAuth, mcpAuthPoll, and 5 more. Their descriptions and schemas cost roughly 1,267 tokens of context every time the server is loaded.
Does the AILANG Parse MCP server require authentication?
No. We connected to AILANG Parse without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AILANG Parse MCP server still maintained?
AILANG Parse is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.