# work.duebuddy/invoices (pypi · duebuddy-mcp)

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

- Trust score: 54/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `duebuddy.work`: 76/100, [markdown](https://verifymcp.io/servers/work-duebuddy-invoices/duebuddy.md), [page](https://verifymcp.io/servers/work-duebuddy-invoices/duebuddy)
- pypi · `duebuddy-mcp`: 54/100 (this document), [markdown](https://verifymcp.io/servers/work-duebuddy-invoices/duebuddy-mcp.md), [page](https://verifymcp.io/servers/work-duebuddy-invoices/duebuddy-mcp)

## Channel facts

- Registry: `pypi`
- Package: `duebuddy-mcp`
- Version: `1.1.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 0 of 28 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

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

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

### Claude

```bash
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.

### Cursor

```json
{
  "mcpServers": {
    "work-duebuddy-invoices": {
      "command": "uvx",
      "args": [
        "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.

### VS Code

```json
{
  "servers": {
    "work-duebuddy-invoices": {
      "command": "uvx",
      "args": [
        "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.

### Codex

```bash
codex 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.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "work-duebuddy-invoices": {
      "type": "local",
      "command": [
        "uvx",
        "duebuddy-mcp"
      ],
      "enabled": true
    }
  }
}
```

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.

### OpenClaw

```bash
openclaw mcp add work-duebuddy-invoices --command uvx --arg 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.

### Hermes

```yaml
mcp_servers:
  work-duebuddy-invoices:
    command: "uvx"
    args: ["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.

### Netclaw

```json
{
  "McpServers": {
    "work-duebuddy-invoices": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "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.

### Vellum

```bash
assistant mcp add work-duebuddy-invoices -t stdio -c uvx -a 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.

### Other

```json
{
  "mcpServers": {
    "work-duebuddy-invoices": {
      "command": "uvx",
      "args": [
        "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 54, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-18 (score 69, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-17 (score 54)

First indexed and scored.

## MCP tools (4)

### `parse_invoice` (~300 tokens)

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.

Input parameters:

- `api_key` (string)
- `country` (string)
- `file_url` (string, required)

### `get_result` (~207 tokens)

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.

Input parameters:

- `api_key` (string)
- `job_id` (string, required)

### `get_balance` (~128 tokens)

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.

Input parameters:

- `api_key` (string)

### `topup_link` (~131 tokens)

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

Input parameters:

- `amount_eur` (number)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/work-duebuddy-invoices/duebuddy-mcp#diagnostics

## Score history

- 2026-11-21: 54
- 2026-11-20: 69
- 2026-11-19: 69
- 2026-11-18: 69
- 2026-11-17: 54

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

## Links

- PyPI project: https://pypi.org/project/duebuddy-mcp/
- Socket report: https://socket.dev/pypi/package/duebuddy-mcp
- Repository: https://github.com/ANTONDrakon/duebuddy-mcp
- Website: https://duebuddy.work/mcp-docs
- Changelog RSS feed: https://verifymcp.io/servers/work-duebuddy-invoices/duebuddy-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/work-duebuddy-invoices/duebuddy-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/work-duebuddy-invoices/duebuddy-mcp.json
- HTML version of this page: https://verifymcp.io/servers/work-duebuddy-invoices/duebuddy-mcp
