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.

io.github.cyanheads/docgen-mcp-server

NPM · @CYANHEADS/DOCGEN-MCP-SERVER · SCANNED AUG 7

Render HTML/markdown to PDF, export rows to xlsx, and fill AcroForm PDFs.

Available components

npm · @cyanheads/docgen-mcp-server 64
+59 this week 64 Trust /100
Trust breakdown (6 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 →

Supply Chain Security88
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects uuid 8.3.2, reached via exceljs > uuid. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 98 of 212 dependencies flagged as unhealthy (6 deprecated). 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 (Apache-2.0).Pass
  • Actively maintained (last published 39 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability66
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 837 tokens (~209/item across 4 items; 4 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 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.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.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @cyanheads/docgen-mcp-server

# add to Claude Code
claude mcp add cyanheads-docgen-mcp-server -- npx -y @cyanheads/docgen-mcp-server
# add to Codex CLI
codex mcp add cyanheads-docgen-mcp-server -- npx -y @cyanheads/docgen-mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cyanheads-docgen-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@cyanheads/docgen-mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add cyanheads-docgen-mcp-server --command npx --arg -y --arg @cyanheads/docgen-mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  cyanheads-docgen-mcp-server:
    command: "npx"
    args: ["-y", "@cyanheads/docgen-mcp-server"]
// mcp.json
{
  "mcpServers": {
    "cyanheads-docgen-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@cyanheads/docgen-mcp-server"
      ]
    }
  }
}
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.

  • 7 Aug 26 +3
    • Security disclosure: fail → unverified ▼ functional
    • Dependency health: partial → 0.77 functional
  • 6 Aug 26 +28
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • MCP protocol: unverified → pass ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Tool coverage: 100 functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
    • First check of Tool coverage: 100 functional
    • First check of Schema quality: fail functional
  • 5 Aug 26 0
    • CVE-2026-69207 no longer affects this package ▲ security
  • 4 Aug 26 0
    • CVE-2026-69207 affects this package: high ▼ security
  • 2 Aug 26 +28
    • CVE-2026-41907 affects this package: high ▼ security
    • Provenance: unverified → fail ▼ security
    • Known CVEs: unverified → fail ▼ security
    • Install scripts: unverified → pass ▲ security
    • Malware scan: unverified → pass ▲ security
    • Dependency health: unverified → partial ▲ functional
    • License: unverified → pass ▲ functional
    • Maintenance: unverified → pass ▲ functional
    • Licence: Apache-2.0 functional
  • 1 Aug 26 0
    • Stability: Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare. security
    • Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
    • Capabilities: Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake. functional
    • Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
  • 31 Jul 26 −19
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
    • Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
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 7 Aug 2026 · Analysed npm/@cyanheads/[email protected]

Provenance No attestation

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

Result No attestation
Ecosystem npm
Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-w5hq-g745-h8pq CVE-2026-41907 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes
Dependencies 212 packages
Packages resolved 212
Deprecated 6
Stale 95
Tree resolution Complete
MCP tools · 4 exposed · ~745 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.

Tool Tokens
docgen_export_spreadsheet ~144

Render one or more named worksheets of row objects to a downloadable .xlsx workbook. Each sheet is a name plus an array of row objects (property → scalar), with an optional column spec controlling header label, value type, width, and number/date format. An empty rows array yields a header-only sheet; provide at least one sheet. Returns a delivery envelope with a documentId, resource URI, sheetCount, byte size, and inline base64 when small enough. The natural export stage for tabular data pulled from another server — reshape its rows into sheets[] and render.

NameTypeReqDescription
sheetsarrayyesOne or more named worksheets to render into the workbook.
NameTypeReqDescription
documentobjectyesDelivery envelope for a rendered document — metadata plus resource/inline byte access.
enginestringyesThe rendering engine that produced the workbook.

No examples provided.

docgen_fill_form ~248

Fill the AcroForm fields of a supplied PDF and optionally flatten it. Provide the source PDF as exactly one of { base64 } or { url } (an https URL fetched behind an SSRF guard; base64 avoids any fetch), plus a fields map of AcroForm field name → value. Field names must match the PDF internal names exactly (case-sensitive); obtain them from whoever supplied the form, since docgen does not expose them. Names with no AcroForm counterpart come back in unmatchedFields[] rather than failing — correct them and re-render. Set flatten to bake the values in so the result is no longer editable. Returns a delivery envelope with a documentId, resource URI, pageCount, and inline base64 when small enough.

NameTypeReqDescription
fieldsobjectyesAcroForm field name → value. Names must match the PDF internal field names exactly (case-sensitive). Unmatched names are returned in unmatchedFields[].
flattenboolean–When true, flatten the form after filling so values are baked in and no longer editable.
sourcePdfobjectyesThe fillable PDF source — provide exactly ONE of { base64 } or { url }.
NameTypeReqDescription
documentobjectyesDelivery envelope for a rendered document — metadata plus resource/inline byte access.
unmatchedFieldsarrayyesField names from the input map that had no matching AcroForm field. Empty when every field matched. Correct these and re-render to fill them.

No examples provided.

docgen_get_document ~166

Re-fetch a previously rendered document by the id a docgen render/export/fill tool returned. Returns the same delivery envelope (metadata plus resource URI, and inline base64 when small enough). Use it to recover a document whose inline copy was dropped (over the inline size limit) while it is still within its TTL. The documentId is obtainable ONLY from an earlier docgen_render_pdf, docgen_export_spreadsheet, or docgen_fill_form result — it is not guessable, and an expired or unknown id returns document_expired.

NameTypeReqDescription
documentIdstringyesThe opaque document id returned by an earlier docgen_render_pdf, docgen_export_spreadsheet, or docgen_fill_form call. Format `doc_` followed by 24 url-safe characters.
NameTypeReqDescription
documentobjectyesDelivery envelope for a rendered document — metadata plus resource/inline byte access.

No examples provided.

docgen_render_pdf ~187

Render content to a downloadable PDF document. Provide exactly one source: { html } (raw HTML you compose — the recommended path), { markdown } (converted to HTML then rendered), or { template, data } (a {{key}} template filled from a data object, server-owned layout). Control page size, orientation, margins, header/footer, and page numbers via pageOptions. Returns a delivery envelope with a documentId, resource URI, pageCount, byte size, and inline base64 when small enough. The lightweight engine renders structured layout (headings, paragraphs, lists, tables) but not arbitrary CSS — a degraded flag is set when unsupported styling is dropped.

NameTypeReqDescription
pageOptionsobject–Page layout options; sensible defaults apply.
sourceobjectyesThe document source — provide exactly ONE of: { html }, { markdown }, or { template, data }.
NameTypeReqDescription
degradedbooleanyesTrue when the lightweight engine dropped unsupported styling (CSS, images, scripts).
documentobjectyesDelivery envelope for a rendered document — metadata plus resource/inline byte access.
enginestringyesThe PDF rendering engine that produced the document.

No examples provided.