# Word to Markdown (npm · word-to-markdown)

Convert Word (.docx) documents to Markdown via CLI, Node.js, or browser

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `word-to-markdown`: 84/100 (this document), [markdown](https://verifymcp.io/servers/benbalter-word-to-markdown/word-to-markdown.md), [page](https://verifymcp.io/servers/benbalter-word-to-markdown/word-to-markdown)

## Channel facts

- Registry: `npm`
- Package: `word-to-markdown`
- Version: `0.9.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 89/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects re2js 2.8.6, reached via markdownlint > re2js. A fixed version is available.
  - No install/post-install scripts declared.
  - 60 of 172 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to benbalter/word-to-markdown-js).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 10 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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 mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add benbalter-word-to-markdown -- npx -y word-to-markdown mcp
```

### Cursor

```json
{
  "mcpServers": {
    "benbalter-word-to-markdown": {
      "command": "npx",
      "args": [
        "-y",
        "word-to-markdown",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "benbalter-word-to-markdown": {
      "command": "npx",
      "args": [
        "-y",
        "word-to-markdown",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add benbalter-word-to-markdown -- npx -y word-to-markdown mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "benbalter-word-to-markdown": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "word-to-markdown",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add benbalter-word-to-markdown --command npx --arg -y --arg word-to-markdown --arg mcp
```

### Hermes

```yaml
mcp_servers:
  benbalter-word-to-markdown:
    command: "npx"
    args: ["-y", "word-to-markdown", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "benbalter-word-to-markdown": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "word-to-markdown",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add benbalter-word-to-markdown -t stdio -c npx -a -y word-to-markdown mcp
```

### Other

```json
{
  "mcpServers": {
    "benbalter-word-to-markdown": {
      "command": "npx",
      "args": [
        "-y",
        "word-to-markdown",
        "mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 84, +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.

### 2026-11-02 (score 83, +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.

### 2026-10-30 (score 82, +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.

### 2026-10-29 (score 81, −2)

- [security regression] CVE-2026-116795 affects this package: high

### 2026-10-28 (score 83, +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.

### 2026-10-26 (score 82, +1)

- [security regression] Stability: 0.20 → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.8.0 → 0.9.0

### 2026-10-24 (score 81, +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.

### 2026-10-22 (score 80, +1)

- [security regression] 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.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.10
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.7.0 → 0.8.0

## MCP tools (1)

### `convert_docx_to_markdown` (~239 tokens)

Convert Word to Markdown

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.

Input parameters:

- `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, required): 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.

Output parameters:

- `images_written` (number)
- `markdown` (string): The Markdown, unless output_path was set.
- `output_path` (string)
- `warnings` (array)

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/benbalter-word-to-markdown/word-to-markdown#diagnostics

## Score history

- 2026-11-05: 84
- 2026-11-04: 84
- 2026-11-03: 83
- 2026-11-02: 83
- 2026-11-01: 82
- 2026-10-31: 82
- 2026-10-30: 82
- 2026-10-29: 81
- 2026-10-28: 83
- 2026-10-27: 82
- 2026-10-26: 82
- 2026-10-25: 81
- 2026-10-24: 81
- 2026-10-23: 80
- 2026-10-22: 80
- 2026-10-21: 79
- 2026-10-20: 79
- 2026-10-19: 64

## Common questions

### 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.

### What did VerifyMCP test on the Word to Markdown MCP server?

VerifyMCP ran 16 checks on Word to Markdown, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/word-to-markdown
- Socket report: https://socket.dev/npm/package/word-to-markdown
- Repository: https://github.com/benbalter/word-to-markdown-js
- Website: https://word2md.com/
- Changelog RSS feed: https://verifymcp.io/servers/benbalter-word-to-markdown/word-to-markdown.xml
- Changelog JSON feed: https://verifymcp.io/servers/benbalter-word-to-markdown/word-to-markdown/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/benbalter-word-to-markdown/word-to-markdown.json
- HTML version of this page: https://verifymcp.io/servers/benbalter-word-to-markdown/word-to-markdown