io.github.ANTONDrakon/duebuddy-invoices
REMOTE · DUEBUDDY.WORK
Read incoming supplier invoices through a remote MCP server and get structured data for accounting.
Available components
Last scanned (10 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Documents and Files
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. How we score → Why this is hard to score →
Endpoint Security51
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 521, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 352 tokens (~88/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 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
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 current MCP spec version (2026-07-28).Pass
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.
- 5 Nov 26 +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.
- 2 Nov 26 +1
- Tool “topup_link” rewrote its description, which is the text the model reads security
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 27 Oct 26 +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.
- 25 Oct 26 +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.
- 23 Oct 26 +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.
- 21 Oct 26 +3
- HSTS header: fail → pass ▲ security
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 5 Nov 2026 · Probed https://duebuddy.work/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=duebuddy.work | CN=WE1,O=Google Trust Services,C=US | 4 Nov 2026 | 2 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 2559a5c299951d1813d978b4b126c31a |
| SANs: duebuddy.work, *.duebuddy.work | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of duebuddy.work. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| work. | present | 33659 | 13 | Verified |
| duebuddy.work. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://duebuddy.work/mcp | Verified | 200 | |
| http (plaintext) | http://duebuddy.work/mcp | Inconclusive | 521 |
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 →
get_balance ~32
How many scanned pages are left on this API key before the next top-up.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | – |
No output schema declared.
No examples provided.
get_result ~40
Fetch the result of a parse job: structured fields plus export links for accounting.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | – |
| job_id | string | yes | – |
No output schema declared.
No examples provided.
parse_invoice ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | – |
| country | string | – | – |
| file_url | string | yes | – |
No output schema declared.
No examples provided.
topup_link ~41
Where to top up the API balance. Lava.top processes the payment; the minimum top-up is 8 EUR.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_eur | number | – | – |
No output schema declared.
No examples provided.
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.
remote · duebuddy.work
claude mcp add --transport http antondrakon-duebuddy-invoices 'https://duebuddy.work/mcp'
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.