io.github.rog0x/markdown
NPM · @ROG0X/MCP-MARKDOWN-TOOLS
Markdown TOC, lint, format, stats for AI agents
Available components
Last scanned (9 hours ago)
Scores higher than 84% of npm servers
Category Developer Tools
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
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 100 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 228 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 459 tokens (~91/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 +1
- Stability: 0.97 → pass security
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −2
- Stability: pass → 0.90 functional
- 22 Oct 26 +1
- Stability: 0.97 → pass security
- 20 Oct 26 −1
- Stability: pass → 0.93 functional
- 19 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 18 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 17 Oct 26 +3
- Stability: 0.80 → pass security
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 6 Nov 2026 · Analysed npm/@rog0x/mcp-markdown-tools@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 →
Dependencies 100 packages
| Packages resolved | 100 |
|---|---|
| Stale | 31 |
| 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 →
format_markdown ~118
Format and prettify markdown: normalize headings, fix spacing, align tables, wrap long lines
| Name | Type | Req | Description |
|---|---|---|---|
| alignTables | boolean | – | Align table columns with consistent padding |
| fixSpacing | boolean | – | Fix blank line spacing around headings and blocks |
| lineWidth | number | – | Maximum line width for wrapping (40-200) |
| markdown | string | yes | The markdown content to format |
| normalizeHeadings | boolean | – | Normalize heading style to ATX (# style) |
| wrapLines | boolean | – | Wrap long lines at word boundaries |
No output schema declared.
No examples provided.
generate_table ~135
Generate a formatted markdown table from JSON data with column selection, custom headers, and alignment options
| Name | Type | Req | Description |
|---|---|---|---|
| alignment | object | – | Alignment per column: 'left', 'center', or 'right'. Defaults to left. |
| columns | array | – | Column keys to include, in order. If omitted, all keys from the first row are used. |
| data | array | yes | Array of objects to render as a markdown table |
| defaultAlignment | string | – | Default alignment for columns not specified in the alignment map |
| headers | object | – | Custom header labels keyed by column name. If omitted, column keys are used as headers. |
No output schema declared.
No examples provided.
generate_toc ~94
Generate a table of contents from markdown headings with configurable depth and ordered/unordered style
| Name | Type | Req | Description |
|---|---|---|---|
| markdown | string | yes | The markdown content to generate a table of contents from |
| maxDepth | number | – | Maximum heading depth to include (1-6) |
| minDepth | number | – | Minimum heading depth to include (1-6) |
| ordered | boolean | – | Use ordered (numbered) list instead of unordered |
No output schema declared.
No examples provided.
lint_markdown ~45
Check markdown for common issues: broken link syntax, heading hierarchy, trailing spaces, missing alt text, inconsistent list markers
| Name | Type | Req | Description |
|---|---|---|---|
| markdown | string | yes | The markdown content to lint |
No output schema declared.
No examples provided.
markdown_stats ~67
Compute markdown statistics: word count, reading time, heading count, link count, image count, code block count, language distribution
| Name | Type | Req | Description |
|---|---|---|---|
| markdown | string | yes | The markdown content to analyze |
| wordsPerMinute | number | – | Reading speed for estimated reading time (100-400 WPM) |
No output schema declared.
No examples provided.
How do I install the io.github.rog0x/markdown MCP server?
io.github.rog0x/markdown runs locally as an npm package, launched with npx -y @rog0x/mcp-markdown-tools. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @rog0x/mcp-markdown-tools
claude mcp add rog0x-markdown -- npx -y @rog0x/mcp-markdown-tools
What is the io.github.rog0x/markdown MCP server?
io.github.rog0x/markdown is an MCP server listed in the public MCP registry as io.github.rog0x/markdown. Markdown TOC, lint, format, stats for AI agents. This page covers its npm package (@rog0x/mcp-markdown-tools).
Is the io.github.rog0x/markdown MCP server safe to use?
io.github.rog0x/markdown scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 November 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 io.github.rog0x/markdown MCP server expose?
io.github.rog0x/markdown exposes 5 tools: generate_toc, lint_markdown, format_markdown, markdown_stats, generate_table. Their descriptions and schemas cost roughly 459 tokens of context every time the server is loaded.
Is the io.github.rog0x/markdown MCP server still maintained?
io.github.rog0x/markdown is still listed as active in the MCP registry. We last reached this channel on 6 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 io.github.rog0x/markdown MCP server under?
io.github.rog0x/markdown declares the MIT 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 io.github.rog0x/markdown MCP server?
VerifyMCP ran 16 checks on io.github.rog0x/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.