oxidize-pdf MCP Server
PYPI · OXIDIZE-PDF
MCP server for PDF generation, parsing, splitting, merging, and manipulation via oxidize-pdf
Available components
Last scanned (16 hours ago)
Scores higher than 82% of PyPI 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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs maturin at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to bzsanti/oxidize-python). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3044 tokens (~179/item across 17 items; 12 tools + 5 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 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
Checks we ran (15)
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 20 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 19 Nov 26 −16
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.97 functional
- 18 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 17 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 13 Nov 26 +1
- Stability: 0.97 → pass security
- 12 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 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 21 Nov 2026 · Analysed pypi/oxidize-pdf@0.23.0
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 | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | bzsanti/oxidize-python |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/bzsanti/oxidize-python/.github/workflows/release.yml@refs/tags/v0.23.0 |
| Rekor log index | 3463820991 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:6954727e2fab47d725ffa404ae43bc02ed381e378cc8b78ddb6e793e8b53b2e7 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | maturin |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
add_pdf_content Add content to a PDF session ~294
Append text or a new page to an open create_pdf session (step 2 of 3). Mutates the in-memory session; nothing is written to disk until save_pdf. Returns JSON {status, session_id, page_count} on success, or {error, code} if the session is missing/inactive or required text fields are absent. Coordinates use PDF points with the origin at the bottom-left of the page. Call repeatedly to build up pages, then call save_pdf. This only works on a session from create_pdf — to add notes/highlights to an existing PDF file use annotate_pdf instead.
| Name | Type | Req | Description |
|---|---|---|---|
| content | – | – | Text to draw. Required when content_type='text'. |
| content_type | string | yes | 'text' draws a text string at (x, y) on the current page; 'new_page' appends a blank page and makes it current. |
| font | – | – | Font name (e.g. 'Helvetica', 'Courier', 'Times-Roman'). Defaults to Helvetica when omitted. |
| font_size | number | – | Font size in points for text content. |
| session_id | string | yes | Session id returned by create_pdf. Must be active. |
| x | – | – | Horizontal position in PDF points from the left edge. Required when content_type='text'. |
| y | – | – | Vertical position in PDF points from the bottom edge (origin is bottom-left). Required when content_type='text'. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
analyze_pdf Analyze / validate a PDF ~278
Inspect a PDF's structural health or conformance (does not read content). Returns JSON keyed by the chosen check: validate → {valid, error_count, warning_count}; corruption → {corrupted, corruption_type, severity, found_pages, file_size, errors}; compliance → {level, is_valid, error_count, warning_count, compliance_percentage}; compare → {structurally_equivalent, content_equivalent, similarity_score, difference_count}. Read-only. Use this to verify a file is well-formed, archival-grade, or identical to another. To read titles/author/page counts use read_pdf; for the text use extract_text.
| Name | Type | Req | Description |
|---|---|---|---|
| check | string | – | Which analysis to run: 'validate' = structural validity with error/warning counts; 'corruption' = damage severity and type; 'compliance' = PDF/A conformance at compliance_level; 'compare' = diff agai… |
| compare_path | – | – | Second PDF to diff against. Required when check='compare', ignored otherwise. |
| compliance_level | string | – | PDF/A conformance level to test. Used only when check='compliance'. Letter = conformance class (a/b/u), number = PDF/A part (1/2/3). |
| path | string | yes | Path to the PDF file to analyze, relative to the workspace. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
annotate_pdf Annotate a PDF ~289
Stamp a sticky note or highlight onto a page of an existing PDF. Writes the annotated copy to output_path (overwriting any existing file) and returns JSON {status, annotation_type}; out-of-range pages or coordinates outside the page bounds return {error, code}. Coordinates are in PDF points with the origin at the bottom-left. Use this to mark up a document. To reorder/rotate/overlay whole pages use manipulate_pdf; to author a new PDF use create_pdf.
| Name | Type | Req | Description |
|---|---|---|---|
| annotation_type | string | yes | 'text' adds a sticky-note marker at (x, y); 'highlight' draws a highlight rectangle of width×height anchored at (x, y). |
| contents | – | – | Note text for a 'text' annotation. Ignored for 'highlight'. |
| height | number | – | Highlight height in points. Used only for 'highlight'. |
| input_path | string | yes | Source PDF to annotate, relative to the workspace. |
| output_path | string | yes | Destination .pdf path; overwritten if it already exists. |
| page | integer | yes | 0-based index of the page to annotate. |
| width | number | – | Highlight width in points. Used only for 'highlight'. |
| x | number | yes | Horizontal anchor in PDF points from the left edge. |
| y | number | yes | Vertical anchor in PDF points from the bottom edge (origin is bottom-left). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
convert_pdf Convert PDF to text representation ~248
Convert a whole PDF into a text representation for downstream LLM use. Returns JSON: {content, format} for 'markdown', or {chunks, format} for 'chunks'/'rag' (each chunk carries its index and page_numbers; rag chunks add token_estimate and heading_context). Read-only. Use this when you need structure or chunking. If you just want the raw reading text use extract_text; for per-run coordinates use extract_entities.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | yes | Output representation: 'markdown' = one structured Markdown document; 'chunks' = fixed-size token windows; 'rag' = heading-aware semantic chunks for retrieval pipelines. |
| max_tokens | integer | – | Target maximum tokens per chunk. Applies to format='chunks' only; ignored for 'markdown' and 'rag' (rag uses heading-aware semantic chunking with a fixed internal budget). |
| overlap | integer | – | Token overlap carried between consecutive chunks. Applies to format='chunks' only; ignored for 'markdown' and 'rag'. |
| password | – | – | User password to unlock an encrypted PDF before conversion. |
| path | string | yes | Path to the PDF file, relative to the configured workspace. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
create_pdf Start a PDF creation session ~177
Open an in-memory PDF building session; the first step of authoring a PDF. Returns JSON {session_id, status, page_size}. No file is written here — this only allocates a session (with one blank starting page) held in server memory and subject to a TTL. Not idempotent: each call creates a new session. Workflow: create_pdf → add_pdf_content (text / new pages, repeatable) → save_pdf (writes the file and closes the session). To annotate or fill an existing PDF instead of authoring one, use annotate_pdf or manage_forms.
| Name | Type | Req | Description |
|---|---|---|---|
| author | – | – | Document author; stored in the PDF metadata on save. |
| page_size | string | – | Page size for every page in this document. |
| title | string | yes | Document title; stored in the PDF metadata on save. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
extract_entities Extract positioned text runs ~140
Extract every text run of a PDF together with its layout geometry. Returns JSON {path, entities, entity_count, page_count} where each entity is {text, page (0-based), x, y, font_size, font_name}. Coordinates are in PDF points with the origin at the bottom-left of the page. Read-only. Use this for layout-aware tasks (table reconstruction, positional lookup, locating a label on the page). If you only need the reading text without coordinates, use extract_text; for Markdown or RAG chunks use convert_pdf.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Path to the PDF file, relative to the configured workspace. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
extract_text Extract plain text ~157
Extract the raw, unformatted text of a PDF as a single string. Returns JSON {text, page_count} (plus `page` when a specific page was requested). Read-only. Use this when you want the plain reading text. If you need Markdown structure or chunking for LLM/RAG pipelines use convert_pdf; if you need each text run with its on-page coordinates and font use extract_entities.
| Name | Type | Req | Description |
|---|---|---|---|
| page | – | – | 0-based page index to extract. Omit to extract every page joined by newlines. Out-of-range indices return an error. |
| password | – | – | User password to unlock an encrypted PDF before extraction. |
| path | string | yes | Path to the PDF file, relative to the configured workspace. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
manage_forms Manage PDF form fields ~332
Create, fill, read or validate PDF form fields. Returns JSON per operation: create→{status, fields_created}; fill→{status, fields_filled}; read→{path, fields, page_count}; validate→{valid, fields}. 'create'/'fill' write output_path (overwriting); 'read'/'validate' are read-only computations. Honest limitations: 'fill' lays the values into a new overlay at computed positions rather than mapping them onto the original AcroForm widgets; 'read' returns the page's text runs (not declared AcroForm field objects); 'validate' currently enforces only a non-empty (required) rule per value. For page-structure edits use manipulate_pdf; to read prose use extract_text.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | – | – | Field definitions for 'create'. Each: {name, type:'text', x, y, width, height (points), default_value?}. |
| input_path | – | – | Source PDF. Required for 'fill', 'read' and 'validate'; unused for 'create'. |
| operation | string | yes | 'create' a new PDF with text fields; 'fill' values onto a copy of an existing PDF; 'read' the text content of a form; 'validate' supplied values. 'read' and 'validate' do not write a file. |
| output_path | – | – | Destination .pdf path (overwritten if present). Required for 'create' and 'fill'; unused for 'read'/'validate'. |
| values | – | – | Map of field name to value. Required for 'fill' and 'validate'. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
manipulate_pdf Restructure PDF pages ~325
Restructure the pages of existing PDF file(s) and write a new PDF. Each operation writes to output_path (overwriting any existing file) and returns JSON {status, operation}; on a missing required argument it returns {error, code}. Per-operation requirements: merge→input_paths; rotate→degrees; extract_pages→page_indices; overlay→overlay_path; split→output_path is a directory. Page indices are 0-based. Use this for page-level structure. To stamp notes/highlights use annotate_pdf; to fill form fields use manage_forms; to encrypt use secure_pdf.
| Name | Type | Req | Description |
|---|---|---|---|
| degrees | – | – | Clockwise rotation in degrees (e.g. 90, 180, 270). Required for 'rotate'. |
| input_path | – | – | Source PDF. Required for every operation except 'merge' (which uses input_paths). |
| input_paths | – | – | Ordered list of PDFs to combine. Required for 'merge'. |
| operation | string | yes | Page operation: 'split' one PDF into per-page files; 'merge' several PDFs into one; 'rotate' all pages; 'extract_pages' a subset; 'reverse' page order; 'overlay' one PDF on top of another. |
| output_path | – | – | Output location, overwritten if it exists. For 'split' this is an existing directory; for all other operations a .pdf file. |
| overlay_path | – | – | PDF stamped on top of input_path. Required for 'overlay'. |
| page_indices | – | – | 0-based page indices to keep, in order. Required for 'extract_pages'. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
read_pdf Read PDF metadata ~232
Read a single PDF's document-level metadata without parsing its content. Returns a JSON object with: page_count, is_encrypted, version, title, author, subject, keywords, and (when include_page_details=true) a `pages` array of {index, width, height, rotation}. Read-only: never modifies the file. Use this to inspect what a PDF is before deciding how to process it. For structural validation, corruption/PDF-A checks, or comparing two files use analyze_pdf instead; for the actual text use extract_text. Encrypted files without a password return {is_encrypted, locked, message} rather than metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| include_page_details | boolean | – | When true, also return per-page width, height (in PDF points) and rotation. Off by default to keep the response small. |
| password | – | – | User password to unlock an encrypted PDF. Omit for unencrypted files; if omitted on an encrypted file the tool reports it as locked instead of failing. |
| path | string | yes | Path to the PDF file, relative to the configured workspace. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
save_pdf Save and close a PDF session ~212
Render an open create_pdf session to a PDF file (step 3 of 3, terminal). Builds a Document from the session's accumulated pages, writes it to output_path (overwriting any existing file), then deletes the session — so the session_id is no longer usable afterwards. Returns JSON {status, path, page_count}, or {error, code} if the session is missing. Only finalizes sessions created via create_pdf/add_pdf_content. To encrypt an already-saved PDF use secure_pdf; to add annotations use annotate_pdf.
| Name | Type | Req | Description |
|---|---|---|---|
| output_path | string | yes | Destination .pdf path inside the workspace. An existing file at this path is overwritten. |
| owner_password | – | – | Owner/permissions password. Encryption is applied only when both user_password and owner_password are provided. |
| session_id | string | yes | Session id returned by create_pdf to finalize. |
| user_password | – | – | If set together with owner_password, the saved PDF is encrypted; this is the password required to open it. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
secure_pdf Encrypt / inspect PDF security ~284
Encrypt a PDF, report its encryption status, or verify its signatures. Returns JSON per operation: encrypt→{status, operation, page_count, note}; permissions→{path, is_encrypted, unlocked, permissions}; verify_signatures→ {path, signatures, signature_count}. 'permissions' and 'verify_signatures' are read-only; 'encrypt' writes output_path (overwriting). Caveat: 'encrypt' rebuilds the document from its text, preserving content and layout but possibly dropping images, embedded fonts and vector graphics (the current API has no in-place encryption). To encrypt a PDF you are authoring, pass the passwords to save_pdf instead.
| Name | Type | Req | Description |
|---|---|---|---|
| input_path | – | – | Source PDF. Required for all three operations. |
| operation | string | yes | 'encrypt' writes a password-protected copy; 'permissions' reports encryption status; 'verify_signatures' checks digital signatures. Only 'encrypt' writes a file. |
| output_path | – | – | Destination .pdf for the encrypted copy (overwritten if present). Required for 'encrypt'; unused otherwise. |
| owner_password | – | – | Owner/permissions password. Required for 'encrypt'. |
| password | – | – | Password used to unlock the file when checking 'permissions' on an encrypted PDF. Unused by other operations. |
| user_password | – | – | Open password for the encrypted copy. Required for 'encrypt'. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the oxidize-pdf MCP Server server?
oxidize-pdf MCP Server runs locally as a PyPI package, launched with uvx --from 'oxidize-pdf[mcp]==0.23.0' oxidize-pdf oxidize-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
pypi · oxidize-pdf
claude mcp add bzsanti-oxidize-pdf-mcp -- uvx --from 'oxidize-pdf[mcp]==0.23.0' oxidize-pdf oxidize-mcp
What is the oxidize-pdf MCP Server server?
oxidize-pdf MCP Server is listed in the public MCP registry as io.github.bzsanti/oxidize-pdf-mcp. MCP server for PDF generation, parsing, splitting, merging, and manipulation via oxidize-pdf. This page covers its PyPI package (oxidize-pdf).
Is the oxidize-pdf MCP Server server safe to use?
oxidize-pdf MCP Server scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. 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 oxidize-pdf MCP Server server expose?
oxidize-pdf MCP Server exposes 12 tools: read_pdf, extract_text, convert_pdf, analyze_pdf, extract_entities, and 7 more. Their descriptions and schemas cost roughly 2,968 tokens of context every time the server is loaded.
Is the oxidize-pdf MCP Server server still maintained?
oxidize-pdf MCP Server is still listed as active in the MCP registry. We last reached this channel on 21 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 oxidize-pdf MCP Server server under?
oxidize-pdf MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the oxidize-pdf MCP Server server?
VerifyMCP ran 15 checks on oxidize-pdf MCP Server, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about oxidize-pdf MCP Server: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.