# Suparse Document Processing (npm · @suparse/mcp)

Extract structured data from PDFs and documents with Suparse AI OCR.

- Trust score: 66/100 (medium)
- Change this week: +22
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `@suparse/mcp`: 66/100 (this document), [markdown](https://verifymcp.io/servers/suparse-suparse-mcp/suparse-mcp.md), [page](https://verifymcp.io/servers/suparse-suparse-mcp/suparse-mcp)

## Channel facts

- Registry: `npm`
- Package: `@suparse/mcp`
- Version: `1.3.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-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/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 61 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add suparse-suparse-mcp -- npx -y @suparse/mcp
```

### Codex

```bash
codex mcp add suparse-suparse-mcp -- npx -y @suparse/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "suparse-suparse-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@suparse/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add suparse-suparse-mcp --command npx --arg -y --arg @suparse/mcp
```

### Hermes

```yaml
mcp_servers:
  suparse-suparse-mcp:
    command: "npx"
    args: ["-y", "@suparse/mcp"]
```

### Other

```json
{
  "mcpServers": {
    "suparse-suparse-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@suparse/mcp"
      ]
    }
  }
}
```

## 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-08-03 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 65, +46)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [functional regression] Security disclosure: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Stability: unverified → 0.20
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Schema quality: unverified → good
- [functional] First check of Schema quality: unverified
- [functional] Licence: MIT

### 2026-07-31 (score 19, −7)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 26, −18)

- [security regression] Malware scan: pass → unverified

### 2026-07-27 (score 44)

First indexed and scored.

## MCP tools (6)

### `extract_file` (~268 tokens)

Extract File

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.

Input parameters:

- `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, required): 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…

Output parameters:

- `failed` (array)
- `result_mode` (string)
- `succeeded` (array)
- `total` (number)

### `extract_folder` (~272 tokens)

Extract Folder

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.

Input parameters:

- `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, required): 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…

Output parameters:

- `failed` (array)
- `result_mode` (string)
- `succeeded` (array)
- `total` (number)

### `list_templates` (~161 tokens)

List Templates

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.

Input parameters:

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

Output parameters:

- `agent_guidance` (string)
- `system_templates` (array)
- `team_templates` (array)
- `templates` (array)

### `fetch_json_results` (~131 tokens)

Fetch JSON Results

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.

Input parameters:

- `api_url` (string): Optional API base URL. Defaults to SUPARSE_API_URL or Suparse production API.
- `document_ids` (array, required): Suparse document IDs to export.
- `export_type` (string): Export mode for JSON results. Defaults to unified.

Output parameters:

- `export_type` (string)
- `format` (string)
- `results` (array)

### `download_results` (~210 tokens)

Download Results

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.

Input parameters:

- `api_url` (string): Optional API base URL. Defaults to SUPARSE_API_URL or Suparse production API.
- `document_ids` (array, required): Suparse document IDs to export.
- `export_type` (string): Export mode for csv, xlsx, and google_sheets. Defaults to unified.
- `format` (string, required): 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.

Output parameters:

- `document_ids` (array)
- `export_type` (string)
- `format` (string)
- `output_path` (string)

### `delete_documents` (~58 tokens)

Delete Documents

Delete one or more documents from Suparse by document ID.

Input parameters:

- `api_url` (string): Optional API base URL. Defaults to SUPARSE_API_URL or Suparse production API.
- `document_ids` (array, required): Suparse document IDs to delete.

Output parameters:

- `deleted` (boolean)
- `document_ids` (array)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/suparse-suparse-mcp/suparse-mcp#diagnostics

## Score history

- 2026-08-03: 66
- 2026-08-02: 65
- 2026-08-01: 19
- 2026-07-31: 19
- 2026-07-30: 26
- 2026-07-28: 44
- 2026-07-27: 44

## Links

- npm package: https://www.npmjs.com/package/@suparse/mcp
- Socket report: https://socket.dev/npm/package/@suparse/mcp
- Repository: https://github.com/suparse/suparse-mcp
- Website: https://www.suparse.com/
- Changelog RSS feed: https://verifymcp.io/servers/suparse-suparse-mcp/suparse-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/suparse-suparse-mcp/suparse-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/suparse-suparse-mcp/suparse-mcp