Onepdf MCP Server

onepdf-mcp-server npm v0.4.0

Published by wendongai — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

91 trustworthy PDF tools for Claude, Cursor, Codex, and other MCP clients

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 3

high Shell/command execution in server code (dist/lib/dependencies.js)MTC-SRC-002

In the server's implementation (`dist/lib/dependencies.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: { execFile } from 'node:child_process'; import { promisify } from 'node:util'; const execFileAsync = promisify(execFile)

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/lib/dependencies.js

high Shell/command execution in server code (dist/lib/exec-safe.js)MTC-SRC-002

In the server's implementation (`dist/lib/exec-safe.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ecFileSync } from 'node:child_process'; /** * Safely execute a command using execFileSync (no shell interpretation) *

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/lib/exec-safe.js

high Shell/command execution in server code (dist/lib/process-runner.js)MTC-SRC-002

In the server's implementation (`dist/lib/process-runner.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: rt { spawn } from 'node:child_process'; function appendBounded(current, chunk, maximum) { const currentBytes = Buffe

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/lib/process-runner.js

Tools 98

Each tool and what it can reach — statically extracted from the published source.

  • get_page_textingests untrusted input
  • page_dimensionsingests untrusted input
  • add_attachmentsno sensitive capability
  • add_blank_pageno sensitive capability
  • add_header_footerno sensitive capability
  • add_stampsno sensitive capability
  • ai_chat_with_pdfno sensitive capability
  • ai_extract_infono sensitive capability
  • ai_summarizeno sensitive capability
  • alternate_mergeno sensitive capability
Show 88 more tools ↓
  • background_colorno sensitive capability
  • bates_number_pdfno sensitive capability
  • bmp_to_pdfno sensitive capability
  • cbz_to_pdfno sensitive capability
  • change_permissionsno sensitive capability
  • combine_single_pageno sensitive capability
  • compare_pdfsno sensitive capability
  • compressno sensitive capability
  • crop_pdfno sensitive capability
  • decryptno sensitive capability
  • delete_pagesno sensitive capability
  • deskew_pdfno sensitive capability
  • divide_pagesno sensitive capability
  • djvu_to_pdfno sensitive capability
  • edit_attachmentsno sensitive capability
  • edit_bookmarksno sensitive capability
  • edit_metadatano sensitive capability
  • email_to_pdfno sensitive capability
  • encryptno sensitive capability
  • epub_to_pdfno sensitive capability
  • excel_to_pdfno sensitive capability
  • extract_attachmentsno sensitive capability
  • extract_imagesno sensitive capability
  • extract_pagesno sensitive capability
  • extract_tablesno sensitive capability
  • fix_page_sizeno sensitive capability
  • flatten_pdfno sensitive capability
  • font_to_outlineno sensitive capability
  • form_creatorno sensitive capability
  • form_fillerno sensitive capability
  • get_pdf_chunksno sensitive capability
  • grid_combineno sensitive capability
  • heic_to_pdfno sensitive capability
  • image_to_pdfno sensitive capability
  • invert_colorsno sensitive capability
  • jpg_to_pdfno sensitive capability
  • json_to_pdfno sensitive capability
  • linearize_pdfno sensitive capability
  • markdown_to_pdfno sensitive capability
  • mergeno sensitive capability
  • mobi_to_pdfno sensitive capability
  • nup_pdfno sensitive capability
  • ocg_managerno sensitive capability
  • page_numberno sensitive capability
  • pdf_bookletno sensitive capability
  • pdf_readerno sensitive capability
  • pdf_searchno sensitive capability
  • pdf_to_bmpno sensitive capability
  • pdf_to_docxno sensitive capability
  • pdf_to_excelno sensitive capability
  • pdf_to_greyscaleno sensitive capability
  • pdf_to_jpgno sensitive capability
  • pdf_to_jsonno sensitive capability
  • pdf_to_markdownno sensitive capability
  • pdf_to_pdfano sensitive capability
  • pdf_to_pngno sensitive capability
  • pdf_to_pptno sensitive capability
  • pdf_to_tiffno sensitive capability
  • pdf_to_webpno sensitive capability
  • pdf_to_zipno sensitive capability
  • png_to_pdfno sensitive capability
  • posterize_pdfno sensitive capability
  • powerpoint_to_pdfno sensitive capability
  • psd_to_pdfno sensitive capability
  • rasterize_pdfno sensitive capability
  • redact_pdfno sensitive capability
  • remove_annotationsno sensitive capability
  • remove_blank_pagesno sensitive capability
  • remove_metadatano sensitive capability
  • remove_restrictionsno sensitive capability
  • repair_pdfno sensitive capability
  • reverse_pagesno sensitive capability
  • rotateno sensitive capability
  • rtf_to_pdfno sensitive capability
  • sanitize_pdfno sensitive capability
  • sign_pdfno sensitive capability
  • sort_pagesno sensitive capability
  • splitno sensitive capability
  • svg_to_pdfno sensitive capability
  • system_statusno sensitive capability
  • table_of_contentsno sensitive capability
  • tiff_to_pdfno sensitive capability
  • txt_to_pdfno sensitive capability
  • view_metadatano sensitive capability
  • watermarkno sensitive capability
  • webp_to_pdfno sensitive capability
  • word_to_pdfno sensitive capability
  • xps_to_pdfno sensitive capability

What this scan could not see

Versions 2

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.4.0 latest A 93/100 3 1.13.0 2026-09-05
v0.3.0 A 93/100 3 1.12.1 2026-07-28

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/onepdf-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/onepdf-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/onepdf-mcp-server"><img src="https://mcptrustchecker.com/registry/onepdf-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/onepdf-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan onepdf-mcp-server --online

Use the free API → How scoring works

More in AI & Agents