dev.pdfops/pdfops-mcp
REMOTE · PDFOPS.DEV · 2 COMPONENTS
Deterministic PDF tools for AI agents: inspect fields, fill forms, merge PDFs, invoices.
Available components
Last scanned (14 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 22 Oct 2026.
Category Documents and Files
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 723 tokens (~144/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 Management73
- Stability observed for 22 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 22 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.
- 20 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.
- 18 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.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 40. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 33. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 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 22 Oct 2026 · Probed https://pdfops.dev/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pdfops.dev | CN=YR2,O=Let's Encrypt,C=US | 14 Sept 2026 | 13 Dec 2026 | RSA 2048 | SHA256-RSA | 66f4258fe4715e8966eb548958082093cd8 |
| SANs: pdfops.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 pdfops.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| pdfops.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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | interest-cohort=(), browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pdfops.dev/api/mcp | Verified | 200 | |
| http (plaintext) | http://pdfops.dev/api/mcp | HTTPS enforced | 308 | https://pdfops.dev/api/mcp |
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 ~196
Fill AcroForm form fields in a PDF and 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. The source PDF is never modified. Returns the filled PDF inline as an application/pdf resource. 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 |
| pdf_path | string | yes | Template PDF source: an https:// URL or a data:application/pdf;base64,… URI (this hosted server cannot read local file paths). |
| Name | Type | Req | Description |
|---|---|---|---|
| bytes | integer | yes | Size of the produced PDF in bytes |
| resource_uri | string | – | pdfops:// uri of the inline application/pdf resource |
No examples provided.
pdf_inspect Inspect PDF form fields ~146
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 fillable form returns count 0. Read-only: the PDF is fetched but never modified. Call this FIRST when filling an unfamiliar PDF, since pdf_fill rejects unknown field names and over-length values.
| Name | Type | Req | Description |
|---|---|---|---|
| pdf_path | string | yes | PDF source: an https:// URL or a data:application/pdf;base64,… URI (this hosted server cannot read local file paths). |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Number of form fields found; 0 when the PDF has no fillable form |
| fields | array | yes | One entry per form field, in document order |
| fillTemplate | object | yes | Field name to empty-or-current value, ready to edit and pass to pdf_fill |
| hasXFA | boolean | yes | True for hybrid AcroForm/XFA documents, whose XFA layer is dropped when filled |
| truncated | boolean | yes | True when the form exceeded an API enumeration cap; fields is then a prefix, not the full list |
No examples provided.
pdf_invoice Generate invoice PDF ~116
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. Returns the invoice inline as an application/pdf resource. Use this when you have invoice DATA and no document; if you already have an invoice PDF or a fillable template to populate, use pdf_fill instead.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice | object | yes | Invoice data |
| Name | Type | Req | Description |
|---|---|---|---|
| bytes | integer | yes | Size of the produced PDF in bytes |
| resource_uri | string | – | pdfops:// uri of the inline application/pdf resource |
No examples provided.
pdf_merge Merge PDFs ~148
Merge two or more PDFs into one, in the order given, and return the result. Sources are read only and never modified. Returns the merged PDF inline as an application/pdf resource. This tool only concatenates whole documents: it does not reorder, rotate or delete pages within them, and it does not fill forms — use pdf_fill for a fillable form and pdf_invoice to build a document from data. An unreadable or rejected input fails with an error, so a partial merge is never returned.
| Name | Type | Req | Description |
|---|---|---|---|
| pdf_paths | array | yes | In order, each a PDF source: an https:// URL or a data:application/pdf;base64,… URI (this hosted server cannot read local file paths). |
| Name | Type | Req | Description |
|---|---|---|---|
| bytes | integer | yes | Size of the produced PDF in bytes |
| resource_uri | string | – | pdfops:// uri of the inline application/pdf resource |
No examples provided.
pdfops_usage Check PDFops quota ~63
Check the current PDFops API quota for the configured key: tier, limit, used, remaining, the billing period, and the reset timestamp. Read-only and safe to call before a batch to confirm there is headroom. Uses the API key this connection authenticated with.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | yes | Calls allowed in the current period |
| period | string | yes | Billing period the counts belong to, YYYY-MM |
| remaining | integer | yes | – |
| resets_at | string | yes | ISO 8601 timestamp when used resets to 0 |
| tier | string | yes | Plan name, e.g. free |
| used | integer | yes | – |
No examples provided.
How do I install the dev.pdfops/pdfops-mcp server?
dev.pdfops/pdfops-mcp is a hosted endpoint at https://pdfops.dev/api/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 · pdfops.dev
claude mcp add --transport http dev-pdfops-pdfops-mcp 'https://pdfops.dev/api/mcp'
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 hosted endpoint (https://pdfops.dev/api/mcp).
Is the dev.pdfops/pdfops-mcp server safe to use?
dev.pdfops/pdfops-mcp scores 84 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 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 669 tokens of context every time the server is loaded.
Does the dev.pdfops/pdfops-mcp server require authentication?
No. We connected to dev.pdfops/pdfops-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.