dual-extract-mcp
Related Servers
Alternatives to dual-extract-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceLocal MCP server for PDFs: read PDFs into Markdown with tables, charts and OCR, export to Word, PowerPoint, EPUB and Excel, and merge, split, fill, compare and edit PDFs. Works only inside the folders you allow; nothing is uploaded.30120 npmApache 2.0
- AlicenseAqualityDmaintenanceFast, local PDF parsing as an MCP server with text extraction, bounding boxes, OCR, and visual citations. No cloud or API key required.5MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to extract text from PDF, image, Word, PowerPoint, and Excel files using MinerU, either on the local machine or a self-hosted private-network API. Parsed results are saved locally as Markdown, structured JSON, and extracted images, which can then be read back in segments.MIT
- AlicenseAqualityDmaintenanceA local-first MCP server that ingests PDFs, extracts structure, and provides semantic search and sequential navigation tools for AI clients to query and learn from documents.10MIT
- FlicenseNot gradedqualityDmaintenanceA local MCP server that extracts text-layer content from PDF files, enabling AI agents to inspect, extract text, outlines, and page content.-
- AlicenseAqualityAmaintenanceFull-stack PDF intelligence MCP server for extracting, manipulating, annotating, converting, validating, and RAG-searching PDFs through a unified tool surface and React workbench.161MIT
TDQS
Scored across 8 tools
The extraction tools are separated by pipeline (text, vision, dual), and table/formula/inspection/validation/health tools occupy distinct roles. The only mild ambiguity is among parse_text, vision_extract, and dual_extract, but their descriptions clearly label them as separate routes.
Most tools follow a verb_noun pattern: inspect_document, validate_output, parse_text, vision_extract, extract_table, extract_formulas. Minor inconsistencies exist: health is a bare noun, and parse_text uses 'parse' while others use 'extract'.
8 tools is well-scoped for a PDF dual-extraction service: one preflight inspector, three extraction routes, two specialized extractors, one output validator, and one health check. No tool feels redundant.
The tool surface covers the full workflow: inspect_document preflights, parse_text/vision_extract/dual_extract handle text/vision/fusion extraction, extract_table and extract_formulas cover specialized content, validate_output closes the loop, and health covers service dependencies. No critical dead-end or missing operation is apparent.