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.

FileToPDF

NPM · FILETOPDF-MCP · 2 COMPONENTS · SCANNED SEP 22

Convert files, HTML, and Markdown to PDF via the FileToPDF API. Bring your own API key.

Available components

remote · api.filetopdf.dev 80 npm · filetopdf-mcp 82
0 this week 82 Trust /100
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
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1224 tokens (~306/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 Management97
  • Stability observed for 29 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
Install

How do I install the FileToPDF MCP server?

FileToPDF runs locally as an npm package, launched with npx -y filetopdf-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 · filetopdf-mcp

# add to Claude Code
claude mcp add dev-filetopdf-filetopdf-mcp -- npx -y filetopdf-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "dev-filetopdf-filetopdf-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "filetopdf-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dev-filetopdf-filetopdf-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "filetopdf-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add dev-filetopdf-filetopdf-mcp -- npx -y filetopdf-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-filetopdf-filetopdf-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "filetopdf-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dev-filetopdf-filetopdf-mcp --command npx --arg -y --arg filetopdf-mcp
# ~/.hermes/config.yaml
mcp_servers:
  dev-filetopdf-filetopdf-mcp:
    command: "npx"
    args: ["-y", "filetopdf-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dev-filetopdf-filetopdf-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "filetopdf-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add dev-filetopdf-filetopdf-mcp -t stdio -c npx -a -y filetopdf-mcp
// mcp.json
{
  "mcpServers": {
    "dev-filetopdf-filetopdf-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "filetopdf-mcp"
      ]
    }
  }
}
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 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 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.

  • 18 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.

  • 17 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 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 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.

  • 11 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.

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 Sept 2026 · Analysed npm/filetopdf-mcp@0.1.1

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 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~1,224 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
convert_file ~307

Convert a document at a public URL into a PDF. Handles Office documents (DOCX, XLSX, PPTX, ODT, RTF, TXT, CSV…), images (PNG, JPG, WebP…), web pages/HTML files, Markdown files, and existing PDFs (passthrough) — the conversion engine is auto-detected from the file extension. Use this when the source lives at a URL; for raw HTML or Markdown strings use convert_html / convert_markdown instead. Returns the PDF as an embedded application/pdf resource (optionally also written to disk via save_path). Costs 1 credit on success; failed conversions are free.

NameTypeReqDescription
landscapeboolean–Render in landscape orientation. (Pro/Scale/trial only.)
nativePageRangesstring–Page ranges to include, e.g. "1-3".
ownerPasswordstring–Owner password controlling permissions on the resulting PDF.
passwordstring–Password to open a protected source document.
pdfastring–PDF/A conformance level, e.g. "PDF/A-2b". (Pro/Scale/trial only.)
pdfuaboolean–Produce an accessible PDF/UA document.
save_pathstring–Optional absolute path to also write the PDF to on disk.
urlstringyesPublic http(s) URL of the file to download and convert.
userPasswordstring–Password required to open the resulting PDF.

No output schema declared.

No examples provided.

convert_html ~413

Render a raw HTML string into a pixel-perfect PDF with a real Chromium engine — ideal for generating invoices, reports, receipts, certificates, letters, and other documents from templates. Optional css is injected into the document <head>; full layout control via paper size, margins, landscape, scale, page ranges, background printing, PDF/A archival conformance, and password protection. Returns the PDF as an embedded application/pdf resource (optionally also written to disk via save_path). Costs 1 credit on success; failed conversions are free.

NameTypeReqDescription
cssstring–Optional CSS, injected into the document <head>.
htmlstringyesThe HTML markup to render.
landscapeboolean–Render in landscape orientation. (Pro/Scale/trial only.)
marginBottomstring–Bottom margin in inches.
marginLeftstring–Left margin in inches.
marginRightstring–Right margin in inches.
marginTopstring–Top margin in inches.
nativePageRangesstring–Page ranges to include, e.g. "1-3,5".
ownerPasswordstring–Owner password controlling permissions on the resulting PDF.
paperHeightstring–Paper height in inches.
paperWidthstring–Paper width in inches, or with a unit e.g. "210mm".
pdfastring–PDF/A conformance level, e.g. "PDF/A-2b". (Pro/Scale/trial only.)
pdfuaboolean–Produce an accessible PDF/UA document.
preferCssPageSizeboolean–Use the page size declared in CSS @page rules.
printBackgroundboolean–Print background graphics/colors.
save_pathstring–Optional absolute path to also write the PDF to on disk.
scalestring–Render scale, 0.1–2.0.
userPasswordstring–Password required to open the resulting PDF.

No output schema declared.

No examples provided.

convert_markdown ~420

Render a Markdown string into a clean, professional PDF — the fastest way to turn notes, reports, documentation, summaries, or any agent-written text into a shareable document. A sensible default stylesheet is applied when no css is given; pass custom CSS to fully control typography and branding, plus layout options (paper size, margins, landscape, page ranges, PDF/A, passwords). Returns the PDF as an embedded application/pdf resource (optionally also written to disk via save_path). Costs 1 credit on success; failed conversions are free.

NameTypeReqDescription
cssstring–Optional CSS to style the rendered Markdown (overrides the default stylesheet).
landscapeboolean–Render in landscape orientation. (Pro/Scale/trial only.)
marginBottomstring–Bottom margin in inches.
marginLeftstring–Left margin in inches.
marginRightstring–Right margin in inches.
marginTopstring–Top margin in inches.
markdownstringyesThe Markdown content to render.
nativePageRangesstring–Page ranges to include, e.g. "1-3,5".
ownerPasswordstring–Owner password controlling permissions on the resulting PDF.
paperHeightstring–Paper height in inches.
paperWidthstring–Paper width in inches, or with a unit e.g. "210mm".
pdfastring–PDF/A conformance level, e.g. "PDF/A-2b". (Pro/Scale/trial only.)
pdfuaboolean–Produce an accessible PDF/UA document.
preferCssPageSizeboolean–Use the page size declared in CSS @page rules.
printBackgroundboolean–Print background graphics/colors.
save_pathstring–Optional absolute path to also write the PDF to on disk.
scalestring–Render scale, 0.1–2.0.
userPasswordstring–Password required to open the resulting PDF.

No output schema declared.

No examples provided.

get_account ~84

Check the FileToPDF connection and return the plan, remaining conversion credits, and subscription status. Free — never costs credits. Call it to verify the API key works, or after a failed conversion to see whether credits ran out. No API key yet? Anyone can get one free, in one click, at https://filetopdf.dev (10 free conversions, no signup).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the FileToPDF MCP server?

FileToPDF is an MCP server listed in the public MCP registry as dev.filetopdf/filetopdf-mcp. Convert files, HTML, and Markdown to PDF via the FileToPDF API. Bring your own API key. This page covers its npm package (filetopdf-mcp).

Is the FileToPDF MCP server safe to use?

FileToPDF scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 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 FileToPDF MCP server expose?

FileToPDF exposes 4 tools: get_account, convert_file, convert_html, convert_markdown. Their descriptions and schemas cost roughly 1,224 tokens of context every time the server is loaded.

Is the FileToPDF MCP server still maintained?

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

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