MCP.Market

Doc Extract MCP server

by koraynar·io.github.koraynar/doc-extract-mcp·v0.1.0

Document tooling for AI agents: PDF/text reading, chunking, schema-validated JSON output.

C63/100grade C
What users say
No reviews yet
Be the first
Safety scan
C63/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Doc Extract yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Doc Extract tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-10-30 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualityno auth information5/15
  • Maintenancelast push 63 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 63/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Doc Extract compares

Against every graded Scraping and browsing MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
63/100
higher than 18% of 867 Scraping and browsing servers

Install Doc Extract in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the Doc Extract repository's README, as published. We do not edit it. Read it on GitHub

doc-extract-mcp

An MCP (Model Context Protocol) server that gives an LLM deterministic document tooling for structured-data extraction workflows. The LLM does the reading and extraction reasoning; this server provides the parts that should never be left to a language model: reliable file access, parsing, chunking, JSON Schema validation, and guarded file output.

Built by Koray Nar as a portfolio project for the AI document-automation workflows he is building — the target use case is turning messy PDFs (purchase orders, invoices, reports) into schema-validated JSON. Published as part of a public portfolio. Pairs with Claude Code and Claude Desktop, and with any other MCP client.

Why

An extraction agent fails in predictable places: it hallucinates file contents, loses track of long documents, silently produces JSON that almost matches the target schema, and writes output wherever it likes. This server removes those failure modes:

"page 3" mean page 3.

  • File access is confined to one allowed root (DOCEXTRACTROOT).
  • PDF text arrives with explicit --- page N --- markers, so citations of

error is reported with a JSON Pointer path — not just the first — so the model can fix all mistakes in one pass.

  • Long documents are chunked deterministically with overlap and page hints.
  • Extracted JSON is checked against a JSON Schema (Draft 2020-12) and every

verifiable row/byte count.

  • Output is written by the server (JSON or CSV), inside the same root, with a

Tools

All path arguments are resolved and refused if they escape the allowed root (path traversal guard). The glob_pattern argument is confined the same way: absolute patterns and patterns containing .. are rejected, and any match that resolves outside the root (for example through a symlink) is silently dropped from the listing. Guard failures are raised as MCP tool errors, so the calling model sees the actual reason, not a masked generic error.

Quickstart

Requires Python 3.11+ and uv.

git clone https://github.com/koraynar/doc-extract-mcp.git
cd doc-extract-mcp
uv venv
uv pip install -e .

Run standalone (stdio transport):

DOC_EXTRACT_ROOT=/path/to/your/documents uv run doc-extract-mcp

Claude Code

claude mcp add doc-extract --env DOC_EXTRACT_ROOT=/path/to/your/documents \
  -- uv run --directory /absolute/path/to/doc-extract-mcp doc-extract-mcp

Claude Desktop

Add to claudedesktopconfig.json:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Grade history

  • 2026-10-30downgradeB → Cscore 63

Doc Extract: common questions

Is Doc Extract MCP server safe?
With care: it is graded C, so read the findings first (63/100). Read the Doc Extract safety report
Does Doc Extract need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Doc Extract maintained?
The last commit was 69 days ago (2026-08-28). The latest release is v0.1.0.
What can I use instead of Doc Extract?
Servers from other publishers that do the same job: Talonic MCP server, Mistral MCP server and three.ws Solana Memo Media MCP server.

Alternatives to Doc Extract

Same job from other publishers: the closest match first, then the best rated.

  • Talonic
    Extract structured, schema-validated data from PDFs, scans, images, spreadsheets, and forms.
    A
  • Mistral
    Mistral MCP server: extract invoices and documents from text, Markdown or OCR into typed JSON.
    B
  • three.ws Solana Memo Media
    Extract validated image data URIs from Solana SPL Memos and return them inline to MCP clients.
    A
  • Pinkpixel Dev Web Scout
    Search the web and extract clean, readable text from webpages. Process multiple URLs at once to sp…
    A
  • Kitewright
    Lightweight browser automation for AI agents: navigate, screenshot, extract, PDF. One small binary.
    A