Skip to main content
Glama
magicyuanh

dual-extract-mcp

by magicyuanh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to dual-extract-mcp

No user-submitted related servers found.

    Related Servers

    • pdf-context

      mematcha
      A
      license
      A
      quality
      D
      maintenance
      A 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.
      10
      MIT

    • pdf-agent-mcp

      sanhua1
      F
      license
      Not graded
      quality
      D
      maintenance
      A local MCP server that extracts text-layer content from PDF files, enabling AI agents to inspect, extract text, outlines, and page content.
      -

    • pdf-mcp

      sandraschi
      A
      license
      A
      quality
      A
      maintenance
      Full-stack PDF intelligence MCP server for extracting, manipulating, annotating, converting, validating, and RAG-searching PDFs through a unified tool surface and React workbench.
      16
      1
      MIT

    • netherbymultimodal

      J-X0
      A
      license
      A
      quality
      D
      maintenance
      Enables fully air-gapped multimodal document processing by fusing layout parsing with text extraction to produce ordered, labelled reading blocks and reconstructed text via an MCP stdio server.
      1
      Academic Free v1.1
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 8 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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'.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources