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.

LoveMarkdown

NPM · LOVEMARKDOWN-MCP

Markdown ⇄ Word (.docx) and Markdown → LaTeX. Native Word equations (OMML) restored as LaTeX math.

Available components

70 Trust /100

Last scanned (22 hours ago)

Scores higher than 40% of npm 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 Security98
  • No malware found by supply-chain analysis.Pass
  • A known CVE affects sprintf-js, but no fixed version has been published, so there is nothing to upgrade to. View diagnostics → Partial
  • No install/post-install scripts declared.Pass
  • 56 of 169 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 334 tokens (~111/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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.

  • 22 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 21 Oct 26 55

    First indexed and scored.

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 22 Oct 2026 · Analysed npm/lovemarkdown-mcp@1.0.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-hp3w-g68c-fv3c CVE-2026-97058 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L no

Background: What a vulnerability scan can and cannot prove →

Dependencies 169 packages
Packages resolved 169
Stale 56
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~334 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
docx_to_markdown ~121

Convert a Word .docx file to clean Markdown. Headings, bold/italic, strikethrough, links, ordered/nested lists, code blocks, and blockquotes become Markdown; tables are kept as HTML. Native Word equations (OMML) are restored as LaTeX — inline $...$, display $$...$$. Optionally also writes the .md to disk.

NameTypeReqDescription
input_pathstringyesPath to the .docx file.
output_pathstring–Optional path to also write the Markdown result to.

No output schema declared.

No examples provided.

markdown_to_docx ~120

Convert Markdown to a styled Word .docx file. Supports headings (real Word heading styles), bullet/ordered/nested lists, tables, code blocks, blockquotes, links, and horizontal rules. LaTeX math in $...$ / $$...$$ degrades to readable Unicode text (no browser rendering in this environment). Writes the file to disk and reports the output path and size.

NameTypeReqDescription
markdownstringyesThe Markdown source text.
output_pathstringyesAbsolute or relative path for the .docx file to write.

No output schema declared.

No examples provided.

markdown_to_latex ~93

Convert Markdown to a complete, compilable LaTeX document (documentclass article, amsmath, listings, booktabs, hyperref). Headings become sections, code blocks become lstlisting environments, tables become tabular, math passes through for amsmath.

NameTypeReqDescription
markdownstringyesThe Markdown source text.
output_pathstring–Optional path to also write the .tex result to.

No output schema declared.

No examples provided.

Install

How do I install the LoveMarkdown MCP server?

LoveMarkdown runs locally as an npm package, launched with npx -y lovemarkdown-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · lovemarkdown-mcp

# add to Claude Code
claude mcp add coolnico-lovemarkdown-mcp -- npx -y lovemarkdown-mcp
Common questions

What is the LoveMarkdown MCP server?

LoveMarkdown is an MCP server listed in the public MCP registry as io.github.coolnico/lovemarkdown-mcp. Markdown ⇄ Word (.docx) and Markdown → LaTeX. Native Word equations (OMML) restored as LaTeX math. This page covers its npm package (lovemarkdown-mcp).

Is the LoveMarkdown MCP server safe to use?

LoveMarkdown scores 70 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 22 October 2026. It declares no install or post-install scripts. 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 LoveMarkdown MCP server expose?

LoveMarkdown exposes 3 tools: markdown_to_docx, docx_to_markdown, markdown_to_latex. Their descriptions and schemas cost roughly 334 tokens of context every time the server is loaded.

Is the LoveMarkdown MCP server still maintained?

LoveMarkdown is still listed as active in the MCP registry. We last reached this channel on 22 October 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 LoveMarkdown MCP server under?

LoveMarkdown declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.