RenderMark
NPM · @RENDERMARK/MCP-SERVER
Markdown to styled HTML, PDF, DOCX, and slides with themes, diagrams, and math.
Available components
Last scanned (20 hours ago)
Scores higher than 35% of npm servers
Category Documents and Files
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 Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.29.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 101 of 256 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 95 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability70
- 57% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1960 tokens (~98/item across 20 items; 17 tools + 3 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 Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "publish_to_rendermark" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 19 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
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.
- 30 Oct 26 0
- Stability: 0.97 → pass security
- 29 Oct 26 0
- CVE-2026-118663 affects this package: high ▼ security
- Stability: pass → 0.97 functional
- 28 Oct 26 0
- GHSA-f897-62hf-6gxq affects this package: high ▼ security
- 24 Oct 26 0
- CVE-2023-54404 affects this package: high ▼ security
- 23 Oct 26 0
- Stability: 0.97 → pass security
- 22 Oct 26 0
- Stability: pass → 0.97 functional
- 21 Oct 26 0
- CVE-2026-111771 affects this package: high ▼ security
- CVE-2026-111768 affects this package: high ▼ security
- CVE-2026-111769 affects this package: high ▼ security
- CVE-2026-111767 affects this package: high ▼ security
- 16 Oct 26 0
- Stability: 0.97 → 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 4 Nov 2026 · Analysed npm/@rendermark/mcp-server@0.1.10
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 9 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-rmxm-3fg6-px4f | CVE-2026-118663 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | yes |
| GHSA-22jm-h49p-29qw | CVE-2026-111767 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L | yes |
| GHSA-46jr-4wx8-v453 | CVE-2026-111768 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-6prh-2h8m-c8cw | CVE-2026-111769 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-6qxp-vccf-f47h | CVE-2026-104850 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-f897-62hf-6gxq | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-rvq5-wwqv-78pq | CVE-2026-111771 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-238p-pmpm-9mq7 | CVE-2026-103923 | low | yes | |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 256 packages
| Packages resolved | 256 |
|---|---|
| Stale | 100 |
| No linked repository | 1 |
| 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 →
delete_document ~65
Delete a document from RenderMark. This is destructive and cannot be undone. Only use when the user explicitly asks to remove a document.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | Must be true to confirm deletion |
| identifier | string | yes | Document slug, ID, or full RenderMark URL |
No output schema declared.
No examples provided.
export_batch ~132
Export multiple markdown files as a single merged document or individual exports. Combine docs/ folders into one PDF, DOCX, or HTML.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | – | List of markdown files to export |
| format | string | yes | Output format |
| glob | string | – | Glob pattern to match markdown files (e.g., 'docs/**/*.md') |
| mode | string | – | Merge into one document or zip individual exports (default: merged) |
| outputPath | string | – | Where to save the output file |
| theme | string | – | Theme name |
| title | string | – | Title for the merged document |
No output schema declared.
No examples provided.
export_markdown ~124
Export markdown to a file (PDF, DOCX, or HTML). Saves a markdown document as a downloadable file in a specific format.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | yes | Output format |
| github | object | – | – |
| markdown | string | yes | The markdown content to export |
| outputPath | string | – | Where to save the file. Defaults to current directory. |
| showToc | boolean | – | Include table of contents (default: true) |
| theme | string | – | Theme name |
| title | string | yes | Document title (used for filename and document header) |
No output schema declared.
No examples provided.
get_rendermark_instructions ~31
Retrieve RenderMark usage instructions, including capabilities, tool selection, workflows, and best practices.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_documents ~96
List the user's documents on RenderMark. Supports filtering by publish status, search by title, and pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default: 20, max: 100) |
| offset | integer | – | Pagination offset |
| published | boolean | – | Filter by publish status |
| search | string | – | Search by title (fuzzy match) |
| sortBy | string | – | Sort order (default: updated) |
No output schema declared.
No examples provided.
publish_to_google_docs ~69
Publish a markdown document as a Google Doc. Requires Google OAuth credentials in ~/.rendermark/config.json. Run `npx @rendermark/mcp-server auth google` to authenticate.
| Name | Type | Req | Description |
|---|---|---|---|
| markdown | string | yes | The markdown content to publish |
| title | string | yes | Document title |
No output schema declared.
No examples provided.
publish_to_rendermark ~57
Publish a markdown document to the authenticated RenderMark account and get a shareable link.
| Name | Type | Req | Description |
|---|---|---|---|
| markdown | string | yes | The markdown content to publish |
| options | object | – | – |
| title | string | yes | Document title |
No output schema declared.
No examples provided.
read_document ~47
Retrieve a document from RenderMark by URL, slug, or ID. Returns the raw markdown content and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Document slug, ID, or full RenderMark URL |
No output schema declared.
No examples provided.
render_diff ~104
Generate a visual diff (redline) between two versions of a markdown document. Additions highlighted in green, deletions in red with strikethrough.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | yes | The revised markdown content |
| before | string | yes | The original markdown content |
| mode | string | – | Diff display mode (default: inline) |
| outputFormat | string | – | Return as HTML string or rendered image (default: html) |
| title | string | – | Document title |
No output schema declared.
No examples provided.
render_markdown ~155
Convert markdown to styled HTML. Returns a professional, styled HTML document with syntax highlighting, table of contents, and GitHub-flavored markdown support.
| Name | Type | Req | Description |
|---|---|---|---|
| github | object | – | GitHub context for resolving relative image paths |
| markdown | string | yes | The markdown content to render |
| showToc | boolean | – | Include table of contents (default: true) |
| template | string | – | Template: report, meeting-notes, memo, letter, slides, changelog |
| theme | string | – | Theme: default, dark, serif, minimal |
| title | string | – | Document title |
| unsanitized | boolean | – | Return unsanitized HTML (default: false, HTML is sanitized for safe embedding) |
No output schema declared.
No examples provided.
render_to_image ~146
Render markdown as a PNG or JPEG image. Use when sharing a visual preview in chat (Telegram, Discord, Slack) where HTML can't be sent directly.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Image format (default: png) |
| markdown | string | yes | The markdown content to render |
| quality | integer | – | JPEG quality 1-100 (default: 90) |
| section | string | – | Render only a specific heading section |
| theme | string | – | Theme name (default, dark, serif, minimal) |
| title | string | – | Document title |
| width | integer | – | Viewport width in pixels (default: 1200, max: 2400) |
No output schema declared.
No examples provided.
setup_api_key ~58
Set up a RenderMark API key by opening the user's browser to sign in and generate a key. The key is automatically saved to ~/.rendermark/config.json. Use this when the user needs to authenticate with RenderMark for the first time.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
share_document ~96
Share a RenderMark document with specific people via email. Sets email-restricted protection and grants access to the specified addresses.
| Name | Type | Req | Description |
|---|---|---|---|
| emails | array | yes | Email addresses to grant access (1-50) |
| identifier | string | yes | Document slug, ID, or full RenderMark URL |
| message | string | – | Optional message to include in the share notification |
| notify | boolean | – | Send email notification to recipients (default: true) |
No output schema declared.
No examples provided.
share_live_preview ~79
Create a temporary shareable URL for a markdown document preview. The URL expires after the specified duration.
| Name | Type | Req | Description |
|---|---|---|---|
| expiresIn | string | – | How long the link stays active (default: 24h) |
| markdown | string | yes | The markdown content to share |
| theme | string | – | Theme name |
| title | string | – | Document title |
No output schema declared.
No examples provided.
sync_from_github ~136
Sync a markdown file from a GitHub repository to RenderMark. Creates a new document or updates an existing one linked to the GitHub source.
| Name | Type | Req | Description |
|---|---|---|---|
| autoSync | boolean | – | Enable automatic sync via webhook (default: false) |
| branch | string | – | Branch name (default: main) |
| owner | string | yes | GitHub repository owner |
| path | string | yes | Path to the markdown file (e.g., 'docs/README.md') |
| publish | boolean | – | Publish the document immediately (default: true) |
| repo | string | yes | GitHub repository name |
| title | string | – | Override title |
No output schema declared.
No examples provided.
update_document ~88
Update an existing document on RenderMark. Can update markdown content, title, publishing settings, or protection.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Document slug, ID, or full RenderMark URL |
| markdown | string | – | New markdown content (replaces entire document) |
| options | object | – | – |
| publish | boolean | – | Set publish state |
| title | string | – | New document title |
No output schema declared.
No examples provided.
validate_markdown ~72
Validate markdown for common issues: broken links, missing images, malformed tables, unclosed formatting, heading structure.
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | – | Which checks to run (default: all) |
| filePath | string | – | File path for resolving relative links |
| markdown | string | yes | The markdown content to validate |
No output schema declared.
No examples provided.
How do I install the RenderMark MCP server?
RenderMark runs locally as an npm package, launched with npx -y @rendermark/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @rendermark/mcp-server
claude mcp add jmsaavedra-rendermark -- npx -y @rendermark/mcp-server
What is the RenderMark MCP server?
RenderMark is an MCP server listed in the public MCP registry as io.github.jmsaavedra/rendermark. Markdown to styled HTML, PDF, DOCX, and slides with themes, diagrams, and math. This page covers its npm package (@rendermark/mcp-server).
Is the RenderMark MCP server safe to use?
RenderMark scores 68 out of 100 on VerifyMCP. We recorded 9 known advisories against it as of 4 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 RenderMark MCP server expose?
RenderMark exposes 17 tools: render_markdown, render_to_image, render_diff, export_markdown, export_batch, and 12 more. Their descriptions and schemas cost roughly 1,555 tokens of context every time the server is loaded.
Is the RenderMark MCP server still maintained?
RenderMark is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.