Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.zp130221/pdfedit-mcp

NPM · @NIUBAI/PDFEDIT-MCP · 2 COMPONENTS

Edit text inside existing PDFs: replace, delete, redact, insert, fill forms; original fonts kept.

77 Trust /100

Last scanned (6 hours ago)

Scores higher than 53% of npm servers

Category Documents and Files

Trust breakdown (7 categories)

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 Security100
  • 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
  • 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to zp130221/pdfedit-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability57
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 980 tokens (~196/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 Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 56% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.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 current MCP spec version (2026-07-28).Pass
Changelog

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.

  • 18 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 17 Oct 26 +13
    • Malware scan: pass → unverified ▼ security
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Stability: unverified → 0.03 ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Tool coverage: 56 functional
    • First check of Schema quality: good functional
    • First check of Schema quality: fail functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: fail functional
    • Package version: 0.1.4 → 0.1.5 functional
  • 16 Oct 26 49

    First indexed and scored.

Diagnostics

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 18 Oct 2026 · Analysed npm/@niubai/pdfedit-mcp@0.1.5

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 zp130221/pdfedit-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/zp130221/pdfedit-mcp/.github/workflows/mcp.yml@refs/tags/mcp-v0.1.5
Rekor log index 3290192493
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:a153125a962d877196b9703405bc93d703d337722f4cf5fb65af665208604b5cfb6d425fb00179ff07956eeb778d4c6d4dedf67235118dedf060d065d

Background: How many MCP packages publish verified provenance →

Dependencies 3 packages
Packages resolved 3
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~980 tokens

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 →

Tool Tokens
pdf_batch ~233

Apply the same edits to one template PDF once per record, producing one output document per record — a mail merge over an existing PDF. Returns a `job_id`: call `pdf_job` with it for the per-record results. To change text on one page only, set `scope.pages`; to pick one of several identical matches, use `scope.after` with nearby text or `scope.occurrence`. Use `op: 'redact'` when the text must be unrecoverable.

NameTypeReqDescription
editsarrayyesThe edits applied to each record, with `{field}` placeholders filled from it.
filestringyesThe PDF: an absolute (or ~) local path, which this server uploads for you, an https:// URL the API fetches, or an `f_…` file id from an earlier call. Used as the template for every record.
optionsobject––
passwordstring––
recordsarray–One object per output document.
records_urlstring–A CSV or JSONL file of records, instead of `records`.

No output schema declared.

No examples provided.

pdf_edit ~296

Edit the text of an existing PDF in place: replace, delete, redact, insert, or fill form fields, keeping the original layout, fonts and everything you did not point at. `edits[]` is taken exactly as the API takes it (`op`, `scope`, `match`, `fit`), and the result carries up to 3 before/after previews of the pages that changed. To change text on one page only, set `scope.pages`; to pick one of several identical matches, use `scope.after` with nearby text or `scope.occurrence`. Use `op: 'redact'` when the text must be unrecoverable.

NameTypeReqDescription
editsarrayyesThe edits to apply, in order, exactly as `POST /v1/edit` takes them.
filestringyesThe PDF: an absolute (or ~) local path, which this server uploads for you, an https:// URL the API fetches, or an `f_…` file id from an earlier call.
optionsobject––
output_pathstring–Where to write the edited PDF (stdio mode only). Default: `<name>.edited.pdf` next to the input, or `<name>.edited.2.pdf`, `.3.pdf`, ... when that exists; an earlier result is never overwritten.
passwordstring–The document open password, when it has one.

No output schema declared.

No examples provided.

pdf_find ~214

Read the text of a PDF: every span with its page, position, font and span id, optionally filtered by `query` (the same four `match` modes an edit uses) and `pages`, over the `content`, `forms` and `annotations` layers. Paginated: pass the returned `next_cursor` back as `cursor` for the next page. Use it before `pdf_edit` to check what a document actually says and to pick the `scope` that selects the match you mean.

NameTypeReqDescription
cursorstring|null––
filestringyesThe PDF: an absolute (or ~) local path, which this server uploads for you, an https:// URL the API fetches, or an `f_…` file id from an earlier call.
layersarray––
limitinteger–(default: 200)
matchobject––
pages–––
passwordstring––
querystring|null––

No output schema declared.

No examples provided.

pdf_job ~99

The result of an async edit or a batch, by `job_id`: the same body `pdf_edit` returns once the job is done, plus `progress` while it is still queued or running, and `records` for a batch.

NameTypeReqDescription
job_idstringyesThe `job_id` an async edit or a batch returned.
output_pathstring–Where to write the finished document (stdio mode, single-document jobs only).

No output schema declared.

No examples provided.

pdf_preview ~138

Render one page of a PDF as a PNG image block, optionally cropped to `region` and with rectangles drawn over `highlight`. Use it to see a page before editing it, or to check the result afterwards.

NameTypeReqDescription
filestringyesThe PDF: an absolute (or ~) local path, which this server uploads for you, an https:// URL the API fetches, or an `f_…` file id from an earlier call.
highlight–––
pageinteger–(default: 1)
passwordstring––
region–––
scale––(default: 2)

No output schema declared.

No examples provided.

Install

How do I install the io.github.zp130221/pdfedit-mcp server?

io.github.zp130221/pdfedit-mcp runs locally as an npm package, launched with npx -y @niubai/pdfedit-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 · @niubai/pdfedit-mcp

# add to Claude Code
claude mcp add zp130221-pdfedit-mcp -- npx -y @niubai/pdfedit-mcp
Common questions

What is the io.github.zp130221/pdfedit-mcp server?

io.github.zp130221/pdfedit-mcp is listed in the public MCP registry as io.github.zp130221/pdfedit-mcp. Edit text inside existing PDFs: replace, delete, redact, insert, fill forms; original fonts kept. This page covers its npm package (@niubai/pdfedit-mcp).

Is the io.github.zp130221/pdfedit-mcp server safe to use?

io.github.zp130221/pdfedit-mcp scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 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 io.github.zp130221/pdfedit-mcp server expose?

io.github.zp130221/pdfedit-mcp exposes 5 tools: pdf_edit, pdf_batch, pdf_find, pdf_preview, pdf_job. Their descriptions and schemas cost roughly 980 tokens of context every time the server is loaded.

Is the io.github.zp130221/pdfedit-mcp server still maintained?

io.github.zp130221/pdfedit-mcp is still listed as active in the MCP registry. We last reached this channel on 18 October 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 io.github.zp130221/pdfedit-mcp server under?

io.github.zp130221/pdfedit-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.