Billomat MCP by usefulapi
REMOTE · BILLOMAT.USEFULAPI.IO
Read Billomat clients, invoices, offers, credit notes, reminders; create clients and draft invoices.
Available components
Last scanned (1 hour ago)
Scores higher than 46% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Finance and Payments
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 5852 tokens (~172/item across 34 items; 34 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 Management17
- Stability observed for 5 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 34 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 35 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 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.
- 14 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- New prompt “getting_started” functional
- Server version: 1.0.0 → 1.1.0 functional
- 13 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 59
First indexed and scored.
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 17 Oct 2026 · Probed https://billomat.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| 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 billomat.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://billomat.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://billomat.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://billomat.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://billomat.usefulapi.io/mcp |
| Authorisation server | https://billomat.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://billomat.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/billomat/ |
| http (plaintext) | http://billomat.usefulapi.io/mcp | Inconclusive | 302 | http://billomat.usefulapi.io/mcp |
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 →
billomat_add_invoice_item ~264
WRITE: add one line item to an invoice that is still a DRAFT (Billomat refuses it for any other status). Does not complete or send the invoice.
| Name | Type | Req | Description |
|---|---|---|---|
| article_id | – | – | An article id (from billomat_list_articles): title, unit, price and tax missing here are taken from the article. |
| description | string | – | Item description. |
| invoice_id | – | yes | The draft invoice id. |
| optional | boolean | – | Offers only: mark the item as optional (its price is left out of the total). |
| quantity | number | – | Quantity (required unless article_id is given). |
| reduction | string | – | Discount: absolute (10) or percent (10%). |
| tax_name | string | – | Tax name; with tax_rate overrides the standard tax of the account. |
| tax_rate | number | – | Tax rate in percent; the account's standard rate when omitted. |
| title | string | – | Item title (required unless article_id is given). |
| type | string | – | PRODUCT or SERVICE. |
| unit | string | – | Unit, e.g. Stunde, Stueck, hour. |
| unit_price | number | – | Unit price, net or gross as net_gross of the document (required unless article_id is given). |
No output schema declared.
No examples provided.
billomat_create_article ~140
WRITE: create a new article (product or service) with a price. Billomat assigns the article number.
| Name | Type | Req | Description |
|---|---|---|---|
| currency_code | string | – | ISO currency code, e.g. EUR (account default when omitted). |
| description | string | – | Description. |
| purchase_price | number | – | Purchase price. |
| sales_price | number | – | Sales price (net or gross as the account is set up). |
| tax_id | – | – | Tax rate id (from billomat_list_taxes). |
| title | string | yes | Article title. |
| type | string | – | PRODUCT or SERVICE. |
| unit_id | – | – | Unit id (from billomat_list_units). |
No output schema declared.
No examples provided.
billomat_create_client ~268
WRITE: create a new client (customer) in Billomat. Billomat assigns the client number. Nothing is sent to the client. Check billomat_list_clients first to avoid duplicates.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City. |
| country_code | string | – | ISO 3166 alpha-2 country code, e.g. DE, AT, CH. |
| currency_code | string | – | ISO currency code, e.g. EUR (account default when omitted). |
| string | – | Email address. | |
| first_name | string | – | First name of the contact person. |
| last_name | string | – | Last name of the contact person. |
| locale | string | – | Locale of the documents, e.g. de-DE. |
| mobile | string | – | Mobile phone. |
| name | string | – | Company name. |
| note | string | – | Internal note. |
| phone | string | – | Phone. |
| salutation | string | – | Salutation, e.g. Herr, Frau. |
| state | string | – | State / region. |
| street | string | – | Street and number. |
| tax_number | string | – | Tax number. |
| vat_number | string | – | VAT ID. |
| www | string | – | Website (without http). |
| zip | string | – | ZIP code. |
No output schema declared.
No examples provided.
billomat_create_draft_invoice ~213
WRITE: create an invoice as a DRAFT (Entwurf) for a client, with optional line items. The invoice is NOT completed, has no number yet and is NOT sent; review and complete it in Billomat. Nothing is charged.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | – | yes | The client id (from billomat_list_clients). |
| contact_id | – | – | A contact of that client. |
| currency_code | string | – | ISO currency code, e.g. EUR (account default when omitted). |
| date | string | – | Document date (yyyy-mm-dd; today when omitted). |
| due_days | integer | – | Days until payment is due. |
| intro | string | – | Introduction text. |
| items | array | – | Line items (up to 200). More can be added to the draft later. |
| label | string | – | Label / subject. |
| net_gross | string | – | Whether prices are net or gross. |
| note | string | – | Closing note. |
| title | string | – | Document title. |
No output schema declared.
No examples provided.
billomat_create_draft_offer ~210
WRITE: create an offer (Angebot) as a DRAFT for a client, with optional line items. The offer is NOT completed, has no number yet and is NOT sent; review and complete it in Billomat.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | – | yes | The client id (from billomat_list_clients). |
| contact_id | – | – | A contact of that client. |
| currency_code | string | – | ISO currency code, e.g. EUR (account default when omitted). |
| date | string | – | Document date (yyyy-mm-dd; today when omitted). |
| intro | string | – | Introduction text. |
| items | array | – | Line items (up to 200). More can be added to the draft later. |
| label | string | – | Label / subject. |
| net_gross | string | – | Whether prices are net or gross. |
| note | string | – | Closing note. |
| title | string | – | Document title. |
| validity_days | integer | – | Days the offer stays valid. |
No output schema declared.
No examples provided.
billomat_get_article ~37
Get one article with its prices, unit, tax and supplier.
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | yes | The article id (from billomat_list_articles). |
No output schema declared.
No examples provided.
billomat_get_client ~41
Get one client with address, contact person, bank details, payment terms and revenue.
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | yes | The client id (from billomat_list_clients). |
No output schema declared.
No examples provided.
billomat_get_company ~33
Show the own company data of the Billomat account (name, address, bank details, tax numbers, currency).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
billomat_get_confirmation ~30
Get one order confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | yes | The confirmation id (from billomat_list_confirmations). |
No output schema declared.
No examples provided.
billomat_get_credit_note ~32
Get one credit note.
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | yes | The credit note id (from billomat_list_credit_notes). |
No output schema declared.
No examples provided.
billomat_get_current_user ~40
Show the Billomat user the API key belongs to (name, email, role and rights). Use it to check which rights the key has.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
billomat_get_delivery_note ~32
Get one delivery note.
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | yes | The delivery note id (from billomat_list_delivery_notes). |
No output schema declared.
No examples provided.
billomat_get_incoming_invoice ~40
Get one incoming invoice with amounts and open amount.
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | yes | The incoming invoice id (from billomat_list_incoming_invoices). |
No output schema declared.
No examples provided.
billomat_get_invoice ~51
Get one invoice (status, totals, dates, client, payment terms). Its line items come from billomat_list_invoice_items.
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | yes | The invoice id (from billomat_list_invoices). |
No output schema declared.
No examples provided.
billomat_get_offer ~37
Get one offer (status, totals, validity, client).
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | yes | The offer id (from billomat_list_offers). |
No output schema declared.
No examples provided.
billomat_get_reminder ~31
Get one payment reminder.
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | yes | The reminder id (from billomat_list_reminders). |
No output schema declared.
No examples provided.
billomat_get_supplier ~34
Get one supplier with address and bank details.
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | yes | The supplier id (from billomat_list_suppliers). |
No output schema declared.
No examples provided.
billomat_invoice_totals ~286
Invoice totals grouped by client, status, day, week, month or year (for example group_by=client,year). Takes the same filters as billomat_list_invoices. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| article_id | – | – | Only documents containing this article. |
| client_id | – | – | Only documents of this client (from billomat_list_clients). |
| contact_id | – | – | Only documents of this client contact. |
| from | string | – | Documents dated on or after this day (yyyy-mm-dd). |
| group_by | string | yes | Grouping: client, status, day, week, month, year; several separated by commas (the order sets the aggregation). |
| intro | string | – | Free-text search in the introduction text. |
| invoice_number | string | – | Invoice number (case-insensitive). |
| label | string | – | Free-text search in the label. |
| note | string | – | Free-text search in the note. |
| payment_type | string | – | Payment type(s), e.g. CASH, BANK_TRANSFER, PAYPAL; several separated by commas. |
| status | string | – | Status filter: DRAFT, OPEN, PAID, OVERDUE, CANCELED; several separated by commas. |
| tags | string | – | Comma-separated tags (Schlagworte). |
| to | string | – | Documents dated on or before this day (yyyy-mm-dd). |
No output schema declared.
No examples provided.
billomat_list_articles ~205
List the articles (products and services) with prices, units and tax. Paged.
| Name | Type | Req | Description |
|---|---|---|---|
| article_number | string | – | Article number. |
| currency_code | string | – | ISO currency code, e.g. EUR (account default when omitted). |
| description | string | – | Search in the description. |
| order_by | string | – | Sort order: field name plus ASC or DESC, several separated by commas, e.g. "date DESC" (default ascending). |
| page | integer | – | Page number, 1-based (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Results per page, 1-1000 (default 100). |
| supplier_id | – | – | Only articles of this supplier. |
| tags | string | – | Comma-separated tags (Schlagworte). |
| title | string | – | Title (case-insensitive). |
| unit_id | – | – | Only articles with this unit (from billomat_list_units). |
No output schema declared.
No examples provided.
billomat_list_clients ~252
List the clients (customers) of the account, filtered by name, number, email, contact person, country, note or tags. Paged.
| Name | Type | Req | Description |
|---|---|---|---|
| client_number | string | – | Client number. |
| country_code | string | – | ISO 3166 alpha-2 country code, e.g. DE, AT, CH. |
| string | – | Email address. | |
| first_name | string | – | First name of the contact person. |
| invoice_id | string | – | Comma-separated invoice ids: the clients of these invoices. |
| last_name | string | – | Last name of the contact person. |
| name | string | – | Company / name (case-insensitive). |
| note | string | – | Search in the note. |
| order_by | string | – | Sort order: field name plus ASC or DESC, several separated by commas, e.g. "date DESC" (default ascending). |
| page | integer | – | Page number, 1-based (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Results per page, 1-1000 (default 100). |
| tags | string | – | Comma-separated tags (Schlagworte). |
No output schema declared.
No examples provided.
billomat_list_confirmations ~305
List order confirmations (Auftragsbestaetigungen), filtered by client, status (DRAFT, COMPLETED, CANCELED, CLEARED), number, date range or text. Paged.
| Name | Type | Req | Description |
|---|---|---|---|
| article_id | – | – | Only documents containing this article. |
| client_id | – | – | Only documents of this client (from billomat_list_clients). |
| confirmation_number | string | – | Confirmation number (partial, case-insensitive). |
| contact_id | – | – | Only documents of this client contact. |
| from | string | – | Documents dated on or after this day (yyyy-mm-dd). |
| intro | string | – | Free-text search in the introduction text. |
| label | string | – | Free-text search in the label. |
| note | string | – | Free-text search in the note. |
| order_by | string | – | Sort order: field name plus ASC or DESC, several separated by commas, e.g. "date DESC" (default ascending). |
| page | integer | – | Page number, 1-based (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Results per page, 1-1000 (default 100). |
| status | string | – | Status filter: DRAFT, COMPLETED, CANCELED, CLEARED; several separated by commas. |
| tags | string | – | Comma-separated tags (Schlagworte). |
| to | string | – | Documents dated on or before this day (yyyy-mm-dd). |
No output schema declared.
No examples provided.
billomat_list_credit_notes ~290
List credit notes (Gutschriften), filtered by client, status (DRAFT, OPEN, PAID), date range or text. Paged.
| Name | Type | Req | Description |
|---|---|---|---|
| article_id | – | – | Only documents containing this article. |
| client_id | – | – | Only documents of this client (from billomat_list_clients). |
| contact_id | – | – | Only documents of this client contact. |
| credit_note_number | string | – | Credit note number (case-insensitive). |
| from | string | – | Documents dated on or after this day (yyyy-mm-dd). |
| intro | string | – | Free-text search in the introduction text. |
| label | string | – | Free-text search in the label. |
| note | string | – | Free-text search in the note. |
| order_by | string | – | Sort order: field name plus ASC or DESC, several separated by commas, e.g. "date DESC" (default ascending). |
| page | integer | – | Page number, 1-based (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Results per page, 1-1000 (default 100). |
| status | string | – | Status filter: DRAFT, OPEN, PAID; several separated by commas. |
| tags | string | – | Comma-separated tags (Schlagworte). |
| to | string | – | Documents dated on or before this day (yyyy-mm-dd). |
No output schema declared.
No examples provided.
billomat_list_delivery_notes ~288
List delivery notes (Lieferscheine), filtered by client, status (DRAFT, CREATED), number, date range or text. Paged.
| Name | Type | Req | Description |
|---|---|---|---|
| article_id | – | – | Only documents containing this article. |
| client_id | – | – | Only documents of this client (from billomat_list_clients). |
| contact_id | – | – | Only documents of this client contact. |
| delivery_note_number | string | – | Delivery note number (case-insensitive). |
| from | string | – | Documents dated on or after this day (yyyy-mm-dd). |
| intro | string | – | Free-text search in the introduction text. |
| label | string | – | Free-text search in the label. |
| note | string | – | Free-text search in the note. |
| order_by | string | – | Sort order: field name plus ASC or DESC, several separated by commas, e.g. "date DESC" (default ascending). |
| page | integer | – | Page number, 1-based (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Results per page, 1-1000 (default 100). |
| status | string | – | Status filter: DRAFT, CREATED; several separated by commas. |
| tags | string | – | Comma-separated tags (Schlagworte). |
| to | string | – | Documents dated on or before this day (yyyy-mm-dd). |
No output schema declared.
No examples provided.
billomat_list_incoming_invoices ~244
List incoming invoices (Eingangsrechnungen, from suppliers), filtered by supplier, status (OPEN, PAID, OVERDUE), number, date range, note or tags. Paged.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Dated on or after this day (yyyy-mm-dd). |
| incoming_number | string | – | Incoming invoice number. |
| note | string | – | Free-text search in the note. |
| order_by | string | – | Sort order: field name plus ASC or DESC, several separated by commas, e.g. "date DESC" (default ascending). |
| page | integer | – | Page number, 1-based (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Results per page, 1-1000 (default 100). |
| status | string | – | Status filter: OPEN, PAID, OVERDUE; several separated by commas. |
| supplier_id | – | – | Only incoming invoices of this supplier. |
| tags | string | – | Comma-separated tags (Schlagworte). |
| to | string | – | Dated on or before this day (yyyy-mm-dd). |
No output schema declared.
No examples provided.
billomat_list_invoice_items ~77
List the line items (positions) of one invoice.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | – | yes | The invoice id. |
| page | integer | – | Page number, 1-based (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Results per page, 1-1000 (default 100). |
No output schema declared.
No examples provided.
billomat_list_invoice_payments ~198
List the payments that were recorded on invoices (read-only), optionally for one invoice, a date range or payment types.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Payments on or after this day (yyyy-mm-dd). |
| invoice_id | – | – | Only payments of this invoice. |
| order_by | string | – | Sort order: field name plus ASC or DESC, several separated by commas, e.g. "date DESC" (default ascending). |
| page | integer | – | Page number, 1-based (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Results per page, 1-1000 (default 100). |
| to | string | – | Payments on or before this day (yyyy-mm-dd). |
| type | string | – | Payment type(s), e.g. CASH, BANK_TRANSFER, PAYPAL; several separated by commas. |
| user_id | – | – | Only payments recorded by this user. |
No output schema declared.
No examples provided.
billomat_list_invoices ~343
List invoices (Rechnungen), filtered by client, status (DRAFT, OPEN, PAID, OVERDUE, CANCELED), number, date range, text or tags. Paged; each invoice carries totals and the open amount.
| Name | Type | Req | Description |
|---|---|---|---|
| article_id | – | – | Only documents containing this article. |
| client_id | – | – | Only documents of this client (from billomat_list_clients). |
| contact_id | – | – | Only documents of this client contact. |
| from | string | – | Documents dated on or after this day (yyyy-mm-dd). |
| intro | string | – | Free-text search in the introduction text. |
| invoice_number | string | – | Invoice number (case-insensitive). |
| label | string | – | Free-text search in the label. |
| note | string | – | Free-text search in the note. |
| order_by | string | – | Sort order: field name plus ASC or DESC, several separated by commas, e.g. "date DESC" (default ascending). |
| page | integer | – | Page number, 1-based (default 1). Use next_page from the previous reply. |
| payment_type | string | – | Payment type(s), e.g. CASH, BANK_TRANSFER, PAYPAL; several separated by commas. |
| per_page | integer | – | Results per page, 1-1000 (default 100). |
| status | string | – | Status filter: DRAFT, OPEN, PAID, OVERDUE, CANCELED; several separated by commas. |
| tags | string | – | Comma-separated tags (Schlagworte). |
| to | string | – | Documents dated on or before this day (yyyy-mm-dd). |
No output schema declared.
No examples provided.
billomat_list_offers ~307
List offers (Angebote), filtered by client, status (DRAFT, OPEN, WON, LOST, CANCELED, CLEARED), number, date range or text. Paged.
| Name | Type | Req | Description |
|---|---|---|---|
| article_id | – | – | Only documents containing this article. |
| client_id | – | – | Only documents of this client (from billomat_list_clients). |
| contact_id | – | – | Only documents of this client contact. |
| from | string | – | Documents dated on or after this day (yyyy-mm-dd). |
| intro | string | – | Free-text search in the introduction text. |
| label | string | – | Free-text search in the label. |
| note | string | – | Free-text search in the note. |
| offer_number | string | – | Offer number (partial, case-insensitive). |
| order_by | string | – | Sort order: field name plus ASC or DESC, several separated by commas, e.g. "date DESC" (default ascending). |
| page | integer | – | Page number, 1-based (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Results per page, 1-1000 (default 100). |
| status | string | – | Status filter: DRAFT, OPEN, WON, LOST, CANCELED, CLEARED; several separated by commas. |
| tags | string | – | Comma-separated tags (Schlagworte). |
| to | string | – | Documents dated on or before this day (yyyy-mm-dd). |
No output schema declared.
No examples provided.
billomat_list_recurring_invoices ~258
List recurring invoices (Abo-Rechnungen): name, cycle (DAILY, WEEKLY, MONTHLY, YEARLY), client and next run. Paged.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | – | – | Only documents of this client (from billomat_list_clients). |
| contact_id | – | – | Only documents of this client contact. |
| cycle | string | – | Interval. |
| intro | string | – | Free-text search in the introduction text. |
| label | string | – | Free-text search in the label. |
| name | string | – | Name of the recurring invoice. |
| note | string | – | Free-text search in the note. |
| order_by | string | – | Sort order: field name plus ASC or DESC, several separated by commas, e.g. "date DESC" (default ascending). |
| page | integer | – | Page number, 1-based (default 1). Use next_page from the previous reply. |
| payment_type | string | – | Payment type(s), e.g. CASH, BANK_TRANSFER, PAYPAL; several separated by commas. |
| per_page | integer | – | Results per page, 1-1000 (default 100). |
| tags | string | – | Comma-separated tags (Schlagworte). |
No output schema declared.
No examples provided.
billomat_list_reminders ~323
List payment reminders (Mahnungen), filtered by client, status (DRAFT, OPEN, OVERDUE, PAID, CANCELED), invoice number, date range or text. Paged.
| Name | Type | Req | Description |
|---|---|---|---|
| article_id | – | – | Only documents containing this article. |
| client_id | – | – | Only documents of this client (from billomat_list_clients). |
| contact_id | – | – | Only documents of this client contact. |
| from | string | – | Documents dated on or after this day (yyyy-mm-dd). |
| intro | string | – | Free-text search in the introduction text. |
| invoice_number | string | – | Number of the reminded invoice (case-insensitive). |
| label | string | – | Free-text search in the label. |
| note | string | – | Free-text search in the note. |
| order_by | string | – | Sort order: field name plus ASC or DESC, several separated by commas, e.g. "date DESC" (default ascending). |
| page | integer | – | Page number, 1-based (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Results per page, 1-1000 (default 100). |
| status | string | – | Status filter: DRAFT, OPEN, PAID, OVERDUE, CANCELED; several separated by commas. |
| subject | string | – | Free-text search in the subject. |
| tags | string | – | Comma-separated tags (Schlagworte). |
| to | string | – | Documents dated on or before this day (yyyy-mm-dd). |
No output schema declared.
No examples provided.
billomat_list_suppliers ~229
List the suppliers of the account, filtered by name, email, contact person, country, note or tags. Paged.
| Name | Type | Req | Description |
|---|---|---|---|
| client_number | string | – | Your customer number at the supplier. |
| country_code | string | – | ISO 3166 alpha-2 country code, e.g. DE, AT, CH. |
| string | – | Email address. | |
| first_name | string | – | First name of the contact person. |
| last_name | string | – | Last name of the contact person. |
| name | string | – | Company / name. |
| note | string | – | Search in the note. |
| order_by | string | – | Sort order: field name plus ASC or DESC, several separated by commas, e.g. "date DESC" (default ascending). |
| page | integer | – | Page number, 1-based (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Results per page, 1-1000 (default 100). |
| tags | string | – | Comma-separated tags (Schlagworte). |
No output schema declared.
No examples provided.
billomat_list_taxes ~109
List the tax rates (Steuersaetze) of the account, with the default one.
| Name | Type | Req | Description |
|---|---|---|---|
| order_by | string | – | Sort order: field name plus ASC or DESC, several separated by commas, e.g. "date DESC" (default ascending). |
| page | integer | – | Page number, 1-based (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Results per page, 1-1000 (default 100). |
No output schema declared.
No examples provided.
billomat_list_units ~123
List the units (Einheiten) used for article and item quantities, optionally filtered by name.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Unit name (substring, case-insensitive). |
| order_by | string | – | Sort order: field name plus ASC or DESC, several separated by commas, e.g. "date DESC" (default ascending). |
| page | integer | – | Page number, 1-based (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Results per page, 1-1000 (default 100). |
No output schema declared.
No examples provided.
billomat_update_client ~277
WRITE: change fields of an existing client (only the fields you pass are changed; everything else stays). Read the client first with billomat_get_client. Nothing is sent to the client.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City. |
| country_code | string | – | ISO 3166 alpha-2 country code, e.g. DE, AT, CH. |
| currency_code | string | – | ISO currency code, e.g. EUR (account default when omitted). |
| string | – | Email address. | |
| first_name | string | – | First name of the contact person. |
| id | – | yes | The client id. |
| last_name | string | – | Last name of the contact person. |
| locale | string | – | Locale of the documents, e.g. de-DE. |
| mobile | string | – | Mobile phone. |
| name | string | – | Company name. |
| note | string | – | Internal note. |
| phone | string | – | Phone. |
| salutation | string | – | Salutation, e.g. Herr, Frau. |
| state | string | – | State / region. |
| street | string | – | Street and number. |
| tax_number | string | – | Tax number. |
| vat_number | string | – | VAT ID. |
| www | string | – | Website (without http). |
| zip | string | – | ZIP code. |
No output schema declared.
No examples provided.
How do I install the Billomat MCP by usefulapi server?
Billomat MCP by usefulapi is a hosted endpoint at https://billomat.usefulapi.io/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 · billomat.usefulapi.io
claude mcp add --transport http io-usefulapi-billomat 'https://billomat.usefulapi.io/mcp'
What is the Billomat MCP by usefulapi server?
Billomat MCP by usefulapi is listed in the public MCP registry as io.usefulapi/billomat. Read Billomat clients, invoices, offers, credit notes, reminders; create clients and draft invoices. This page covers its hosted endpoint (https://billomat.usefulapi.io/mcp).
Is the Billomat MCP by usefulapi server safe to use?
Billomat MCP by usefulapi scores 64 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 Billomat MCP by usefulapi server expose?
Billomat MCP by usefulapi exposes 34 tools: billomat_get_current_user, billomat_get_company, billomat_list_clients, billomat_get_client, billomat_list_articles, and 29 more. Their descriptions and schemas cost roughly 5,647 tokens of context every time the server is loaded.
Does the Billomat MCP by usefulapi server require authentication?
Yes. Billomat MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Billomat MCP by usefulapi server still maintained?
Billomat MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.