invoices MCP server
work.duebuddy/invoicesduebuddy.workstreamable-httpv1.1.1Scanned
Read supplier invoices (PDF, photo, XML) and return fields plus a DATEV/1C/CSV file.
4 tools: 2 change things and 2 only read.
- Reads private data · 1
- Reads text others write · 3
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the invoices MCP server can do
The invoices MCP server is published by duebuddy.work, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: parse_invoice and topup_link), but cannot delete data. 2 tools only read.
1 tool reads private data (parse_invoice); 3 tools bring in text other people can write (parse_invoice, get_result and get_balance).
The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 17, 2026, version 1.1.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 2Claude Code: ask
parse_invoiceReads ONE incoming supplier invoice and returns a job id for polling.Reads private dataReads text others write1 finding
Why it is in this group
- The description's first verb is "read": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- private-dataThe input names a file (input.file_url), and the tool reads: it reads files.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "parse_invoice" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "read": a word for reading.
Description, as the server wrote it 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. Not idempotent: each call creates a new job and, for scans, a new charge — do not retry blindly after a timeout, poll get_result 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 that selects the parsing profile and changes field names and tax rules, not the price. api_key may be omitted when the server was added with an X-Api-Key header. Returns: {ok, job_id, status}. Next step: call get_result with that job_id.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
- readOnlyHint: false
- title: Parse one incoming invoice
topup_linkReturns the page where the prepaid balance can be topped up, plus the minimum amount.1 finding
Why it is in this group
- The name "topup_link" says "link": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "topup_link" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "topup_link" says "link": a word for a change.
Description, as the server wrote it 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. Parameters: amount_eur is informational only and does not create an order. Returns: {ok, url, minimum_eur}.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Get top-up link
Only reads 2Show 2 read-only tools
get_balanceShows how many scanned pages are left on the prepaid balance for this API key.Reads text others writeNo findings
Why it is in this group
- The name "get_balance" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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; read-only and idempotent. Parameters: api_key is the DueBuddy key; optional when the server was added with an X-Api-Key header. Returns: {ok, balance} with remaining pages and the current plan.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: Check prepaid balance
get_resultReturns 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 accountin…Reads text others writeNo findings
Why it is in this group
- The name "get_result" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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. Read-only and idempotent; does not touch 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 queued, processing, done or failed; on done it also carries fields and export links.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: Get parsed invoice result
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 15, 2026, 13:20 UTC, unchanged since Nov 15, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://duebuddy.work/mcp: tools/list returned 4 tools to an anonymous client, including topup_link (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnparse_invoice
The server marks "parse_invoice" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "read": a word for reading.
- Warntopup_link
The server marks "topup_link" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "topup_link" says "link": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools4 changed.~4 changedView diff
- Changed:get_balanceOnly readstitledescriptionannotations
- Changed:get_resultOnly readstitledescriptionannotations
- Changed:parse_invoiceChanges thingstitledescriptionannotations
- Changed:topup_linkChanges thingstitledescriptionannotations
Install
Pinned to version 1.1.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http invoices https://duebuddy.work/mcpclaude mcp add --transport http invoices https://duebuddy.work/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__invoices__get_result",
"mcp__invoices__get_balance"
],
"ask": [
"mcp__invoices__parse_invoice",
"mcp__invoices__topup_link"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as invoices. Review it before you use it.
Capability tags behind 3 rules
- mcp__invoices__parse_invoice private-data, untrusted-input
- mcp__invoices__get_result untrusted-input
- mcp__invoices__get_balance untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/work.duebuddy/invoices/verify?hash=ce53f0a0a08486e3fb861c870dd759b6d6ef891451c5e97e29f19b4b92065ab3" | jq -e '.changed == false'Pinned hash ce53f0a0a084, from Nov 17, 2026, 10:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/work.duebuddy/invoices/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/work.duebuddy/invoices)Source: MCP Registry · repository. Synced Nov 17, 2026, 10:18 UTC.
invoices MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the invoices MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the invoices MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the invoices MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the invoices MCP server have?
- 4 tools: 2 write, 2 read. parse_invoice, topup_link, get_result and get_balance.
Does the invoices MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the invoices MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the invoices MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 17, 2026. Every change is on this page and in its Atom feed.