PDFMakerAPI
REMOTE · API.PDFMAKERAPI.COM · 2 COMPONENTS · SCANNED SEP 20
Turn a description into a shareable, editable PDF — invoices, certificates, reports, resumes.
Available components
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety–
Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 4 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the PDFMakerAPI MCP server?
PDFMakerAPI is a hosted endpoint at https://api.pdfmakerapi.com/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 · api.pdfmakerapi.com
claude mcp add --transport http gerardobarrera-pdfmakerapi-mcp 'https://api.pdfmakerapi.com/mcp'
{
"mcpServers": {
"gerardobarrera-pdfmakerapi-mcp": {
"url": "https://api.pdfmakerapi.com/mcp"
}
}
} {
"servers": {
"gerardobarrera-pdfmakerapi-mcp": {
"type": "http",
"url": "https://api.pdfmakerapi.com/mcp"
}
}
} [mcp_servers.gerardobarrera-pdfmakerapi-mcp] url = "https://api.pdfmakerapi.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"gerardobarrera-pdfmakerapi-mcp": {
"type": "remote",
"url": "https://api.pdfmakerapi.com/mcp",
"enabled": true
}
}
} openclaw mcp add gerardobarrera-pdfmakerapi-mcp --url 'https://api.pdfmakerapi.com/mcp' --transport streamable-http
mcp_servers:
gerardobarrera-pdfmakerapi-mcp:
url: "https://api.pdfmakerapi.com/mcp" {
"McpServers": {
"gerardobarrera-pdfmakerapi-mcp": {
"Transport": "http",
"Url": "https://api.pdfmakerapi.com/mcp"
}
}
} assistant mcp add gerardobarrera-pdfmakerapi-mcp -t streamable-http -u 'https://api.pdfmakerapi.com/mcp'
{
"mcpServers": {
"gerardobarrera-pdfmakerapi-mcp": {
"type": "http",
"url": "https://api.pdfmakerapi.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 19 Aug 26 −10
The score moved with no change recorded against any check. We would rather say so than guess.
- 13 Aug 26 −10
The score moved with no change recorded against any check. We would rather say so than guess.
- 12 Aug 26 −11
The score moved with no change recorded against any check. We would rather say so than guess.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 −10
The score moved with no change recorded against any check. We would rather say so than guess.
- 9 Aug 26 −10
The score moved with no change recorded against any check. We would rather say so than guess.
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
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 19 Aug 2026 · Probed https://api.pdfmakerapi.com/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of api.pdfmakerapi.com. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| api.pdfmakerapi.com. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.pdfmakerapi.com/mcp | Unreachable | ||
| http (plaintext) | http://api.pdfmakerapi.com/mcp | HTTPS enforced |
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 →
create_document ~1,672
Create a professional, shareable PDF document — invoices, receipts, certificates, reports, resumes, letters. Returns a link that opens the document in the PDFMakerAPI editor to preview, edit any field, and download the PDF. Design a THOROUGH, realistic document (don't leave it sparse) that exactly follows this model, then pass it as `document`. DOCUMENT MODEL (PDFMakerAPI): Document: - id: string (short slug) - name: string - description: string (one short sentence) - pageSize: "letter" | "a4" | "legal" | "letter-landscape" | "a4-landscape" | "square" | "auto" (default "a4"; "auto" = letter width with the height growing to fit the content — use it for certificates/awards so there's no empty space below) - pageBackgroundColor: hex string (default "#ffffff") - margin: "none"|"sm"|"md"|"lg" // page margin (inset from the page edge); default "lg" - gap: "none"|"sm"|"md"|"lg" // vertical spacing between top-level sections; default to "lg" (most spacing) for an airy layout - variables: Variable[] // every {{placeholder}} you use MUST be declared here - children: Node[] // the document body, top to bottom Variable: { id, name (snake_case, used as {{name}}), label (human), type: "text"|"date"|"number"|"currency", defaultValue?: string } Node is one of (every node has: id, name, width: "full"|"1/2"|"1/3"|"1/4"|"2/3"|"3/4"|"auto", order: number, align?: "left"|"center"|"right", style?: NodeStyle): container: { type:"container", layout: { direction:"row"|"column", gap:"none"|"sm"|"md"|"lg", justify?:"start"|"center"|"end"|"between", alignItems?:"start"|"center"|"end"|"stretch" }, children: Node[] } text: { type:"text", content: string (supports \n, {{vars}}, and **inline bold** — wrap part of the text in double asterisks to bold just that part, e.g. "Total: **{{total}}**"), fontSize?:"xs"|"sm"|"base"|"lg"|"xl", fontWeight?:"normal"|"medium"|"semibold"|"bold" } table: { type:"table", columns: { id, name (data key), label (hea…
| Name | Type | Req | Description |
|---|---|---|---|
| document | object | yes | The PDFMakerAPI Document object to create, following the schema in this description. |
No output schema declared.
No examples provided.
What is the PDFMakerAPI MCP server?
PDFMakerAPI is an MCP server listed in the public MCP registry as io.github.GerardoBarrera/pdfmakerapi-mcp. Turn a description into a shareable, editable PDF, invoices, certificates, reports, resumes. This page covers its hosted endpoint (https://api.pdfmakerapi.com/mcp).
Is the PDFMakerAPI MCP server safe to use?
PDFMakerAPI scores 0 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 PDFMakerAPI MCP server expose?
PDFMakerAPI exposes 1 tool: create_document. Their descriptions and schemas cost roughly 1,672 tokens of context every time the server is loaded.
Does the PDFMakerAPI MCP server require authentication?
Its publisher declares no required credentials for PDFMakerAPI. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the PDFMakerAPI MCP server still maintained?
PDFMakerAPI has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 27 July 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.