# io.github.drsound/markdown-to-whatsapp (npm · markdown-to-whatsapp)

Convert Markdown into WhatsApp formatting: tables drawn to fit the phone's monospace width.

- Trust score: 94/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- npm · `markdown-to-whatsapp`: 94/100 (this document), [markdown](https://verifymcp.io/servers/drsound-markdown-to-whatsapp/markdown-to-whatsapp.md), [page](https://verifymcp.io/servers/drsound-markdown-to-whatsapp/markdown-to-whatsapp)

## Channel facts

- Registry: `npm`
- Package: `markdown-to-whatsapp`
- Version: `1.0.3`
- 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-09-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 0 of 4 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to drsound/markdown-to-whatsapp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 26 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 369 tokens (~369/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**: 97/100
  - Stability observed for 29 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 1 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 io.github.drsound/markdown-to-whatsapp MCP server?

io.github.drsound/markdown-to-whatsapp runs locally as an npm package, launched with npx -y markdown-to-whatsapp. 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 drsound-markdown-to-whatsapp -- npx -y markdown-to-whatsapp
```

### Cursor

```json
{
  "mcpServers": {
    "drsound-markdown-to-whatsapp": {
      "command": "npx",
      "args": [
        "-y",
        "markdown-to-whatsapp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "drsound-markdown-to-whatsapp": {
      "command": "npx",
      "args": [
        "-y",
        "markdown-to-whatsapp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add drsound-markdown-to-whatsapp -- npx -y markdown-to-whatsapp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add drsound-markdown-to-whatsapp --command npx --arg -y --arg markdown-to-whatsapp
```

### Hermes

```yaml
mcp_servers:
  drsound-markdown-to-whatsapp:
    command: "npx"
    args: ["-y", "markdown-to-whatsapp"]
```

### Netclaw

```json
{
  "McpServers": {
    "drsound-markdown-to-whatsapp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "markdown-to-whatsapp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add drsound-markdown-to-whatsapp -t stdio -c npx -a -y markdown-to-whatsapp
```

### Other

```json
{
  "mcpServers": {
    "drsound-markdown-to-whatsapp": {
      "command": "npx",
      "args": [
        "-y",
        "markdown-to-whatsapp"
      ]
    }
  }
}
```

## 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-09-21 (score 94, +1)

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

### 2026-09-19 (score 93, +1)

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

### 2026-09-17 (score 92, +1)

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

### 2026-09-15 (score 91, +1)

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

### 2026-09-13 (score 90, +1)

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

### 2026-09-11 (score 89, +1)

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

### 2026-09-09 (score 88, +1)

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

### 2026-09-06 (score 87, +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.

## MCP tools (1)

### `convert_markdown_to_whatsapp` (~369 tokens)

Convert Markdown to WhatsApp

Convert Markdown into the formatting WhatsApp renders (*bold*, _italic_, ~strike~, `code`, lists, quotes), ready to paste or send.
Use it instead of hand-writing WhatsApp syntax whenever the text has tables, nested lists, headings or inline formatting next to punctuation.
It applies WhatsApp's real rules: markers only on word boundaries, escapes that WhatsApp does not interpret, no mid-word formatting.
Each table is drawn as a monospace box sized to the reader's phone, degrading in this order: cell padding removed, then borders, then cells word-wrapped. It becomes a bulleted list only when no box fits.
Counting columns against a 26-character bubble is exactly what this tool does and a model does not.

Input parameters:

- `headingEmojis` (boolean): Prefix headings with a level emoji (📌 🟠 🟡 …) before the bold text. Default true.
- `listLayout` (string): How a table reads when it is a list: rows (one group per row), columns (one group per column, for comparison matrices), pairs (bare "key: value" lines, two columns only). auto guesses from the header…
- `markdown` (string, required): The Markdown text to convert
- `monoWidth` (integer): Monospace characters that fit on one line of the reader's WhatsApp bubble; about 26 on a 360 px phone (default 26). Tables are drawn to fit this width.
- `rowSeparator` (boolean): Draw a rule between table rows. Always drawn when a row wraps. Default false.
- `tableFormat` (string): auto: a drawn table when it fits monoWidth, a bulleted list otherwise. list: always a bulleted list. Default auto.

Output parameters:

- `tables` (array): One entry per table in the document, in order
- `text` (string): The WhatsApp-formatted message

## Diagnostics

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

## Score history

- 2026-09-21: 94
- 2026-09-20: 93
- 2026-09-19: 93
- 2026-09-18: 92
- 2026-09-17: 92
- 2026-09-16: 91
- 2026-09-15: 91
- 2026-09-14: 90
- 2026-09-13: 90
- 2026-09-12: 89
- 2026-09-11: 89
- 2026-09-10: 88
- 2026-09-09: 88
- 2026-09-08: 87
- 2026-09-07: 87
- 2026-09-06: 87
- 2026-09-05: 86
- 2026-09-04: 86
- 2026-09-03: 85
- 2026-09-02: 85
- 2026-09-01: 84
- 2026-08-31: 84
- 2026-08-30: 83
- 2026-08-29: 83
- 2026-08-28: 82
- 2026-08-27: 82
- 2026-08-26: 81
- 2026-08-25: 68
- 2026-08-24: 79
- 2026-08-23: 64

## Common questions

### What is the io.github.drsound/markdown-to-whatsapp MCP server?

io.github.drsound/markdown-to-whatsapp is an MCP server listed in the public MCP registry as io.github.drsound/markdown-to-whatsapp. Convert Markdown into WhatsApp formatting: tables drawn to fit the phone's monospace width. This page covers its npm package (markdown-to-whatsapp).

### Is the io.github.drsound/markdown-to-whatsapp MCP server safe to use?

io.github.drsound/markdown-to-whatsapp scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 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 io.github.drsound/markdown-to-whatsapp MCP server expose?

io.github.drsound/markdown-to-whatsapp exposes 1 tool: convert_markdown_to_whatsapp. Their descriptions and schemas cost roughly 369 tokens of context every time the server is loaded.

### Is the io.github.drsound/markdown-to-whatsapp MCP server still maintained?

io.github.drsound/markdown-to-whatsapp is still listed as active in the MCP registry. We last reached this channel on 21 September 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 io.github.drsound/markdown-to-whatsapp MCP server under?

io.github.drsound/markdown-to-whatsapp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/markdown-to-whatsapp
- Socket report: https://socket.dev/npm/package/markdown-to-whatsapp
- Repository: https://github.com/drsound/markdown-to-whatsapp
- Website: https://drsound.github.io/markdown-to-whatsapp/
- Changelog RSS feed: https://verifymcp.io/servers/drsound-markdown-to-whatsapp/markdown-to-whatsapp.xml
- Changelog JSON feed: https://verifymcp.io/servers/drsound-markdown-to-whatsapp/markdown-to-whatsapp.json
- HTML version of this page: https://verifymcp.io/servers/drsound-markdown-to-whatsapp/markdown-to-whatsapp