Suparse Document Processing

NPM · @SUPARSE/MCP · SCANNED AUG 3

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

Available components

+22 this week 66 66 Trust /100

Trust breakdown (6 categories)

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 →

Supply Chain Security87

No malware found by supply-chain analysis.Pass
Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree.Partial
No install/post-install scripts declared.Pass
Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree. View diagnostics → Partial

Provenance & Transparency45

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 61 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability61

AI-judged instruction clarity (good).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 Management23

Stability observed for 7 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

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @suparse/mcp

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# add to Codex CLI

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

# add to OpenClaw

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

# ~/.hermes/config.yaml

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

// mcp.json

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

Changelog

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.

3 Aug 26 +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.
2 Aug 26 +46
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Security disclosure: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Stability: unverified → 0.20 ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- First check of Schema quality: unverified functional
- Licence: MIT functional
31 Jul 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
27 Jul 26 44

First indexed and scored.

Show 2 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 2026 · Analysed npm/@suparse/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 96 packages

96 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 6 exposed · ~1,100 tokens

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.

Tool Tokens

delete_documents Delete Documents ~58

Delete one or more documents from Suparse by document ID.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 3 Aug