# AILANG Parse (remote · docparse.ailang.sunholo.com)

Parse, convert and create Office and PDF documents. OAuth at /mcp/connect/, API key at /mcp/.

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `docparse.ailang.sunholo.com`: 81/100, [markdown](https://verifymcp.io/servers/sunholo-data-parse/docparse.md), [page](https://verifymcp.io/servers/sunholo-data-parse/docparse)
- remote · `docparse.ailang.sunholo.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/sunholo-data-parse/mcp-connect.md), [page](https://verifymcp.io/servers/sunholo-data-parse/mcp-connect)
- npm · `@ailang/parse`: 49/100, [markdown](https://verifymcp.io/servers/sunholo-data-parse/ailang-parse.md), [page](https://verifymcp.io/servers/sunholo-data-parse/ailang-parse)
- pypi · `ailang-parse`: 49/100, [markdown](https://verifymcp.io/servers/sunholo-data-parse/ailang-parse-2.md), [page](https://verifymcp.io/servers/sunholo-data-parse/ailang-parse-2)

## Channel facts

- Endpoint: `https://docparse.ailang.sunholo.com/mcp/connect/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.14.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2493 tokens (~207/item across 12 items; 10 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 73/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 18% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the AILANG Parse MCP server?

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

### Claude

```bash
claude mcp add --transport http sunholo-data-parse 'https://docparse.ailang.sunholo.com/mcp/connect/'
```

### Cursor

```json
{
  "mcpServers": {
    "sunholo-data-parse": {
      "url": "https://docparse.ailang.sunholo.com/mcp/connect/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "sunholo-data-parse": {
      "type": "http",
      "url": "https://docparse.ailang.sunholo.com/mcp/connect/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.sunholo-data-parse]
url = "https://docparse.ailang.sunholo.com/mcp/connect/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sunholo-data-parse": {
      "type": "remote",
      "url": "https://docparse.ailang.sunholo.com/mcp/connect/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add sunholo-data-parse --url 'https://docparse.ailang.sunholo.com/mcp/connect/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  sunholo-data-parse:
    url: "https://docparse.ailang.sunholo.com/mcp/connect/"
```

### Netclaw

```json
{
  "McpServers": {
    "sunholo-data-parse": {
      "Transport": "http",
      "Url": "https://docparse.ailang.sunholo.com/mcp/connect/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add sunholo-data-parse -t streamable-http -u 'https://docparse.ailang.sunholo.com/mcp/connect/'
```

### Other

```json
{
  "mcpServers": {
    "sunholo-data-parse": {
      "type": "http",
      "url": "https://docparse.ailang.sunholo.com/mcp/connect/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 69)

First indexed and scored.

## MCP tools (10)

### `createUpload` (~191 tokens)

Create upload link

Get one-time upload links for files in your sandbox or workspace, when you
can run shell commands with network access (Claude Code, Codex, a code
sandbox). One token PER FILE: a token uploads exactly one file. For several
files set count (1..20) to get that many descriptors in one call. Each
descriptor has a curl line: run it where the file is (replace <path>); it
prints a receipt with a fileRef. Then call mcpParse, mcpConvert or
editDocument with that fileRef. Tokens work once, for 10 minutes.
If curl fails with a network error, or the user wants to pick a file,
call uploadDocument instead, or ask for an https:// link. Never parse the
file yourself.

Input parameters:

- `count` (number)
- `filename` (string)
- `mimeType` (string)

### `editDocument` (~405 tokens)

Edit document

Edit a document: parse it, apply a JSON array of edit deltas, and return
the modified blocks (same shape as mcpParse with outputFormat "blocks").
deltas "" or "[]" returns the document unchanged. Office formats only:
docx, pptx, xlsx, odt, odp, ods. Give the document ONE way:
  fileRef: a file the user uploaded (mcp-file://docparse/file_...).
  file: in ChatGPT, the file the user attached (ChatGPT fills it in).
  content + filename: the file base64-encoded, contentEncoding="base64",
    e.g. filename "contract.docx".
  filepath: an https:// URL of a publicly reachable document, or a sample id
    from mcpFormats such as "sample_docx_formatting".
To get a file back, pass the edited blocks' Markdown to mcpConvert.
Which way to send a file:
  a file in your sandbox or workspace: call createUpload (one token PER
    FILE; set count for several) and run its curl line, then pass the
    fileRef here.
  curl fails with a network error, or the user wants to pick a file: call
    uploadDocument (the user chooses it in the AILANG Parse card). The card
    parses the file; it does not convert or edit it.
  a public https:// link; short text as content. In ChatGPT, file.
  Never parse the file yourself (your own script, or your own reading of
  it) and present that as this tool's result: if the file cannot be sent,
  tell the user.

Input parameters:

- `content` (string)
- `contentEncoding` (string)
- `deltas` (string)
- `file` (object)
- `fileRef` (string)
- `filename` (string)
- `filepath` (string)

### `mcpAccount` (~125 tokens)

Account, quota and usage

Your AILANG Parse account: plan, monthly usage and limits, your keys, and
whether request history is kept.
Actions:
  "status"  (default) → plan, usage this month and remaining allowance
  "keys"              → your keys with per-key usage ("usage" is an alias)
  "history"           → whether request history (parsed output kept for
                        replay) is on for your account
  "history_on" / "history_off" → change it for the account and all its keys

Input parameters:

- `action` (string)

### `mcpConvert` (~452 tokens)

Convert document

Create a document in another format: docx, pptx, xlsx, odt, odp, ods, html,
md or qmd. To write a new document, write Markdown and send it as content
with filename "notes.md" (headings become slides in pptx). To convert an
existing document, give it ONE way:
  fileRef: a file the user uploaded (mcp-file://docparse/file_...).
  file: in ChatGPT, the file the user attached (ChatGPT fills it in).
  content + filename: the document itself; binary files base64-encoded with
    contentEncoding="base64", text as plain text.
  input: an https:// URL of a publicly reachable document, or a sample id
    from mcpFormats.
Which way to send a file:
  a file in your sandbox or workspace: call createUpload (one token PER
    FILE; set count for several) and run its curl line, then pass the
    fileRef here.
  curl fails with a network error, or the user wants to pick a file: call
    uploadDocument (the user chooses it in the AILANG Parse card). The card
    parses the file; it does not convert or edit it.
  a public https:// link; short text as content. In ChatGPT, file.
  Never parse the file yourself (your own script, or your own reading of
  it) and present that as this tool's result: if the file cannot be sent,
  tell the user.
The result carries download_url, a link to the generated file valid for one
hour: give it to the user. It also carries the file as base64 in content
(encoding "base64"; text formats come back as utf8). Leave outputPath
empty: the server cannot write to your filesystem.

Input parameters:

- `content` (string)
- `contentEncoding` (string)
- `file` (object)
- `fileRef` (string)
- `filename` (string)
- `input` (string)
- `outputFormat` (string, required)
- `outputPath` (string)

### `mcpEstimate` (~46 tokens)

Estimate cost and latency

Estimate cost and latency for parsing a document.
Accepts a file path or sample_id. No auth required.

Input parameters:

- `filepath` (string, required)
- `outputFormat` (string, required)

### `mcpFormats` (~42 tokens)

List formats and capabilities

What AILANG Parse can read and write, how to send it a document, and the
sample documents you can try without one. No sign-in needed.

### `mcpParse` (~594 tokens)

Parse document

Parse a document into structured blocks, Markdown, HTML or A2UI, or a short
summary of it.
Give the document ONE way:
  fileRef: an uploaded file (mcp-file://docparse/file_...). The same user can
    use it again for 30 minutes after the first use (more parts, another
    format), then it is deleted.
  file: in ChatGPT, the file the user attached (ChatGPT fills it in).
  filepath: an https:// URL of a publicly reachable document, or a sample id
    from mcpFormats such as "sample_docx_formatting".
  content + filename: short text only (Markdown, HTML, CSV); the
    filename's extension picks the parser.
outputFormat: blocks (default), markdown, html, a2ui, or summary (counts,
  the first 50 headings, warnings: a few KB). Look with summary first when
  a document may be large.
Large documents come in parts: when the result has page.nextCursor, call
  mcpParse again with the same fileRef/filepath and cursor=<nextCursor> for
  the next part; read every part before answering about the whole document.
  maxChars sets the part size as a string of digits (default "80000",
  "2000".."120000").
pdfBackend: leave empty for PDFs with a text layer. Set "ai" when the result
  is PDF_TEXT_LAYER_SPARSE (a scanned PDF): each page is read by an AI model,
  about 5 seconds a page, and the call counts as an AI request. Pass the same
  pdfBackend with every cursor call.
Which way to send a file:
  a file in your sandbox or workspace: call createUpload (one token PER
    FILE; set count for several) and run its curl line, then call this
    tool with the fileRef the upload prints.
  curl fails with a network error, or the user wants to pick a file: call
    uploadDocument; the user chooses it in the AILANG Parse card, which
    uploads it and gives you its fileRef.
  a public https:// link: filepath. Short text: content.
  Never parse the file yourself (your own script, or your own reading of
  it) and present that as this tool's result: if the file cannot be sent,
  tell the user.

Input parameters:

- `content` (string)
- `contentEncoding` (string)
- `cursor` (string)
- `file` (object)
- `fileRef` (string)
- `filename` (string)
- `filepath` (string)
- `maxChars` (string)
- `outputFormat` (string)
- `pdfBackend` (string)
- `requestId` (string)

### `submit_feedback` (~325 tokens)

Send feedback

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).

Input parameters:

- `ailang_version` (string, required): 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, required): Full description (≤10 KB)
- `category` (string, required): 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, required): Short title for the report

### `uploadDocument` (~143 tokens)

Upload a document

Let the user pick a file to parse: shows the AILANG Parse card with a
Choose file button. The card uploads the file and tries to summarise it
for you; either way you get its fileRef. Then call mcpParse with that
fileRef for the content (the same user can reuse it for 30 minutes; a large
document comes in parts). Use this when the user wants to pick a file, or
when createUpload's curl fails with a network error. For a file already in
your sandbox or workspace, use createUpload + curl instead.
Never parse the file yourself.

Input parameters:

- `outputFormat` (string)

### `uploadViaHost` (~67 tokens)

Receive upload from widget

Receive a file from the AILANG Parse upload widget, relayed by the host as
base64. Only the widget calls this; ticket is the upload token it holds.

Input parameters:

- `base64` (string, required)
- `filename` (string, required)
- `ticket` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/sunholo-data-parse/mcp-connect#diagnostics

## Score history

- 2026-11-05: 69

## Common questions

### 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. Parse, convert and create Office and PDF documents. OAuth at /mcp/connect/, API key at /mcp/. This page covers its hosted endpoint (https://docparse.ailang.sunholo.com/mcp/connect/).

### Is the AILANG Parse MCP server safe to use?

AILANG Parse scores 69 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: createUpload, editDocument, mcpAccount, mcpConvert, mcpEstimate, and 5 more. Their descriptions and schemas cost roughly 2,390 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://docparse.ailang.sunholo.com/mcp/connect/
- Repository: https://github.com/sunholo-data/ailang-parse
- Website: https://www.sunholo.com/ailang-parse/
- Changelog RSS feed: https://verifymcp.io/servers/sunholo-data-parse/mcp-connect.xml
- Changelog JSON feed: https://verifymcp.io/servers/sunholo-data-parse/mcp-connect.json
- HTML version of this page: https://verifymcp.io/servers/sunholo-data-parse/mcp-connect