MinerU MCP
OCI · GHCR.IO/GERMANIU/MINERU-MCP
Parse PDF, DOCX, PPTX, XLSX and images to Markdown (tables, LaTeX) via a self-hosted MinerU API.
Available components
Last scanned (9 hours ago)
Scores higher than 64% 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 & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 16 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 501 tokens (~100/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.
Checks we ran (12)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (4)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)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.
- Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 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.
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/germaniu/mineru-mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
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 →
get_task_result Get Task Result ~45
Obtiene el Markdown de una tarea asíncrona COMPLETADA (llamar después de que get_task_status devuelva 'completed').
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_task_status Get Task Status ~39
Consulta el estado de una tarea asíncrona de MinerU (pending/processing/completed/failed).
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
mineru_health Mineru Health ~26
Verifica que MinerU esté disponible: versión, tareas en cola, workers activos.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
parse_document Parse Document ~240
Parsea un documento (PDF, DOCX, PPTX, XLSX, imagen) con MinerU y devuelve su contenido como Markdown estructurado (texto, tablas, fórmulas, títulos). Enviar el archivo con file_path (si ya vive en Pop!_OS) o file_base64+file_name (contenido, para callers remotos). backend=pipeline es rápido y sin GPU; hybrid-engine/vlm-engine usan ~4GB VRAM (GPU Broker para llama-server automáticamente, lo re-arranca al terminar) y dan mejor calidad — hybrid-engine + effort=high + image_analysis=true convierte figuras a diagramas Mermaid. Tiempo: 30-120s. Docs >50 páginas: preferir submit_parse_task.
| Name | Type | Req | Description |
|---|---|---|---|
| backend | string | – | – |
| effort | string | – | – |
| end_page | – | – | – |
| file_base64 | – | – | – |
| file_name | – | – | – |
| file_path | – | – | – |
| formula_enable | boolean | – | – |
| image_analysis | boolean | – | – |
| lang | string | – | – |
| parse_method | string | – | – |
| start_page | – | – | – |
| table_enable | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
submit_parse_task Submit Parse Task ~151
Envía un documento a MinerU para parseo ASÍNCRONO y devuelve un task_id. Usar para documentos grandes (>50 páginas). Mismos params de entrada que parse_document (file_path o file_base64+file_name). Luego get_task_status y get_task_result.
| Name | Type | Req | Description |
|---|---|---|---|
| backend | string | – | – |
| effort | string | – | – |
| end_page | – | – | – |
| file_base64 | – | – | – |
| file_name | – | – | – |
| file_path | – | – | – |
| formula_enable | boolean | – | – |
| image_analysis | boolean | – | – |
| lang | string | – | – |
| parse_method | string | – | – |
| start_page | – | – | – |
| table_enable | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the MinerU MCP server?
MinerU MCP runs locally as a container image, launched with docker run --rm -i -e MINERU_URL -e MINERU_BACKEND -e MINERU_PARSE_METHOD -e MINERU_LANG ghcr.io/germaniu/mineru-mcp:0.1.0 --stdio. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. 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/germaniu/mineru-mcp
claude mcp add germaniu-mineru-mcp -- docker run --rm -i -e MINERU_URL -e MINERU_BACKEND -e MINERU_PARSE_METHOD -e MINERU_LANG ghcr.io/germaniu/mineru-mcp:0.1.0 --stdio
This image reads MINERU_URL, MINERU_BACKEND, MINERU_PARSE_METHOD and MINERU_LANG. Set them in your client's env block for this server; docker run -e passes each one through to the container. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it.
What is the MinerU MCP server?
MinerU MCP is listed in the public MCP registry as io.github.GermaniU/mineru-mcp. Parse PDF, DOCX, PPTX, XLSX and images to Markdown (tables, LaTeX) via a self-hosted MinerU API. This page covers its container image (ghcr.io/germaniu/mineru-mcp).
Is the MinerU MCP server safe to use?
MinerU MCP scores 45 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 MinerU MCP server expose?
MinerU MCP exposes 5 tools: parse_document, submit_parse_task, get_task_status, get_task_result, mineru_health. Their descriptions and schemas cost roughly 501 tokens of context every time the server is loaded.
Is the MinerU MCP server still maintained?
MinerU MCP 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 MinerU MCP server under?
MinerU MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the MinerU MCP server?
VerifyMCP ran 12 checks on MinerU MCP, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about MinerU MCP: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.