docling.rs MCP
Score = points from 5 automated checks. Not a quality or security rating. Methodology
- Install20/20
- Handshake30/30
- Maintenance25/25
- Docs15/15
- License10/10
Tested PyPI docling-rs-mcp 2.62.0 (docling.rs, the Rust port in the docling-project org; repo docling-project/docling.rs). Its 3 tools listed without credentials. Real tool calls (no LLM, no credentials): list_input_formats, convert_to_markdown on a small local HTML file and convert (to DoclingDocument JSON) on a local Markdown file all worked. URL fetching is off by default and was not tested; PDFs, images and OCR were not tested. An X post (MCPScores, Oct 21) flagged CVE-2026-112403 for this server: NVD lists it as a Pillow < 13.0.0 bug, and our install resolved Pillow 13.0.0 (fixed).
Tool-call test (2026-11-02, direct MCP stdio client, no LLM): pass. 3 of 3 calls passed: list_input_formats, convert_to_markdown (HTML) and convert to DoclingDocument JSON (Markdown). No credentials; PDF/OCR and URL input not tested. Evidence: local test run, Nov 2, 2026.
Transport (tested 2026-11-02): stdio
Score 100/100 · Tools 3 · Token cost ~901 · Compare · Last tested 2026-11-02 · Version tested 2.62.0 · Package docling-rs-mcp · Repo docling-project/docling.rs
Summary: docling.rs MCP completed an MCP handshake without credentials and exposed 3 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 3
- Context cost
- 901 model-visible tokens (name, description, inputSchema; tiktoken cl100k_base)
Extra payload (sent by the server, usually not read by the model): 55 tokens; raw tools/list total 956. Clients differ in what they forward. ranking · add up your servers' context cost - API key
- No key needed for the tools we called
- Tested
- 2026-11-02
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | uv pip install docling-rs-mcp (Python venv, Linux) succeeded in 2s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 3 tools listed in 2.0s. |
| maintenance | pass | 25 | Repo pushed 0 days before test; 121 GitHub stars. |
| docs | pass | 15 | README over 3,000 chars; install instructions present; mcpServers config example present. Automated check of the package's own README (PyPI long_description (package README)). |
| license | pass | 10 | MIT (OSI-approved). |
Local-model readiness
Schema context cost: ~901 tokens for 3 tools (3,554 bytes) · about 11% of an 8k context. Method: tiktoken cl100k_base over compact JSON of name+description+inputSchema (approximate).
Small-model friendly (schema heuristic, not a model result): unknown.
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-11-02
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 3 tools (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Tool-schema token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that it is safe to give it access to your data.
Known security issues
Not yet checked.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-11-02 test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
c13a0e70fc99: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "docling-rs-mcp",
"version": "2.62.0",
"registry": "pypi",
"status": "working",
"tested": "2026-11-02",
"tools_count": 3,
"tools_schema_tokens_est": 901,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"`uv pip install docling-rs-mcp` (Python venv, Linux) succeeded in 2s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 3 tools listed in 2.0s."
],
"maintenance": [
"pass",
25,
"Repo pushed 0 days before test; 121 GitHub stars."
],
"docs": [
"pass",
15,
"README over 3,000 chars; install instructions present; `mcpServers` config example present. Automated check of the package's own README (PyPI long_description (package README))."
],
"license": [
"pass",
10,
"MIT (OSI-approved)."
]
}
}Install
uvx docling-rs-mcp
Tools listed
convert, convert_to_markdown, list_input_formats
Quick config
{
"mcpServers": {
"docling-rs-mcp": {
"command": "uvx",
"args": [
"docling-rs-mcp"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
uv pip install docling-rs-mcp(Python venv). This is the exact command we ran on 2026-11-02. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (3 in our test).
{
"mcpServers": {
"docling-rs-mcp": {
"command": "uvx",
"args": [
"docling-rs-mcp"
]
}
}
}Test history
No dated events yet.
FAQ
Is docling.rs MCP deprecated?
No. docling-rs-mcp was not deprecated or archived when we last tested it on 2026-11-02.
What replaces docling.rs MCP?
Nothing; docling.rs MCP is not deprecated as of 2026-11-02.
Does docling.rs MCP need an API key?
No. It completed an MCP handshake with no credentials and listed 3 tools.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.