ToolsMCP
Suparse Document Processing
Listed in the official MCP Registry with an installable npm package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- suparse (GitHub)
- Prerequisites
- Install @suparse/mcp from npm (stdio transport). Declares 1 secret input. Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 1.5.0 · updated
- Official links
Publisher’s description
Extract data, create schemas, and export results from PDFs and documents with Suparse AI OCR.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 1.5.0, registry status active. 1 package (npm)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- suparse (GitHub)
- Version observed
- 1.5.0
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.suparse%2Fsuparse-mcp/versions/1.5.0
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Extract structured data from PDFs | Publisher description mentions “pdfs”, “extract”, “ocr”. | No connection check or task run. Capability is as described by the publisher. | Rule pdf-extraction matched: “pdfs”, “extract”, “ocr”. Rule pdf-extraction. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
@suparse/mcp(npm, stdio, 1 secret input)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.suparse/suparse-mcp
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.