# dev.pdfops/pdfops-mcp (remote · pdfops.dev)

Deterministic PDF tools for AI agents: inspect fields, fill forms, merge PDFs, invoices.

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-22

## Components

- remote · `pdfops.dev`: 84/100 (this document), [markdown](https://verifymcp.io/servers/dev-pdfops-pdfops-mcp/api-mcp.md), [page](https://verifymcp.io/servers/dev-pdfops-pdfops-mcp/api-mcp)
- npm · `pdfops-mcp`: 94/100, [markdown](https://verifymcp.io/servers/dev-pdfops-pdfops-mcp/pdfops-mcp.md), [page](https://verifymcp.io/servers/dev-pdfops-pdfops-mcp/pdfops-mcp)

## Channel facts

- Endpoint: `https://pdfops.dev/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.6`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-22.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http dev-pdfops-pdfops-mcp 'https://pdfops.dev/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-pdfops-pdfops-mcp": {
      "url": "https://pdfops.dev/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-pdfops-pdfops-mcp": {
      "type": "http",
      "url": "https://pdfops.dev/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-pdfops-pdfops-mcp]
url = "https://pdfops.dev/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-pdfops-pdfops-mcp": {
      "type": "remote",
      "url": "https://pdfops.dev/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-pdfops-pdfops-mcp --url 'https://pdfops.dev/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-pdfops-pdfops-mcp:
    url: "https://pdfops.dev/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-pdfops-pdfops-mcp": {
      "Transport": "http",
      "Url": "https://pdfops.dev/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-pdfops-pdfops-mcp -t streamable-http -u 'https://pdfops.dev/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-pdfops-pdfops-mcp": {
      "type": "http",
      "url": "https://pdfops.dev/api/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-22 (score 84, +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.

### 2026-10-20 (score 83, +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.

### 2026-10-18 (score 82, +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.

### 2026-10-15 (score 81, +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.

### 2026-10-13 (score 80, +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.

### 2026-10-12 (score 79, +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.

### 2026-10-10 (score 78, +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.

### 2026-10-07 (score 77, +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.

## MCP tools (5)

### `pdf_inspect` (~146 tokens)

Inspect PDF form fields

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.

Input parameters:

- `pdf_path` (string, required): PDF source: an https:// URL or a data:application/pdf;base64,… URI (this hosted server cannot read local file paths).

Output parameters:

- `count` (integer): Number of form fields found; 0 when the PDF has no fillable form
- `fields` (array): One entry per form field, in document order
- `fillTemplate` (object): Field name to empty-or-current value, ready to edit and pass to pdf_fill
- `hasXFA` (boolean): True for hybrid AcroForm/XFA documents, whose XFA layer is dropped when filled
- `truncated` (boolean): True when the form exceeded an API enumeration cap; fields is then a prefix, not the full list

### `pdf_fill` (~196 tokens)

Fill PDF form

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).

Input parameters:

- `fields` (object, required): 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, required): Template PDF source: an https:// URL or a data:application/pdf;base64,… URI (this hosted server cannot read local file paths).

Output parameters:

- `bytes` (integer): Size of the produced PDF in bytes
- `resource_uri` (string): pdfops:// uri of the inline application/pdf resource

### `pdf_merge` (~148 tokens)

Merge PDFs

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.

Input parameters:

- `pdf_paths` (array, required): In order, each a PDF source: an https:// URL or a data:application/pdf;base64,… URI (this hosted server cannot read local file paths).

Output parameters:

- `bytes` (integer): Size of the produced PDF in bytes
- `resource_uri` (string): pdfops:// uri of the inline application/pdf resource

### `pdf_invoice` (~116 tokens)

Generate invoice PDF

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.

Input parameters:

- `invoice` (object, required): Invoice data

Output parameters:

- `bytes` (integer): Size of the produced PDF in bytes
- `resource_uri` (string): pdfops:// uri of the inline application/pdf resource

### `pdfops_usage` (~63 tokens)

Check PDFops quota

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.

Output parameters:

- `limit` (integer): Calls allowed in the current period
- `period` (string): Billing period the counts belong to, YYYY-MM
- `remaining` (integer)
- `resets_at` (string): ISO 8601 timestamp when used resets to 0
- `tier` (string): Plan name, e.g. free
- `used` (integer)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-pdfops-pdfops-mcp/api-mcp#diagnostics

## Score history

- 2026-10-22: 84
- 2026-10-21: 83
- 2026-10-20: 83
- 2026-10-19: 82
- 2026-10-18: 82
- 2026-10-17: 81
- 2026-10-16: 81
- 2026-10-15: 81
- 2026-10-14: 80
- 2026-10-13: 80
- 2026-10-12: 79
- 2026-10-10: 78
- 2026-10-07: 77
- 2026-10-06: 76
- 2026-10-04: 75
- 2026-10-03: 75
- 2026-10-02: 74
- 2026-10-01: 74
- 2026-09-30: 74

## Common questions

### 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.

## Links

- Remote endpoint: https://pdfops.dev/api/mcp
- Authorisation metadata: https://pdfops.dev/.well-known/oauth-protected-resource/api/mcp
- Repository: https://github.com/pdfops/pdfops-mcp
- Website: https://pdfops.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-pdfops-pdfops-mcp/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-pdfops-pdfops-mcp/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-pdfops-pdfops-mcp/api-mcp