Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ReadAnyDoc

PYPI · READANYDOC

Parse PDFs, scans and Office files to Markdown; extract typed fields with page citations.

Available components

64 Trust /100

Last scanned (14 hours ago)

Scores higher than 56% of PyPI servers

Category Documents and Files

Trust breakdown (7 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 → Why this is hard to score →

Supply Chain Security49
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 5 of 51 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to arpitpatel25/ReadAnyDoc). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability58
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 749 tokens (~187/item across 4 items; 4 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 Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Nov 26 0
    • Package version: 0.4.4 → 0.4.6 functional
  • 19 Nov 26 +1
    • Schema quality: 392 → 749 ▼ functional
    • Schema quality: 196 → 170 ▲ functional
    • Package version: 0.3.0 → 0.4.4 functional
    • Package version: 0.3.0 → 0.4.3 functional
    • Package version: 0.3.0 → 0.4.2 functional
  • 18 Nov 26 −1
    • Schema quality: pass → fail ▼ functional
    • Package version: 0.1.8 → 0.3.0 functional
    • Package version: 0.1.8 → 0.2.0 functional
  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 0
    • Malware scan: unverified → pass ▲ security
    • Stability: unverified → 0.03 ▲ functional
    • Package version: 0.1.6 → 0.1.8 functional
  • 15 Nov 26 62

    First indexed and scored.

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 21 Nov 2026 · Analysed pypi/readanydoc@0.4.6

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo arpitpatel25/ReadAnyDoc
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/arpitpatel25/ReadAnyDoc/.github/workflows/release.yml@refs/tags/v0.4.6
Rekor log index 4026861568
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:770bcf5c6951743971387226b205e6819abfcad21a0a538026a4173411a5abda

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 51 packages
Packages resolved 51
Stale 4
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~606 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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
extract_fields ~278

Extract structured values from a local document into a JSON Schema, with citations. schema: a JSON Schema object (type "object" with properties). instructions: optional guidance for the extraction. array_extract: true for long lists or tables that span many pages. review: also list values to check (found by code, no extra cost). alternatives: also return other values the document gives for a field (a special term or an amendment that changes a price). part_tokens: largest document part per call, in tokens (default 30,000). parse_first: false to skip parsing (the model reads the file itself: about half the cost and faster, less accurate, fewer citations). fill_required: which required fields always get a value: "choices" (default, yes/no and enum fields), true (numbers and text too: the model may guess, each guess is flagged in to_check as filled_because_required), a list of field paths, or false (nothing forced).

NameTypeReqDescription
alternativesboolean––
array_extractboolean––
fill_required–––
instructions–––
modestring––
parse_firstboolean––
part_tokens–––
pathstringyes–
reviewboolean––
schemaobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

list_test_sets ~55

The public test sets (invoices, receipts, financial reports, contracts, research papers, resumes, result tables, long reports), with what each tests, its size and its licence, and the systems that can be compared.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

parse_document ~96

Parse a local document (PDF, image, DOCX, XLSX, PPTX ...) into Markdown. path: file on this computer. mode: "engine" (default, most accurate) or "model-only" (one model read per page, faster). pages: 1-based page numbers to read; all pages when omitted.

NameTypeReqDescription
modestring––
pages–––
pathstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

run_test ~177

Compare systems on a public test set (set_id) or on the user's own documents (folder + schema_path, and answers_folder with <file stem>.json answer keys if they have them). Scored by code against the answer key. With confirm=false (the default) nothing is spent: it returns the plan (documents, pages, rough cost per system, systems that cannot run and why). Ask the user, then call again with confirm=true to run it. Returns the scores per system and the path of an HTML report with a citation viewer for every document.

NameTypeReqDescription
answers_folder–––
budget_usd–––
confirmboolean––
folder–––
limit–––
out–––
schema_path–––
set_id–––
systems–––

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the ReadAnyDoc MCP server?

ReadAnyDoc runs locally as a PyPI package, launched with uvx --from 'readanydoc[engine]==0.4.6' readanydoc mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

pypi · readanydoc

# add to Claude Code
claude mcp add arpitpatel25-readanydoc -- uvx --from 'readanydoc[engine]==0.4.6' readanydoc mcp
Common questions

What is the ReadAnyDoc MCP server?

ReadAnyDoc is an MCP server listed in the public MCP registry as io.github.arpitpatel25/readanydoc. Parse PDFs, scans and Office files to Markdown; extract typed fields with page citations. This page covers its PyPI package (readanydoc).

Is the ReadAnyDoc MCP server safe to use?

ReadAnyDoc scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the ReadAnyDoc MCP server expose?

ReadAnyDoc exposes 4 tools: parse_document, extract_fields, list_test_sets, run_test. Their descriptions and schemas cost roughly 606 tokens of context every time the server is loaded.

Is the ReadAnyDoc MCP server still maintained?

ReadAnyDoc is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the ReadAnyDoc MCP server under?

ReadAnyDoc declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the ReadAnyDoc MCP server?

VerifyMCP ran 15 checks on ReadAnyDoc, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about ReadAnyDoc: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.