io.github.drsound/markdown-to-whatsapp
NPM · MARKDOWN-TO-WHATSAPP · SCANNED SEP 20
Convert Markdown into WhatsApp formatting: tables drawn to fit the phone's monospace width.
Available components
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 4 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to drsound/markdown-to-whatsapp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 25 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 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 1 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
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.
npm · markdown-to-whatsapp
claude mcp add drsound-markdown-to-whatsapp -- npx -y markdown-to-whatsapp
{
"mcpServers": {
"drsound-markdown-to-whatsapp": {
"command": "npx",
"args": [
"-y",
"markdown-to-whatsapp"
]
}
}
} {
"servers": {
"drsound-markdown-to-whatsapp": {
"command": "npx",
"args": [
"-y",
"markdown-to-whatsapp"
]
}
}
} codex mcp add drsound-markdown-to-whatsapp -- npx -y markdown-to-whatsapp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"drsound-markdown-to-whatsapp": {
"type": "local",
"command": [
"npx",
"-y",
"markdown-to-whatsapp"
],
"enabled": true
}
}
} openclaw mcp add drsound-markdown-to-whatsapp --command npx --arg -y --arg markdown-to-whatsapp
mcp_servers:
drsound-markdown-to-whatsapp:
command: "npx"
args: ["-y", "markdown-to-whatsapp"] {
"McpServers": {
"drsound-markdown-to-whatsapp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"markdown-to-whatsapp"
]
}
}
} assistant mcp add drsound-markdown-to-whatsapp -t stdio -c npx -a -y markdown-to-whatsapp
{
"mcpServers": {
"drsound-markdown-to-whatsapp": {
"command": "npx",
"args": [
"-y",
"markdown-to-whatsapp"
]
}
}
} 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.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 13 Sept 26 +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.
- 11 Sept 26 +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.
- 9 Sept 26 +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.
- 6 Sept 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.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Analysed npm/markdown-to-whatsapp@1.0.3
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 | drsound/markdown-to-whatsapp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/drsound/markdown-to-whatsapp/.github/workflows/release.yml@refs/tags/v1.0.3 |
| Rekor log index | 2582930027 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:29c7c88bd56076a6767c131761b5acf58233d9849e21c96116f220b6fc1bd60c15fbfebe3d790b3e3f050ea02e63a21e96891f6d2187cbb5b501cf90a |
Background: How many MCP packages publish verified provenance →
Dependencies 4 packages
| Packages resolved | 4 |
|---|---|
| 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_markdown_to_whatsapp Convert Markdown to WhatsApp ~369
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| tables | array | yes | One entry per table in the document, in order |
| text | string | yes | The WhatsApp-formatted message |
No examples provided.
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 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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 20 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.