Word to Markdown
NPM · WORD-TO-MARKDOWN
Convert Word (.docx) documents to Markdown via CLI, Node.js, or browser
Available components
Last scanned (3 hours ago)
Scores higher than 81% of npm servers
Category Documents and Files
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 Security89
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects re2js 2.8.6, reached via markdownlint > re2js. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 60 of 172 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 benbalter/word-to-markdown-js). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 10 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 365 tokens (~365/item across 1 items; 1 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 Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 −2
- CVE-2026-116795 affects this package: high ▼ security
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
- Stability: 0.20 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.8.0 → 0.9.0 functional
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.10 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.7.0 → 0.8.0 functional
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 npm/word-to-markdown@0.9.0
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 | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | benbalter/word-to-markdown-js |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/benbalter/word-to-markdown-js/.github/workflows/release.yml@refs/tags/v0.9.0 |
| Rekor log index | 3471488779 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:6fcd377d263a3e1e30b3b5d4a29ef66b411124814af20d934f18f7c01f632630eb8f0efc5b41e9653473c7a5f85a250fc851ee58a813a23aec69b2482 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 2 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-238p-pmpm-9mq7 | CVE-2026-103923 | low | yes | |
| GHSA-gg6h-894w-4m9c | CVE-2026-116795 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 172 packages
| Packages resolved | 172 |
|---|---|
| Stale | 60 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
convert_docx_to_markdown Convert Word to Markdown ~239
Convert a Word (.docx) file to GitHub-flavored Markdown. Returns the Markdown plus any document warnings (encryption, sensitivity labels, content that could not be converted). Only .docx is supported; re-save older .doc files as .docx first.
| Name | Type | Req | Description |
|---|---|---|---|
| bullet_lists | boolean | – | Turn numbered lists into bullets. |
| image_dir | string | – | Extract images into this folder and link them from the Markdown. A relative folder inside output_path's folder when set, else the .docx's. Omit to drop images. |
| output_path | string | – | Write the Markdown to this .md file instead of returning it. Useful for long documents. |
| overwrite | boolean | – | Replace output_path or image files that already exist. Off by default, so a conversion never clobbers a file by accident. |
| path | string | yes | Path to the .docx file. Relative paths resolve against the server's working directory, so prefer an absolute path. |
| preserve_footnotes | boolean | – | Keep footnotes as raw <sup> links instead of GFM [^1] footnotes. |
| Name | Type | Req | Description |
|---|---|---|---|
| images_written | number | – | – |
| markdown | string | – | The Markdown, unless output_path was set. |
| output_path | string | – | – |
| warnings | array | yes | – |
No examples provided.
How do I install the Word to Markdown MCP server?
Word to Markdown runs locally as an npm package, launched with npx -y word-to-markdown. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · word-to-markdown
claude mcp add benbalter-word-to-markdown -- npx -y word-to-markdown
What is the Word to Markdown MCP server?
Word to Markdown is an MCP server listed in the public MCP registry as io.github.benbalter/word-to-markdown. Convert Word (.docx) documents to Markdown via CLI, Node.js, or browser. This page covers its npm package (word-to-markdown).
Is the Word to Markdown MCP server safe to use?
Word to Markdown scores 84 out of 100 on VerifyMCP. We recorded 2 known advisories against 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 Word to Markdown MCP server expose?
Word to Markdown exposes 1 tool: convert_docx_to_markdown. Their descriptions and schemas cost roughly 239 tokens of context every time the server is loaded.
Is the Word to Markdown MCP server still maintained?
Word to 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 licence is the Word to Markdown MCP server under?
Word to Markdown 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.