Quire PDF
NPM · QUIREPDF-MCP
Turn JSON into polished PDFs: invoices, receipts, quotes, certificates, or any data.
Available components
Last scanned (2 hours ago)
Scores higher than 58% 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 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 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 31 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 508 tokens (~101/item across 5 items; 5 tools + 0 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 Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 78% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 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.
- 30 Oct 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.
- 28 Oct 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.
- 26 Oct 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.
- 24 Oct 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.
- 22 Oct 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.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Analysed npm/quirepdf-mcp@0.2.0
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 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
get_template Get a template's fields ~50
Get a template's JSON Schema (required and optional fields) and a complete sample. Use the sample as a starting point for render_document.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Template name, e.g. invoice |
No output schema declared.
No examples provided.
get_usage Get render usage ~22
Current plan and renders used this month (requires QUIRE_API_KEY).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_templates List document templates ~33
List the built-in templates (invoice, receipt, quote, credit-note, statement, certificate, and the generic document layout).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
render_document Render a PDF document ~194
Render JSON data into a polished PDF (or a PNG preview of one page) and save it to disk. `template` is optional: omit it to auto-detect or use the generic layout. Returns the saved file path, the template used, and page count.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | The document content as a JSON object. |
| format | string | – | pdf (default) or png (one page, returned as an image too). |
| output_path | string | – | Where to save the file. Default: <template>-<timestamp>.pdf in the working directory. |
| page | integer | – | Page to render when format is png (default 1). |
| template | string | – | Template name from list_templates. Omit to auto-detect. |
| test | boolean | – | Free watermarked test render, not counted against the quota. Use while iterating on the data; omit for the final document. |
No output schema declared.
No examples provided.
validate_document Validate document data ~50
Check data against a template (or see which template would be auto-selected) without rendering. Free; lists every problem with its field path.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| template | string | – | – |
No output schema declared.
No examples provided.
How do I install the Quire PDF MCP server?
Quire PDF runs locally as an npm package, launched with npx -y quirepdf-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 · quirepdf-mcp
claude mcp add dev-quirepdf-quirepdf-mcp -- npx -y quirepdf-mcp
What is the Quire PDF MCP server?
Quire PDF is an MCP server listed in the public MCP registry as dev.quirepdf/quirepdf-mcp. Turn JSON into polished PDFs: invoices, receipts, quotes, certificates, or any data. This page covers its npm package (quirepdf-mcp).
Is the Quire PDF MCP server safe to use?
Quire PDF scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 Quire PDF MCP server expose?
Quire PDF exposes 5 tools: render_document, validate_document, list_templates, get_template, get_usage. Their descriptions and schemas cost roughly 349 tokens of context every time the server is loaded.
Is the Quire PDF MCP server still maintained?
Quire PDF is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Quire PDF MCP server under?
Quire PDF declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.