# io.github.ANTONDrakon/duebuddy-invoices (remote · duebuddy.work)

Read incoming supplier invoices through a remote MCP server and get structured data for accounting.

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

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

## Channel facts

- Endpoint: `https://duebuddy.work/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-05.

- **Endpoint Security**: 51/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 521, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 352 tokens (~88/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/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.
- **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 current MCP spec version (2026-07-28).

## Install

### How do I install the io.github.ANTONDrakon/duebuddy-invoices MCP server?

io.github.ANTONDrakon/duebuddy-invoices is a hosted endpoint at https://duebuddy.work/mcp, so there is nothing to install locally. 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 --transport http antondrakon-duebuddy-invoices 'https://duebuddy.work/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "antondrakon-duebuddy-invoices": {
      "url": "https://duebuddy.work/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "antondrakon-duebuddy-invoices": {
      "type": "http",
      "url": "https://duebuddy.work/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.antondrakon-duebuddy-invoices]
url = "https://duebuddy.work/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "antondrakon-duebuddy-invoices": {
      "type": "remote",
      "url": "https://duebuddy.work/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add antondrakon-duebuddy-invoices --url 'https://duebuddy.work/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  antondrakon-duebuddy-invoices:
    url: "https://duebuddy.work/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "antondrakon-duebuddy-invoices": {
      "Transport": "http",
      "Url": "https://duebuddy.work/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add antondrakon-duebuddy-invoices -t streamable-http -u 'https://duebuddy.work/mcp'
```

### Other

```json
{
  "mcpServers": {
    "antondrakon-duebuddy-invoices": {
      "type": "http",
      "url": "https://duebuddy.work/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-05 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 68, +1)

- [security] Tool “topup_link” rewrote its description, which is the text the model reads

### 2026-10-31 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 62, +3)

- [security improvement] HSTS header: fail → pass

## MCP tools (4)

### `parse_invoice` (~124 tokens)

Read one incoming invoice. Pass a publicly reachable file URL and the country code (de, fr, it, pl, ru, kz, by, us, ae, sa, ua, ge). The API key can be passed once as an X-Api-Key header when the server is added, instead of on every call. Returns a job id and status. Electronic invoices (XML, QR) are free; scans cost 0.07 EUR per page.

Input parameters:

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

### `get_result` (~40 tokens)

Fetch the result of a parse job: structured fields plus export links for accounting.

Input parameters:

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

### `get_balance` (~32 tokens)

How many scanned pages are left on this API key before the next top-up.

Input parameters:

- `api_key` (string)

### `topup_link` (~41 tokens)

Where to top up the API balance. Lava.top processes the payment; the minimum top-up is 8 EUR.

Input parameters:

- `amount_eur` (number)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/antondrakon-duebuddy-invoices/duebuddy#diagnostics

## Score history

- 2026-11-05: 69
- 2026-11-04: 68
- 2026-11-03: 68
- 2026-11-02: 68
- 2026-11-01: 67
- 2026-10-31: 67
- 2026-10-30: 66
- 2026-10-29: 66
- 2026-10-28: 65
- 2026-10-27: 65
- 2026-10-26: 64
- 2026-10-25: 64
- 2026-10-24: 63
- 2026-10-23: 63
- 2026-10-22: 62
- 2026-10-21: 62
- 2026-10-20: 59
- 2026-10-19: 59
- 2026-10-18: 59
- 2026-10-17: 58
- 2026-10-16: 58
- 2026-10-15: 57
- 2026-10-14: 57
- 2026-10-13: 56
- 2026-10-12: 56
- 2026-10-11: 55
- 2026-10-10: 55

## Common questions

### What is the io.github.ANTONDrakon/duebuddy-invoices MCP server?

io.github.ANTONDrakon/duebuddy-invoices is an MCP server listed in the public MCP registry as io.github.ANTONDrakon/duebuddy-invoices. Read incoming supplier invoices through a remote MCP server and get structured data for accounting. This page covers its hosted endpoint (https://duebuddy.work/mcp).

### Is the io.github.ANTONDrakon/duebuddy-invoices MCP server safe to use?

io.github.ANTONDrakon/duebuddy-invoices scores 69 out of 100 on VerifyMCP. 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.ANTONDrakon/duebuddy-invoices MCP server expose?

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

### Does the io.github.ANTONDrakon/duebuddy-invoices MCP server require authentication?

No. We connected to io.github.ANTONDrakon/duebuddy-invoices without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.ANTONDrakon/duebuddy-invoices MCP server still maintained?

io.github.ANTONDrakon/duebuddy-invoices is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://duebuddy.work/mcp
- Repository: https://github.com/ANTONDrakon/duebuddy-mcp
- Website: https://duebuddy.work/mcp-docs
- Changelog RSS feed: https://verifymcp.io/servers/antondrakon-duebuddy-invoices/duebuddy.xml
- Changelog JSON feed: https://verifymcp.io/servers/antondrakon-duebuddy-invoices/duebuddy.json
- HTML version of this page: https://verifymcp.io/servers/antondrakon-duebuddy-invoices/duebuddy