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

- Trust score: 45/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- oci · `ghcr.io/germaniu/mineru-mcp`: 45/100 (this document), [markdown](https://verifymcp.io/servers/germaniu-mineru-mcp/ghcr-io-germaniu-mineru-mcp.md), [page](https://verifymcp.io/servers/germaniu-mineru-mcp/ghcr-io-germaniu-mineru-mcp)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/germaniu/mineru-mcp`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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

- **Supply Chain Security**: 0/100
  - 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 could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 16 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 501 tokens (~100/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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).

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

## Install

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

### Claude

```bash
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.

### Cursor

```json
{
  "mcpServers": {
    "germaniu-mineru-mcp": {
      "command": "docker",
      "args": [
        "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.

### VS Code

```json
{
  "servers": {
    "germaniu-mineru-mcp": {
      "command": "docker",
      "args": [
        "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.

### Codex

```bash
codex 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.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "germaniu-mineru-mcp": {
      "type": "local",
      "command": [
        "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"
      ],
      "enabled": true
    }
  }
}
```

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.

### Hermes

```yaml
mcp_servers:
  germaniu-mineru-mcp:
    command: "docker"
    args: ["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.

### Netclaw

```json
{
  "McpServers": {
    "germaniu-mineru-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "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.

### Other

```json
{
  "mcpServers": {
    "germaniu-mineru-mcp": {
      "command": "docker",
      "args": [
        "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.

## 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 45, +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.

### 2026-11-02 (score 44, +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.

### 2026-10-31 (score 43, +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.

### 2026-10-29 (score 42, +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.

### 2026-10-27 (score 41, +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.

### 2026-10-25 (score 40, +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.

### 2026-10-23 (score 39, +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.

### 2026-10-21 (score 38, +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.

## MCP tools (5)

### `parse_document` (~240 tokens)

Parse Document

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.

Input parameters:

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

Output parameters:

- `result` (string)

### `submit_parse_task` (~151 tokens)

Submit Parse Task

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.

Input parameters:

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

Output parameters:

- `result` (string)

### `get_task_status` (~39 tokens)

Get Task Status

Consulta el estado de una tarea asíncrona de MinerU (pending/processing/completed/failed).

Input parameters:

- `task_id` (string, required)

Output parameters:

- `result` (string)

### `get_task_result` (~45 tokens)

Get Task Result

Obtiene el Markdown de una tarea asíncrona COMPLETADA (llamar después de que get_task_status devuelva 'completed').

Input parameters:

- `task_id` (string, required)

Output parameters:

- `result` (string)

### `mineru_health` (~26 tokens)

Mineru Health

Verifica que MinerU esté disponible: versión, tareas en cola, workers activos.

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/germaniu-mineru-mcp/ghcr-io-germaniu-mineru-mcp#diagnostics

## Score history

- 2026-11-05: 45
- 2026-11-04: 44
- 2026-11-03: 44
- 2026-11-02: 44
- 2026-11-01: 43
- 2026-10-31: 43
- 2026-10-30: 42
- 2026-10-29: 42
- 2026-10-28: 41
- 2026-10-27: 41
- 2026-10-26: 40
- 2026-10-25: 40
- 2026-10-24: 39
- 2026-10-23: 39
- 2026-10-22: 38
- 2026-10-21: 38
- 2026-10-20: 37
- 2026-10-19: 37

## Common questions

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

## Links

- GitHub Container Registry: https://ghcr.io/germaniu/mineru-mcp
- Repository: https://github.com/GermaniU/mineru-mcp
- Changelog RSS feed: https://verifymcp.io/servers/germaniu-mineru-mcp/ghcr-io-germaniu-mineru-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/germaniu-mineru-mcp/ghcr-io-germaniu-mineru-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/germaniu-mineru-mcp/ghcr-io-germaniu-mineru-mcp.json
- HTML version of this page: https://verifymcp.io/servers/germaniu-mineru-mcp/ghcr-io-germaniu-mineru-mcp