dev.pdfops/pdfops-mcp
NPM · PDFOPS-MCP · SCANNED SEP 21
Deterministic PDF tools for AI agents: inspect fields, fill forms, merge PDFs, invoices.
Available components
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 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pdfops/pdfops-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 12 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 681 tokens (~136/item across 5 items; 5 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 Management83
- Stability observed for 25 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 5 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
How do I install the dev.pdfops/pdfops-mcp server?
dev.pdfops/pdfops-mcp runs locally as an npm package, launched with npx -y pdfops-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 · pdfops-mcp
claude mcp add dev-pdfops-pdfops-mcp -- npx -y pdfops-mcp
{
"mcpServers": {
"dev-pdfops-pdfops-mcp": {
"command": "npx",
"args": [
"-y",
"pdfops-mcp"
]
}
}
} {
"servers": {
"dev-pdfops-pdfops-mcp": {
"command": "npx",
"args": [
"-y",
"pdfops-mcp"
]
}
}
} codex mcp add dev-pdfops-pdfops-mcp -- npx -y pdfops-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-pdfops-pdfops-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"pdfops-mcp"
],
"enabled": true
}
}
} openclaw mcp add dev-pdfops-pdfops-mcp --command npx --arg -y --arg pdfops-mcp
mcp_servers:
dev-pdfops-pdfops-mcp:
command: "npx"
args: ["-y", "pdfops-mcp"] {
"McpServers": {
"dev-pdfops-pdfops-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"pdfops-mcp"
]
}
}
} assistant mcp add dev-pdfops-pdfops-mcp -t stdio -c npx -a -y pdfops-mcp
{
"mcpServers": {
"dev-pdfops-pdfops-mcp": {
"command": "npx",
"args": [
"-y",
"pdfops-mcp"
]
}
}
} 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.
- 21 Sept 26 +1
- Package version: 0.2.0 → 0.3.1 functional
- 20 Sept 26 0
- Package version: 0.2.0 → 0.3.1 functional
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 17 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 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 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
- Package version: 0.2.0 → 0.3.1 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 21 Sept 2026 · Analysed npm/pdfops-mcp@0.3.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pdfops/pdfops-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pdfops/pdfops-mcp/.github/workflows/publish.yml@refs/tags/v0.3.1 |
| Rekor log index | 2735279636 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:6df7551761274800d2cec5d40d74459d01512f12c96aab4f30582c1ffe91c84891be53ca74ff947432b4264b3954f80888877a90ee9c9a8fef3b2d7a4 |
Background: How many MCP packages publish verified provenance →
Dependencies 97 packages
| Packages resolved | 97 |
|---|---|
| Stale | 31 |
| 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 →
pdf_fill Fill PDF form ~239
Fill AcroForm form fields in a PDF and save or return the result. Field names must exist in the PDF (use pdf_inspect first). All values are strings; checkboxes take "true"/"false"; dropdown/radio/optionlist values must be one of the field's options; text values must respect the field's maxLength from pdf_inspect. Encrypted PDFs are rejected with decrypt advice (common for government blanks with an empty user password).
| Name | Type | Req | Description |
|---|---|---|---|
| fields | object | yes | Field name → string value (from pdf_inspect's fillTemplate) |
| flatten | boolean | – | Bake values into page content and drop the AcroForm so fields are no longer editable |
| output_path | string | – | Absolute path to write the result. Omit when running remotely: the PDF is then returned inline as an application/pdf resource for the client to save. |
| pdf_path | string | yes | Template PDF source: an absolute file path, an https:// URL, or a data:application/pdf;base64,… URI. Use a URL or data URI when this server runs remotely (Smithery, hosted gateways) where local paths… |
No output schema declared.
No examples provided.
pdf_inspect Inspect PDF form fields ~166
List a PDF's AcroForm form fields — names, types, options, current values, per-field maxLength where declared — plus a paste-ready fillTemplate object for pdf_fill and a hasXFA flag (hybrid AcroForm/XFA inputs lose their XFA layer when filled). A PDF with no form returns count 0. Call this FIRST when filling an unfamiliar PDF: you cannot fill fields whose names you do not know, and values longer than a field's maxLength are rejected.
| Name | Type | Req | Description |
|---|---|---|---|
| pdf_path | string | yes | PDF source: an absolute file path, an https:// URL, or a data:application/pdf;base64,… URI. Use a URL or data URI when this server runs remotely (Smithery, hosted gateways) where local paths do not e… |
No output schema declared.
No examples provided.
pdf_invoice Generate invoice PDF ~112
Generate a complete, professionally laid-out invoice PDF from structured data — no template needed. Deterministic: the same input produces byte-identical output (safe to re-run). Note: without a paid PDFops key the output carries a small "Generated with pdfops.dev" footer line.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice | object | yes | Invoice data |
| output_path | string | – | Absolute path to write the result. Omit when running remotely: the PDF is then returned inline as an application/pdf resource for the client to save. |
No output schema declared.
No examples provided.
pdf_merge Merge PDFs ~126
Merge two or more PDFs into one, in the order given, and save or return the result.
| Name | Type | Req | Description |
|---|---|---|---|
| output_path | string | – | Absolute path to write the result. Omit when running remotely: the PDF is then returned inline as an application/pdf resource for the client to save. |
| pdf_paths | array | yes | In order, each a PDF source: an absolute file path, an https:// URL, or a data:application/pdf;base64,… URI. Use a URL or data URI when this server runs remotely (Smithery, hosted gateways) where loc… |
No output schema declared.
No examples provided.
pdfops_usage Check PDFops quota ~38
Check the current PDFops API quota for the configured key: tier, limit, used, remaining, reset date. Requires PDFOPS_API_KEY.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the dev.pdfops/pdfops-mcp server?
dev.pdfops/pdfops-mcp is listed in the public MCP registry as dev.pdfops/pdfops-mcp. Deterministic PDF tools for AI agents: inspect fields, fill forms, merge PDFs, invoices. This page covers its npm package (pdfops-mcp).
Is the dev.pdfops/pdfops-mcp server safe to use?
dev.pdfops/pdfops-mcp scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 dev.pdfops/pdfops-mcp server expose?
dev.pdfops/pdfops-mcp exposes 5 tools: pdf_inspect, pdf_fill, pdf_merge, pdf_invoice, pdfops_usage. Their descriptions and schemas cost roughly 681 tokens of context every time the server is loaded.
Is the dev.pdfops/pdfops-mcp server still maintained?
dev.pdfops/pdfops-mcp is still listed as active in the MCP registry. We last reached this channel on 21 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 dev.pdfops/pdfops-mcp server under?
dev.pdfops/pdfops-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.