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.

MintPDF

REMOTE · MINTPDF.DEV · 2 COMPONENTS · SCANNED SEP 20

Turn HTML or Markdown into a clean, styled PDF and get a download link.

0 this week 77 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 417 tokens (~208/item across 2 items; 2 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 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 2 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
Install

How do I install the MintPDF MCP server?

MintPDF is a hosted endpoint at https://mintpdf.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mintpdf.dev

# add to Claude Code
claude mcp add --transport http trendtweekers-mintpdf 'https://mintpdf.dev/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "trendtweekers-mintpdf": {
      "url": "https://mintpdf.dev/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "trendtweekers-mintpdf": {
      "type": "http",
      "url": "https://mintpdf.dev/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.trendtweekers-mintpdf]
url = "https://mintpdf.dev/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "trendtweekers-mintpdf": {
      "type": "remote",
      "url": "https://mintpdf.dev/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add trendtweekers-mintpdf --url 'https://mintpdf.dev/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  trendtweekers-mintpdf:
    url: "https://mintpdf.dev/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "trendtweekers-mintpdf": {
      "Transport": "http",
      "Url": "https://mintpdf.dev/mcp"
    }
  }
}
# add to Vellum
assistant mcp add trendtweekers-mintpdf -t streamable-http -u 'https://mintpdf.dev/mcp'
// mcp.json
{
  "mcpServers": {
    "trendtweekers-mintpdf": {
      "type": "http",
      "url": "https://mintpdf.dev/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 9 Sept 26 0
    • Stability: 0.97 → pass security
  • 8 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.

  • 5 Sept 26 +1

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

  • 3 Sept 26 +1

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

  • 1 Sept 26 +1

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

  • 30 Aug 26 +1

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

  • 28 Aug 26 +1

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

  • 26 Aug 26 +2
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 20 Sept 2026 · Probed https://mintpdf.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mintpdf.dev CN=YR2,O=Let's Encrypt,C=US 9 Aug 2026 7 Nov 2026 RSA 2048 SHA256-RSA 5188e57731f442ef73ff85508d0fe04164f
SANs: mintpdf.dev
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mintpdf.dev. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
mintpdf.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mintpdf.dev/mcp Verified 200
http (plaintext) http://mintpdf.dev/mcp HTTPS enforced 301 https://mintpdf.dev/mcp
MCP tools · 2 exposed · ~316 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
generate_pdf ~174

Renders HTML or Markdown into a PDF and returns a download URL (valid for 1 hour). Provide exactly one of `html` or `markdown`. Markdown gets a clean default stylesheet, so it is the fastest way to produce a good-looking document.

NameTypeReqDescription
footerTextstringSmall footer text on every page
formatstringPaper size, default A4
headerTextstringSmall header text on every page
htmlstringFull HTML document or fragment to render
landscapebooleanLandscape orientation, default false
marginstringPage margin on all sides, e.g. "18mm"
markdownstringMarkdown content to render with the default stylesheet
pageNumbersbooleanShow page numbers in the footer

No output schema declared.

No examples provided.

pdf_from_url ~142

Loads a public web page and renders it to PDF. Returns a download URL valid for 1 hour. Only public http/https URLs are allowed.

NameTypeReqDescription
footerTextstringSmall footer text on every page
formatstringPaper size, default A4
headerTextstringSmall header text on every page
landscapebooleanLandscape orientation, default false
marginstringPage margin on all sides, e.g. "18mm"
pageNumbersbooleanShow page numbers in the footer
urlstringyesPublic http(s) URL of the page to render

No output schema declared.

No examples provided.

Common questions

What is the MintPDF MCP server?

MintPDF is an MCP server listed in the public MCP registry as io.github.TrendTweekers/mintpdf. Turn HTML or Markdown into a clean, styled PDF and get a download link. This page covers its hosted endpoint (https://mintpdf.dev/mcp).

Is the MintPDF MCP server safe to use?

MintPDF scores 77 out of 100 on VerifyMCP. 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 MintPDF MCP server expose?

MintPDF exposes 2 tools: generate_pdf, pdf_from_url. Their descriptions and schemas cost roughly 316 tokens of context every time the server is loaded.

Does the MintPDF MCP server require authentication?

No. We connected to MintPDF without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the MintPDF MCP server still maintained?

MintPDF is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.