docling.rs
OCI · GHCR.IO/DOCLING-PROJECT/DOCLING-RS · 2 COMPONENTS
Documents to Markdown for agents: PDF layout, tables and OCR, Office, HTML, scans. docling in Rust.
Available components
Last scanned (5 hours ago)
Scores higher than 98% of OCI servers
Category Documents and Files
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to docling-project/docling.rs). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 868 tokens (~289/item across 3 items; 3 tools + 0 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 Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
- Package version: 2.62.0 → 2.65.1 functional
- 1 Nov 26 +1
- Stability: 0.53 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 2.55.4 → 2.62.0 functional
- 30 Oct 26 +1
- Package version: 2.53.3 → 2.55.4 functional
- Package version: 2.24.0 → 2.55.4 functional
- 28 Oct 26 +1
- Stability: 0.40 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 2.52.9 → 2.53.3 functional
- Package version: 2.52.9 → 2.53.1 functional
- 27 Oct 26 0
- Package version: 2.52.7 → 2.52.9 functional
- 26 Oct 26 +1
- Package version: 2.51.3 → 2.52.7 functional
- Package version: 2.51.3 → 2.52.6 functional
- 24 Oct 26 0
- Package version: 2.51.0 → 2.51.3 functional
- Package version: 2.51.0 → 2.51.1 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 5 Nov 2026 · Analysed oci/ghcr.io/docling-project/docling-rs@2.65.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | oci |
| Reason | Verified |
| Discovered via | OCI referrers API |
| Source repo | docling-project/docling.rs |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/docling-project/docling.rs/.github/workflows/docker-publish.yml@refs/heads/master |
| Rekor log index | 3664348415 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha256:141eb8984822e0970626f7c8e25d02dd66220e2628650bf214b8547b892bf392 |
Background: How many MCP packages publish verified provenance →
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 →
convert ~463
Convert a document to a chosen output format, with conversion options, and return the result as text. `to` picks the format (Markdown, docling JSON with structure and page provenance, HTML, plain text, LaTeX, RAG chunks, WebVTT, Pandoc JSON); `images` embeds pictures instead of placeholders; `options` sets page ranges, OCR language and mode, text-layer-only PDFs, passwords and the rest. For plain Markdown with default settings, `convert_to_markdown` is the simpler call. Inputs and errors as for `convert_to_markdown`; an unknown `to`, `images` value or option key is an error that says what is accepted. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| images | string | – | Pictures in md, html or pandoc output: placeholder (the default, an `<!-- image -->` marker) or embedded (the image as a data: URI). |
| options | object | – | Conversion options, docling.rs's shared set (docs/OPTIONS.md), e.g. {"pages": "1-5"}, {"text_layer_only": true} (digital PDFs, fastest; "auto" = the text layer when it has text, OCR when it has none)… |
| to | string | – | Output format: md (Markdown, the default), json (docling's DoclingDocument: structure, tables and page provenance), html, text, latex, chunks (RAG-ready chunk records as JSON), vtt (WebVTT, for audio… |
| uri | string | yes | The document to read: an http: or https: URL (only when the server allows URL fetching — see list_input_formats), a file: URI, a data: URI, or a file path. Relative paths resolve against the server's… |
No output schema declared.
No examples provided.
convert_to_markdown ~227
Read a document as Markdown, with default settings, and return the Markdown text. Handles PDF (layout analysis, tables, OCR for scans), Word, PowerPoint, Excel, HTML, EPUB, e-mail, images, audio and more. Use this whenever Markdown is all you need. Use `convert` instead for another output format (docling JSON, HTML, RAG chunks, …), embedded images, or options such as a page range, OCR language or password. Fails with a message when the document is missing, outside the server's root, of an unsupported type (see `list_input_formats`), or a URL while URL fetching is off. Read-only. Same name and contract as MarkItDown's MCP tool.
| Name | Type | Req | Description |
|---|---|---|---|
| uri | string | yes | The document to read: an http: or https: URL (only when the server allows URL fetching — see list_input_formats), a file: URI, a data: URI, or a file path. Relative paths resolve against the server's… |
No output schema declared.
No examples provided.
list_input_formats ~75
List the file extensions this server can convert, one per line, and whether it accepts http(s) URLs. Takes no arguments and converts nothing. Call it before `convert_to_markdown` or `convert` when unsure whether a file type is supported, or to learn why a URL was refused.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the docling.rs MCP server?
docling.rs runs locally as a container image, launched with docker run --rm -i ghcr.io/docling-project/docling-rs:2.65.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/docling-project/docling-rs
claude mcp add docling-project-docling-rs -- docker run --rm -i ghcr.io/docling-project/docling-rs:2.65.1
What is the docling.rs MCP server?
docling.rs is an MCP server listed in the public MCP registry as io.github.docling-project/docling-rs. Documents to Markdown for agents: PDF layout, tables and OCR, Office, HTML, scans. docling in Rust. This page covers its container image (ghcr.io/docling-project/docling-rs).
Is the docling.rs MCP server safe to use?
docling.rs scores 60 out of 100 on VerifyMCP. Its build provenance is signed and verified. 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 docling.rs MCP server expose?
docling.rs exposes 3 tools: convert, convert_to_markdown, list_input_formats. Their descriptions and schemas cost roughly 765 tokens of context every time the server is loaded.
Is the docling.rs MCP server still maintained?
docling.rs 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.
What licence is the docling.rs MCP server under?
docling.rs declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.