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

REMOTE · DUEBUDDY.WORK · 2 COMPONENTS

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

76 Trust /100

Last scanned (21 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Documents and Files

Trust breakdown (7 categories)

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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • 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
Schema Quality & AI Usability76
  • 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 1432 tokens (~358/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 Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

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.

  • 19 Nov 26 +3
    • Tool “get_result” rewrote its description, which is the text the model reads security
    • Tool “parse_invoice” rewrote its description, which is the text the model reads security
    • Tool “topup_link” rewrote its description, which is the text the model reads security
    • Tool “get_balance” rewrote its description, which is the text the model reads security
    • Schema quality: 218 → 358 ▼ functional
    • Tool coverage: 0% → 100% ▲ functional
    • “get_balance” reworded the description of “api_key” cosmetic
    • “get_result” reworded the description of “api_key” cosmetic
    • “get_result” reworded the description of “job_id” cosmetic
    • “parse_invoice” reworded the description of “api_key” cosmetic
    • “parse_invoice” reworded the description of “country” cosmetic
    • “parse_invoice” reworded the description of “file_url” cosmetic
    • “topup_link” reworded the description of “amount_eur” cosmetic
  • 18 Nov 26 +1

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

  • 17 Nov 26 +10
    • Authorization: unverified → partial ▲ security
    • Tool “get_balance” rewrote its description, which is the text the model reads security
    • Tool “get_result” rewrote its description, which is the text the model reads security
    • Tool “parse_invoice” rewrote its description, which is the text the model reads security
    • Tool “topup_link” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • First check of Schema quality: 100 functional
    • Schema quality: fair → excellent functional
    • New prompt “invoice_to_accounting” functional
    • Tool “get_result” changed its title: Get parsed invoice result cosmetic
    • Tool “parse_invoice” changed its title: Parse one incoming invoice cosmetic
    • Tool “topup_link” changed its title: Get top-up link cosmetic
    • Tool “get_balance” changed its title: Check prepaid balance cosmetic
  • 16 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 15 Nov 26 62

    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 · 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. DS published 33659 13 Verified
duebuddy.work. No DS 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 HTTPS enforced 301 https://duebuddy.work/mcp
MCP tools · 4 exposed · ~1,317 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 ~249

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 the remaining amount must be confirmed. Do not use when: the user asks about invoice content — that is get_result. Side effects and cost: none. The number comes from the same counter that blocks parsing, so it can change between two calls while a batch is running. Parameter interactions and edge cases: this is the same counter that blocks parsing, so a balance of zero makes the next parse_invoice fail with insufficient_balance and a topup_link is the only way forward. Two keys of one account see the same number, because usage is counted per account. The number can drop between two calls while a batch runs, and pages parsed on the free cabinet allowance are not part of it. Returns: {ok, balance} with remaining pages and the current plan.

NameTypeReqDescription
api_keystring–DueBuddy API key (starts with dd_). Omit it when the server was added with an X-Api-Key header or DUEBUDDY_API_KEY is set; the call returns api_key_required instead of raising.

No output schema declared.

No examples provided.

get_result ~333

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, text PDFs and XML usually finish in under a minute. Side effects and cost: none. Does not touch the prepaid balance, so repeated polling is free; a failed job stays failed. Parameter interactions and edge cases: job_id belongs to the key that created it, so a job started with one key is invisible to another. A pasted URL or a document id from another system returns 404 rather than a guess. A job that failed stays failed — polling it again will not resurrect it; start a new parse_invoice call instead. Returns: {ok, result}, where result.status is queued, processing, done or failed; on done it also carries fields and export links.

NameTypeReqDescription
api_keystring–DueBuddy API key (starts with dd_). Omit it when the server was added with an X-Api-Key header or DUEBUDDY_API_KEY is set. Must be the same key that started the job.
job_idstringyesJob identifier from the parse_invoice response, for example "2507". Scoped to the API key that created it: another key gets 404. Accepts the numeric id, not a URL.

No output schema declared.

No examples provided.

parse_invoice ~501

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. XML and QR invoices are parsed by code and cost nothing; scans and photos cost 0.07 EUR per page, charged to the prepaid balance. Not idempotent: each call creates a new job and a new charge for scans. Parameter interactions and edge cases: the same file parsed twice returns the existing job with charged=false instead of billing twice, so retrying after a client timeout is safe — and the second call's country is ignored, the first profile wins. Per API key there is a request rate limit and a cap of 3 parses in flight; exceeding either returns 429 with Retry-After, which is a throttle, not a billing error. country changes field names and tax checks, never the price. Returns: {ok, job_id, status}. Next step: call get_result with that job_id.

NameTypeReqDescription
api_keystring–DueBuddy API key (starts with dd_). Omit it when the server was added with an X-Api-Key header or DUEBUDDY_API_KEY is set; the call returns api_key_required when no key is available anywhere.
countrystring–Two-letter parsing profile that selects field names and tax rules: de, fr, it, pl, ru, kz, by, us, ae, sa, ua, ge. Defaults to de. Does not change the price; a wrong profile returns plausible but mis…
file_urlstringyesPublic https URL of exactly ONE invoice file hosted on duebuddy.work, for example https://duebuddy.work/files/invoice-218.pdf. Allowed endings: .pdf, .jpg, .jpeg, .png, .xml, .xlsx, .xls, .csv. http…

No output schema declared.

No examples provided.

topup_link ~234

Returns the page where the prepaid balance can be topped up, plus 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 happens in the browser and is handled by the payment provider, never by this server. Parameter interactions and edge cases: amount_eur is echoed back only; a value outside 8..5000 is rejected by parameter validation before the call runs. The returned url is a pricing page, not a payment link tied to a sum — the user chooses the amount there. Calling it repeatedly returns the same page and creates no orders. Returns: {ok, url, minimum_eur}.

NameTypeReqDescription
amount_eurnumber–Planned top-up in euro, minimum 8, maximum 5000, default 8. Informational only: it does not create an order or reserve money, it is echoed back in requested_eur so the assistant can show the user wha…

No output schema declared.

No examples provided.

Install

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

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

# add to Claude Code
claude mcp add --transport http work-duebuddy-invoices 'https://duebuddy.work/mcp'
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 hosted endpoint (https://duebuddy.work/mcp).

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

work.duebuddy/invoices scores 76 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 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 1,317 tokens of context every time the server is loaded.

Does the work.duebuddy/invoices MCP server require authentication?

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

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 did VerifyMCP test on the work.duebuddy/invoices MCP server?

VerifyMCP ran 13 checks on work.duebuddy/invoices, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.