Suparse Document Processing
NPM · @SUPARSE/MCP · SCANNED SEP 24
Extract structured data from PDFs and documents with Suparse AI OCR.
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 97 dependencies flagged as unhealthy. View diagnostics → Partial
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 2 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1100 tokens (~183/item across 6 items; 6 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 Management80
- Stability observed for 24 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_documents" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 6 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
How do I install the Suparse Document Processing MCP server?
Suparse Document Processing runs locally as an npm package, launched with npx -y @suparse/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @suparse/mcp
claude mcp add suparse-suparse-mcp -- npx -y @suparse/mcp
{
"mcpServers": {
"suparse-suparse-mcp": {
"command": "npx",
"args": [
"-y",
"@suparse/mcp"
]
}
}
} {
"servers": {
"suparse-suparse-mcp": {
"command": "npx",
"args": [
"-y",
"@suparse/mcp"
]
}
}
} codex mcp add suparse-suparse-mcp -- npx -y @suparse/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"suparse-suparse-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@suparse/mcp"
],
"enabled": true
}
}
} openclaw mcp add suparse-suparse-mcp --command npx --arg -y --arg @suparse/mcp
mcp_servers:
suparse-suparse-mcp:
command: "npx"
args: ["-y", "@suparse/mcp"] {
"McpServers": {
"suparse-suparse-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@suparse/mcp"
]
}
}
} assistant mcp add suparse-suparse-mcp -t stdio -c npx -a -y @suparse/mcp
{
"mcpServers": {
"suparse-suparse-mcp": {
"command": "npx",
"args": [
"-y",
"@suparse/mcp"
]
}
}
} 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.
- 23 Sept 26 −3
- Stability: pass → 0.77 functional
- 22 Sept 26 +1
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 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 24 Sept 2026 · Analysed npm/@suparse/mcp@1.3.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 97 packages
| Packages resolved | 97 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
delete_documents Delete Documents ~58
Delete one or more documents from Suparse by document ID.
| Name | Type | Req | Description |
|---|---|---|---|
| api_url | string | – | Optional API base URL. Defaults to SUPARSE_API_URL or Suparse production API. |
| document_ids | array | yes | Suparse document IDs to delete. |
| Name | Type | Req | Description |
|---|---|---|---|
| deleted | boolean | yes | – |
| document_ids | array | yes | – |
No examples provided.
download_results Download Results ~210
Fetch an export for one or more Suparse document IDs and write it directly to local disk. Use this for CSV, XLSX, Google Sheets, and saved JSON files. Do not call fetch_json_results unless you intentionally need full JSON in the MCP response. If output_path is a directory, the API-provided filename is used inside that directory. If cleanup is needed, call delete_documents after this tool succeeds.
| Name | Type | Req | Description |
|---|---|---|---|
| api_url | string | – | Optional API base URL. Defaults to SUPARSE_API_URL or Suparse production API. |
| document_ids | array | yes | Suparse document IDs to export. |
| export_type | string | – | Export mode for csv, xlsx, and google_sheets. Defaults to unified. |
| format | string | yes | Export format to write to local disk. Use this tool for csv and xlsx. |
| output_path | string | – | Optional local output file path or existing directory. When omitted, writes to the current working directory using the API-provided or generated filename. |
| Name | Type | Req | Description |
|---|---|---|---|
| document_ids | array | yes | – |
| export_type | string | yes | – |
| format | string | yes | – |
| output_path | string | yes | – |
No examples provided.
extract_file Extract File ~268
Process one local document through Suparse. Defaults to result_mode defer, which uploads and polls only, then returns compact task_id/document_ids for later download_results. Use result_mode return_json only when you need the full JSON extraction in the MCP response. cleanup is only valid with return_json.
| Name | Type | Req | Description |
|---|---|---|---|
| api_url | string | – | Optional API base URL. Defaults to SUPARSE_API_URL or Suparse production API. |
| cleanup | boolean | – | Only valid with result_mode return_json. Deletes processed Suparse documents after JSON results are returned, so later exports cannot be fetched from those document IDs. |
| file_path | string | yes | Local path to a supported document file. |
| result_mode | string | – | Controls whether extraction results in json format are returned directly. Use return_json only when you need the full JSON extraction in the MCP response. In all other cases you can retrieve the resu… |
| split | boolean | – | Enable auto-splitting of multi-page documents with mixed document types. |
| template_id | string | – | Optional extraction template ID. Use only a non-system team template ID from list_templates. Do not pass system template IDs directly; ask the user to add the matching system template to their templa… |
| Name | Type | Req | Description |
|---|---|---|---|
| failed | array | yes | – |
| result_mode | string | yes | – |
| succeeded | array | yes | – |
| total | number | yes | – |
No examples provided.
extract_folder Extract Folder ~272
Process all supported files in an immediate local folder through Suparse. Defaults to result_mode defer, which uploads and polls only, then returns compact task_id/document_ids for later download_results. Use result_mode return_json only when you need full JSON extractions in the MCP response. cleanup is only valid with return_json.
| Name | Type | Req | Description |
|---|---|---|---|
| api_url | string | – | Optional API base URL. Defaults to SUPARSE_API_URL or Suparse production API. |
| cleanup | boolean | – | Only valid with result_mode return_json. Deletes processed Suparse documents after JSON results are returned, so later exports cannot be fetched from those document IDs. |
| folder_path | string | yes | Local folder containing supported document files. |
| result_mode | string | – | Controls whether extraction results in json format are returned directly. Use return_json only when you need the full JSON extraction in the MCP response. In all other cases you can retrieve the resu… |
| split | boolean | – | Enable auto-splitting of multi-page documents with mixed document types. |
| template_id | string | – | Optional extraction template ID. Use only a non-system team template ID from list_templates. Do not pass system template IDs directly; ask the user to add the matching system template to their templa… |
| Name | Type | Req | Description |
|---|---|---|---|
| failed | array | yes | – |
| result_mode | string | yes | – |
| succeeded | array | yes | – |
| total | number | yes | – |
No examples provided.
fetch_json_results Fetch JSON Results ~131
Fetch JSON extraction results for one or more Suparse document IDs directly in the MCP response. This can be large; use only when you need the full JSON in context. For CSV, XLSX, Google Sheets, or saved JSON files, use download_results. If you need cleanup after fetching, call delete_documents after this tool succeeds.
| Name | Type | Req | Description |
|---|---|---|---|
| api_url | string | – | Optional API base URL. Defaults to SUPARSE_API_URL or Suparse production API. |
| document_ids | array | yes | Suparse document IDs to export. |
| export_type | string | – | Export mode for JSON results. Defaults to unified. |
| Name | Type | Req | Description |
|---|---|---|---|
| export_type | string | yes | – |
| format | string | yes | – |
| results | array | yes | – |
No examples provided.
list_templates List Templates ~161
List extraction templates for choosing an extraction template. Agents must use team_templates for processing. System templates are discovery-only in MCP: if a matching system template exists but no matching team template exists, ask the user to add that system template to their templates in the Suparse UI before processing. If no matching team or system template exists, ask the user to create a custom extraction schema for that document type in the Suparse UI.
| Name | Type | Req | Description |
|---|---|---|---|
| api_url | string | – | Optional API base URL. Defaults to SUPARSE_API_URL or Suparse production API. |
| include_system | boolean | – | Include discovery-only system templates in addition to team templates. System templates returned here are not directly usable for extraction through MCP until the user adds them to their templates in… |
| Name | Type | Req | Description |
|---|---|---|---|
| agent_guidance | string | yes | – |
| system_templates | array | yes | – |
| team_templates | array | yes | – |
| templates | array | yes | – |
No examples provided.
What is the Suparse Document Processing MCP server?
Suparse Document Processing is an MCP server listed in the public MCP registry as io.github.suparse/suparse-mcp. Extract structured data from PDFs and documents with Suparse AI OCR. This page covers its npm package (@suparse/mcp).
Is the Suparse Document Processing MCP server safe to use?
Suparse Document Processing scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. 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 Suparse Document Processing MCP server expose?
Suparse Document Processing exposes 6 tools: extract_file, extract_folder, list_templates, fetch_json_results, download_results, delete_documents. Their descriptions and schemas cost roughly 1,100 tokens of context every time the server is loaded.
Is the Suparse Document Processing MCP server still maintained?
Suparse Document Processing is still listed as active in the MCP registry. We last reached this channel on 24 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 Suparse Document Processing MCP server under?
Suparse Document Processing declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.