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.

pdfvera

NPM · PDFVERA-MCP

PDF invoices to XRechnung/ZUGFeRD; Brazilian bank statement PDFs to OFX, CSV and Excel.

Available components

0 this week 70 Trust /100

Last scanned (21 hours ago)

Scores higher than 41% 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
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 10 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 556 tokens (~185/item across 3 items; 3 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • 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.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

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 →

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.

  • 11 Nov 26 +26
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → pass ▲ functional
  • 10 Nov 26 44

    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 21 Nov 2026 · Analysed npm/pdfvera-mcp@1.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~556 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
convert_bank_statement ~195

Convert a Brazilian bank statement PDF (extrato bancário) into OFX for an accounting system, CSV and Excel. The entries are summed and checked against the balances printed in the statement; files are only written when the balance reconciles. Password-protected PDFs need `password` (or `cpf` to try the banks' usual passwords). Each converted statement counts once against the monthly quota of the user's pdfvera plan; check_only never counts.

NameTypeReqDescription
check_onlyboolean–Only check, write no files and use no quota
cpfstring–Account holder's CPF, to try the banks' usual passwords
output_dirstring–Folder for the result files; default: the PDF's folder
passwordstring–PDF password
pdf_pathstringyesPath of the statement PDF on this computer
profilestring–Accounting system the OFX is for

No output schema declared.

No examples provided.

convert_invoice ~336

Convert a German PDF invoice into an e-invoice: XRechnung 3.0 (UBL and CII), a ZUGFeRD PDF (EN 16931) and a check report, checked against the KoSIT rules. Files are written next to the PDF. If mandatory data is missing, nothing is written and the result lists the missing fields with a German label, help text and example: ask the user for them (or use the offered escape value when it fits), then call again with the same PDF and `answers`. Wrong values read from the PDF are fixed with `corrections` (keys from found[].edit[].key, e.g. fix:number). Each converted invoice counts once against the monthly quota of the user's pdfvera plan; the same PDF again in the same month does not count, check_only never counts.

NameTypeReqDescription
answersobject–Values for missing fields, keyed by questions[].field, e.g. {"buyer_reference": "04011000-12345-06"}
check_onlyboolean–Only check, write no files and use no quota
correctionsobject–Corrections of values read from the PDF, keyed by found[].edit[].key, e.g. {"fix:number": "RE-2026-0042"}
output_dirstring–Folder for the result files; default: the PDF's folder
pdf_pathstringyesPath of the PDF invoice on this computer
rolestring–Whether the user issued (issuer) or received (recipient) the invoice; only changes the wording of the questions

No output schema declared.

No examples provided.

get_usage ~25

Show the user's pdfvera plan and how many documents of the monthly quota are used.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the pdfvera MCP server?

pdfvera runs locally as an npm package, launched with npx -y pdfvera-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 · pdfvera-mcp

# add to Claude Code
claude mcp add com-pdfvera-pdfvera -- npx -y pdfvera-mcp
Common questions

What is the pdfvera MCP server?

pdfvera is an MCP server listed in the public MCP registry as com.pdfvera/pdfvera. PDF invoices to XRechnung/ZUGFeRD; Brazilian bank statement PDFs to OFX, CSV and Excel. This page covers its npm package (pdfvera-mcp).

Is the pdfvera MCP server safe to use?

pdfvera scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 pdfvera MCP server expose?

pdfvera exposes 3 tools: convert_invoice, convert_bank_statement, get_usage. Their descriptions and schemas cost roughly 556 tokens of context every time the server is loaded.

Is the pdfvera MCP server still maintained?

pdfvera 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 pdfvera MCP server under?

pdfvera 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 pdfvera MCP server?

VerifyMCP ran 15 checks on pdfvera, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about pdfvera: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.