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.

OpenDocKit

PYPI · OPENDOCKIT-MCP

Read local PDF, Office, HWP, OpenDocument, RTF, EPUB, HTML and email files as Markdown. Offline.

Available components

+4 this week 67 Trust /100

Last scanned (10 hours ago)

Scores higher than 60% 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
  • 4 of 20 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 hyeonsang010716/OpenDocKit). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 290 tokens (~145/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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 −14
    • Malware scan: pass → unverified ▼ security
  • 20 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 19 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.3.13 → 0.3.14 functional
  • 18 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 17 Nov 26 +1
    • Package version: 0.3.11 → 0.3.13 functional
  • 16 Nov 26 0
    • Malware scan: unverified → pass ▲ security
    • Security disclosure: pass → unverified ▼ functional
    • Package version: 0.3.7 → 0.3.11 functional
    • Package version: 0.3.7 → 0.3.10 functional
    • Package version: 0.3.7 → 0.3.9 functional
    • Package version: 0.3.7 → 0.3.8 functional
  • 15 Nov 26 +1
    • Malware scan: unverified → pass ▲ security
    • Package version: 0.3.5 → 0.3.7 functional
    • Package version: 0.3.5 → 0.3.6 functional
  • 14 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Stability: unverified → 0.03 ▲ functional
    • Package version: 0.3.2 → 0.3.5 functional
    • Package version: 0.3.2 → 0.3.4 functional
    • Package version: 0.3.2 → 0.3.3 functional
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/opendockit-mcp@0.3.14

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 hyeonsang010716/OpenDocKit
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/hyeonsang010716/OpenDocKit/.github/workflows/release.yml@refs/tags/v0.3.14
Rekor log index 3990666038
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:884c2d1cf2498c5ca73a82429a68325273ce68e8ec3e29d160ad40a80ffb2dbb

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 20 packages
Packages resolved 20
Stale 4
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~197 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
convert_document ~120

Convert a local document to Markdown. path: the file to read (absolute, or relative to where the server was started). sections: which pages, slides or sheets to return, by their numbers in document_outline: "3" or "2-5". Leave out for the whole document. max_chars: the most characters of the document to return (default 100,000). A longer text is cut there, and a note after it says so.

NameTypeReqDescription
max_charsinteger––
pathstringyes–
sections–––

No output schema declared.

No examples provided.

document_outline ~77

Describe a local document without returning its text: format, title, size, and its pages, slides or sheets with their numbers, titles and lengths. Use it to decide which `sections` to ask convert_document for. path: the file to read (absolute, or relative to where the server was started).

NameTypeReqDescription
pathstringyes–

No output schema declared.

No examples provided.

Install

How do I install the OpenDocKit MCP server?

OpenDocKit runs locally as a PyPI package, launched with uvx opendockit-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · opendockit-mcp

# add to Claude Code
claude mcp add hyeonsang010716-opendockit -- uvx opendockit-mcp
Common questions

What is the OpenDocKit MCP server?

OpenDocKit is an MCP server listed in the public MCP registry as io.github.hyeonsang010716/opendockit. Read local PDF, Office, HWP, OpenDocument, RTF, EPUB, HTML and email files as Markdown. Offline. This page covers its PyPI package (opendockit-mcp).

Is the OpenDocKit MCP server safe to use?

OpenDocKit scores 67 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 OpenDocKit MCP server expose?

OpenDocKit exposes 2 tools: convert_document, document_outline. Their descriptions and schemas cost roughly 197 tokens of context every time the server is loaded.

Is the OpenDocKit MCP server still maintained?

OpenDocKit 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 OpenDocKit MCP server under?

OpenDocKit declares the MIT 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 OpenDocKit MCP server?

VerifyMCP ran 15 checks on OpenDocKit, 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 OpenDocKit: 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.