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.

work.duebuddy/invoices

PYPI · DUEBUDDY-MCP · 2 COMPONENTS

Read supplier invoices (PDF, photo, XML) and return fields plus a DATEV/1C/CSV file.

54 Trust /100

Last scanned (18 hours ago)

Scores higher than 52% of PyPI 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 Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability77
  • 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 957 tokens (~239/item across 4 items; 4 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 Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • 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 4 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 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 (14)

  • 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 (2)

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

  • 21 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 18 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 17 Nov 26 54

    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 pypi/duebuddy-mcp@1.1.1

Provenance No attestation

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

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 28 packages
Packages resolved 28
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~766 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
get_balance ~128

Shows how many scanned pages are left on the prepaid balance for this API key. Use when: before a batch of scans or photos, or when parse_invoice answered insufficient_balance and you need to confirm the remaining amount. Do not use when: the user asks about invoice content — that is get_result. Side effects and cost: none; read-only and idempotent. Parameters: api_key is the DueBuddy key; optional if DUEBUDDY_API_KEY is set. Returns: {ok, balance} with the remaining pages and the current plan.

NameTypeReqDescription
api_keystring––

Structured output declared, but exposes no named fields.

No examples provided.

get_result ~207

Returns the result of a parse job started by parse_invoice: structured fields (supplier, invoice number, dates, net/VAT/gross, currency, line items) plus export links for accounting systems. Use when: you already have a job_id and want its status or its extracted data. Do not use when: you have no job_id yet — start with parse_invoice. Do not poll in a tight loop; one call every few seconds is enough, and jobs for text PDFs or XML usually finish in under a minute. Side effects and cost: none. This call is read-only and idempotent, reads nothing from the prepaid balance, and can be repeated safely. Parameters: job_id is the identifier returned by parse_invoice for the same API key. Returns: {ok, result} where result.status is one of queued, processing, done, failed; on done it also carries fields and export links.

NameTypeReqDescription
api_keystring––
job_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

parse_invoice ~300

Reads ONE incoming supplier invoice and returns a job id for polling. Use when: the user has a single invoice (PDF, photo, scan, XML e-invoice or QR bill) and wants supplier, invoice number, dates, amounts, VAT or line items extracted. Do not use when: the user asks to ISSUE an invoice, to send a payment, or to post entries into DATEV/1C — this tool only reads documents. For several documents call it once per document; the returned job ids can be polled independently. Side effects and cost: the document is downloaded and queued for parsing. XML and QR invoices are parsed by code and cost nothing; scans and photos cost 0.07 EUR per page and are charged to the prepaid balance. The call is not idempotent: each call creates a new job and a new charge for scans, so do not retry blindly after a timeout — poll get_result with the job id instead. Parameters: file_url must be a public https link to a single document on duebuddy.work (upload first via the cabinet); country is a two-letter code from the supported list and selects the parsing profile — it changes field names and tax rules, but does not change the price. Returns: {ok, job_id, status}. Next step: call get_result with that job_id.

NameTypeReqDescription
api_keystring––
countrystring––
file_urlstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

topup_link ~131

Returns the page where the prepaid balance can be topped up, and the minimum amount. Use when: the balance is empty or too low for the documents the user wants to process. Do not use when: the balance is sufficient — check it with get_balance first. Side effects and cost: none. The call only builds a link; the payment itself happens in the browser and is handled by the payment provider, never by this server. Parameters: amount_eur is informational only and does not create an order. Returns: {ok, url, minimum_eur}.

NameTypeReqDescription
amount_eurnumber––

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the work.duebuddy/invoices MCP server?

work.duebuddy/invoices runs locally as a PyPI package, launched with uvx duebuddy-mcp. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · duebuddy-mcp

# add to Claude Code
claude mcp add work-duebuddy-invoices -- uvx duebuddy-mcp

The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it.

Common questions

What is the work.duebuddy/invoices MCP server?

work.duebuddy/invoices is an MCP server listed in the public MCP registry as work.duebuddy/invoices. Read supplier invoices (PDF, photo, XML) and return fields plus a DATEV/1C/CSV file. This page covers its PyPI package (duebuddy-mcp).

Is the work.duebuddy/invoices MCP server safe to use?

work.duebuddy/invoices scores 54 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. 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 work.duebuddy/invoices MCP server expose?

work.duebuddy/invoices exposes 4 tools: parse_invoice, get_result, get_balance, topup_link. Their descriptions and schemas cost roughly 766 tokens of context every time the server is loaded.

Is the work.duebuddy/invoices MCP server still maintained?

work.duebuddy/invoices 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 work.duebuddy/invoices MCP server under?

work.duebuddy/invoices 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 work.duebuddy/invoices MCP server?

VerifyMCP ran 14 checks on work.duebuddy/invoices, covering Known CVEs, Install scripts, Dependency health, Source repository and 10 more. 2 items could not be completed, a gap on our side rather than a finding about work.duebuddy/invoices: Malware scan and 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 a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.