io.github.groupdocs-parser/groupdocs-parser-mcp
OCI · GHCR.IO/GROUPDOCS-PARSER/PARSER-NET-MCP:26.9.0 · SCANNED SEP 20
MCP server for GroupDocs.Parser — extract text, images, metadata, tables, barcodes via AI.
Available components
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
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.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 14 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 1417 tokens (~202/item across 7 items; 7 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 Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 65% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
How do I install the io.github.groupdocs-parser/groupdocs-parser-mcp server?
io.github.groupdocs-parser/groupdocs-parser-mcp runs locally as a container image, launched with docker run --rm -i ghcr.io/groupdocs-parser/parser-net-mcp:26.9.0. 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/groupdocs-parser/parser-net-mcp:26.9.0
claude mcp add groupdocs-parser-groupdocs-parser-mcp -- docker run --rm -i ghcr.io/groupdocs-parser/parser-net-mcp:26.9.0
{
"mcpServers": {
"groupdocs-parser-groupdocs-parser-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/groupdocs-parser/parser-net-mcp:26.9.0"
]
}
}
} {
"servers": {
"groupdocs-parser-groupdocs-parser-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/groupdocs-parser/parser-net-mcp:26.9.0"
]
}
}
} codex mcp add groupdocs-parser-groupdocs-parser-mcp -- docker run --rm -i ghcr.io/groupdocs-parser/parser-net-mcp:26.9.0
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"groupdocs-parser-groupdocs-parser-mcp": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/groupdocs-parser/parser-net-mcp:26.9.0"
],
"enabled": true
}
}
} mcp_servers:
groupdocs-parser-groupdocs-parser-mcp:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/groupdocs-parser/parser-net-mcp:26.9.0"] {
"McpServers": {
"groupdocs-parser-groupdocs-parser-mcp": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/groupdocs-parser/parser-net-mcp:26.9.0"
]
}
}
} {
"mcpServers": {
"groupdocs-parser-groupdocs-parser-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/groupdocs-parser/parser-net-mcp:26.9.0"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +3
- Stability: unverified → 0.23 ▲ functional
- 6 Sept 26 39
First indexed and scored.
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 20 Sept 2026 · Analysed oci/ghcr.io/groupdocs-parser/parser-net-mcp:26.9.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 →
extract_barcodes ~252
Extracts all barcodes and QR codes from a document and returns their decoded values and type names as JSON. Detects Code128, QR Code, PDF417, DataMatrix, EAN-13, EAN-8, UPC, Aztec, and many more symbologies. Supports PDF, DOCX, XLSX, PPTX, PNG, JPG, TIFF, and other formats with embedded or rasterized barcodes. Call this tool immediately whenever the user asks to read, scan, or extract barcodes or QR codes from a document. Do NOT pre-check whether files exist — just pass the filename the user provided. Returns a header line ('Found N barcode(s) in ...') followed by a JSON array of `{ index, value, type, page, confidence, angle }` per barcode, or a 'No barcodes found' message. On failure, the response text starts with 'Barcode extraction failed for' followed by the underlying exception type, message, and inner-exception chain.
| Name | Type | Req | Description |
|---|---|---|---|
| file | object | yes | – |
| page | integer|null | – | Page number to scan (1-based). Omit for all pages. |
| password | string|null | – | Password for protected documents |
No output schema declared.
No examples provided.
extract_images ~184
Extracts all images from a document and saves them to storage as separate image files. Supports PDF, DOCX, XLSX, PPTX, HTML, EPUB, and 30+ more formats with embedded images. Call this tool immediately whenever the user asks to extract images, get images, or save images from a document. Do NOT pre-check whether files exist — just pass the filename the user provided. Returns a list of saved-path messages, one per extracted image (named '<basename>_image<N>.<ext>'). On failure, the response text starts with 'Image extraction failed for' followed by the underlying exception type, message, and inner-exception chain.
| Name | Type | Req | Description |
|---|---|---|---|
| file | object | yes | – |
| page | integer|null | – | Page number to extract images from (1-based). Omit for all pages. |
| password | string|null | – | Password for protected documents |
No output schema declared.
No examples provided.
extract_metadata ~193
Extracts metadata from a document file (author, title, creation date, page count, custom properties, EXIF, XMP, IPTC) and returns it as JSON. Supports PDF, DOCX, XLSX, PPTX, JPEG, PNG, TIFF, MP3, MP4, and 50+ more document and image formats. Call this tool immediately whenever the user asks to extract metadata or get document properties from a file. Do NOT pre-check whether files exist — just pass the filename the user provided. Returns a JSON object whose keys are metadata field names (e.g. 'Author', 'Title', 'CreatedDate') and values are the corresponding string values. On failure, the response text starts with 'Metadata extraction failed for' followed by the underlying exception type, message, and inner-exception chain.
| Name | Type | Req | Description |
|---|---|---|---|
| file | object | yes | – |
| password | string|null | – | Password for protected documents |
No output schema declared.
No examples provided.
extract_tables ~272
Extracts tables from a document and returns them as Markdown (default) or JSON. Supports PDF, DOCX, XLSX, PPTX, HTML, and other tabular formats. Markdown tables render instantly in VS Code, GitHub, and AI chat — use this format to visually review table data right in the response. Use format='json' to get a structured array of rows for programmatic processing or further manipulation. Call this tool immediately whenever the user asks to extract, read, or view tables from a document. Do NOT pre-check whether files exist — just pass the filename the user provided. Returns either a Markdown document (multiple `### Table N (page N, R×C)` sections) or a JSON array of `{ table, page, rows, columns, data: string[][] }` objects. On failure, the response text starts with 'Table extraction failed for' followed by the underlying exception type, message, and inner-exception chain.
| Name | Type | Req | Description |
|---|---|---|---|
| file | object | yes | – |
| format | string | – | Output format: 'markdown' (default — renders in IDE and chat) or 'json' (structured data) |
| page | integer|null | – | Page number to extract tables from (1-based). Omit for all pages. |
| password | string|null | – | Password for protected documents |
No output schema declared.
No examples provided.
extract_text ~183
Extracts plain text from a document file. Supports PDF, DOCX, XLSX, PPTX, TXT, HTML, CSV, EML, MSG, RTF, ODT, EPUB, and 50+ more formats. Call this tool immediately whenever the user asks to extract text, read text, or get the content of a document. Do NOT pre-check whether files exist — just pass the filename the user provided. Returns the document's plain text (truncated with a marker if it exceeds the configured budget). On failure, the response text starts with 'Text extraction failed for' followed by the underlying exception type, message, and inner-exception chain.
| Name | Type | Req | Description |
|---|---|---|---|
| file | object | yes | – |
| page | integer|null | – | Page number to extract from (1-based). Omit for all pages. |
| password | string|null | – | Password for protected documents |
No output schema declared.
No examples provided.
get_document_info ~198
Returns basic information about a document — file type, page count, size — as JSON, without modifying the file. Supports PDF, DOCX, XLSX, PPTX, PNG, JPG, HTML, EPUB, MSG, EML, and 50+ more document formats. Call this tool whenever the user asks to get document info, check a file's details, or inspect it before extracting text / metadata / images / tables. Do NOT pre-check whether files exist — just pass the filename the user provided. Returns a JSON object with fields `fileName`, `fileType` (extension), `fileTypeName` (engine-reported format name), `pageCount`, and `size`. On failure, the response text starts with 'Document-info lookup failed for' followed by the underlying exception type, message, and inner-exception chain.
| Name | Type | Req | Description |
|---|---|---|---|
| file | object | yes | – |
| password | string|null | – | Password for protected documents |
No output schema declared.
No examples provided.
get_license_status ~135
Returns how this MCP server is licensed, and — under metered licensing — how much has been consumed. Call this when the user asks about licensing, evaluation limitations, metered usage, remaining credit, or which product engine version is running. Returns a JSON object with `mode` ("evaluation", "licensed" or "metered"), `licensed` (true for both licensed and metered), `consumption` (null unless metered; otherwise `quantity` and `credit`, or `error` if the reading failed), and `server` / `engine` name and version. Takes no arguments and never modifies anything.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.groupdocs-parser/groupdocs-parser-mcp server?
io.github.groupdocs-parser/groupdocs-parser-mcp is listed in the public MCP registry as io.github.groupdocs-parser/groupdocs-parser-mcp. MCP server for GroupDocs.Parser, extract text, images, metadata, tables, barcodes via AI. This page covers its container image (ghcr.io/groupdocs-parser/parser-net-mcp:26.9.0).
Is the io.github.groupdocs-parser/groupdocs-parser-mcp server safe to use?
io.github.groupdocs-parser/groupdocs-parser-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 io.github.groupdocs-parser/groupdocs-parser-mcp server expose?
io.github.groupdocs-parser/groupdocs-parser-mcp exposes 7 tools: extract_images, extract_barcodes, get_license_status, get_document_info, extract_text, and 2 more. Their descriptions and schemas cost roughly 1,417 tokens of context every time the server is loaded.
Is the io.github.groupdocs-parser/groupdocs-parser-mcp server still maintained?
io.github.groupdocs-parser/groupdocs-parser-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.groupdocs-parser/groupdocs-parser-mcp server under?
io.github.groupdocs-parser/groupdocs-parser-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.