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.

Markovo File to Text, Word and Markdown

PYPI · MARKOVO · 2 COMPONENTS

Convert files and authorized public HTTPS pages to text, editable Word or Markdown.

+1 this week 67 Trust /100

Last scanned (4 hours ago)

Scores higher than 65% 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 Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency87
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to fisher-byte/markovo). View diagnostics → Pass
  • Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
  • Actively maintained (last published 5 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability51
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 447 tokens (~40/item across 11 items; 11 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 14% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "markovo_asset_revoke" implies "revoke" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (14)

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

Checks we could not complete (2)

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.
  • License in Provenance & TransparencyLicence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.

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.

  • 4 Nov 26 +1
    • Stability: 0.97 → pass security
  • 3 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 2 Nov 26 +14
    • Malware scan: unverified → pass ▲ security
    • Stability: pass → 0.93 functional
  • 1 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 31 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 30 Oct 26 +1
    • License: fail → unverified ▼ functional
    • Tool coverage: 5% → 14% ▲ functional
    • Package version: 0.1.1 → 0.1.2 functional
  • 29 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 27 Oct 26 0
    • Stability: 0.97 → pass security
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 5 Nov 2026 · Analysed pypi/markovo@0.1.2

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 fisher-byte/markovo
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/fisher-byte/markovo/.github/workflows/publish-pypi.yml@refs/heads/main
Rekor log index 3600604622
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:c39dda1516a424f95dfd6a83887ba4c24c382ab311a677424aa414dca0b855e0

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 11 exposed · ~447 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
markovo_asset_revoke ~37

Revoke a temporary asset URL before it expires.

NameTypeReqDescription
grant_idstring––
job_idstring––

No output schema declared.

No examples provided.

markovo_asset_url ~51

Create a revocable 60-600 second bearer URL for one Bundle image.

NameTypeReqDescription
asset_pathstring––
expires_in_secondsinteger––
job_idstring––

No output schema declared.

No examples provided.

markovo_billing ~16

Return the secure billing URL.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

markovo_bundle_verify ~24

Verify a downloaded Markovo bundle.

NameTypeReqDescription
bundlestring––

No output schema declared.

No examples provided.

markovo_capabilities ~16

Fetch the live capability registry.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

markovo_convert ~115

Convert a supported file through the account-metered Markovo API.

NameTypeReqDescription
capability_idstring––
download_formatstring––
input_pathstringyes–
layout_fidelitystring–Compatibility-only formula flag for PDFs; normalized to the standard pipeline. The formula-region Beta is retired.
max_creditsnumber–Convenience safety ceiling; defaults to 15 Credits. Set an explicit bound for deliberate automation.
modestring––
out_dirstringyes–

No output schema declared.

No examples provided.

markovo_convert_url ~102

Convert one public HTTPS page after explicit consent to Markovo's isolated remote fetch.

NameTypeReqDescription
accept_remote_fetchbooleanyes–
download_formatstring––
max_creditsnumber–Convenience safety ceiling; defaults to 15 Credits. Set an explicit bound for deliberate automation.
out_dirstringyes–
poll_attemptsinteger––
poll_interval_secondsnumber––
urlstringyes–

No output schema declared.

No examples provided.

markovo_doctor ~20

Check client, service, and API-key readiness.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

markovo_job_assets ~29

List manifest-verified image assets for a completed job.

NameTypeReqDescription
job_idstring––

No output schema declared.

No examples provided.

markovo_job_status ~23

Fetch a remote job.

NameTypeReqDescription
job_idstring––

No output schema declared.

No examples provided.

markovo_usage ~14

Fetch account Credit usage.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Markovo File to Text, Word and Markdown MCP server?

Markovo File to Text, Word and Markdown runs locally as a PyPI package, launched with uvx markovo 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 · markovo

# add to Claude Code
claude mcp add fisher-byte-markovo -- uvx markovo mcp
Common questions

What is the Markovo File to Text, Word and Markdown MCP server?

Markovo File to Text, Word and Markdown is an MCP server listed in the public MCP registry as io.github.fisher-byte/markovo. Convert files and authorized public HTTPS pages to text, editable Word or Markdown. This page covers its PyPI package (markovo).

Is the Markovo File to Text, Word and Markdown MCP server safe to use?

Markovo File to Text, Word and Markdown scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 Markovo File to Text, Word and Markdown MCP server expose?

Markovo File to Text, Word and Markdown exposes 11 tools: markovo_convert, markovo_convert_url, markovo_job_status, markovo_job_assets, markovo_asset_url, and 6 more. Their descriptions and schemas cost roughly 447 tokens of context every time the server is loaded.

Is the Markovo File to Text, Word and Markdown MCP server still maintained?

Markovo File to Text, Word and Markdown is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Markovo File to Text, Word and Markdown MCP server?

VerifyMCP ran 14 checks on Markovo File to Text, Word and Markdown, covering Known CVEs, Install scripts, Dependency health, Source repository and 10 more. 2 items could not be completed, a gap on our side rather than a finding about Markovo File to Text, Word and Markdown: Malware scan and License. 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.