e-Boekhouden MCP by usefulapi
REMOTE · E-BOEKHOUDEN.USEFULAPI.IO
Read e-Boekhouden relations, invoices, ledgers, bookings and products; create relations, invoices.
Available components
Last scanned (23 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 16 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 Usability78
- 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 3979 tokens (~159/item across 25 items; 25 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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 25 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 26 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.
- 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 +3
- 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 0
- 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 16 Oct 2026 · Probed https://e-boekhouden.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 e-boekhouden.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://e-boekhouden.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://e-boekhouden.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://e-boekhouden.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://e-boekhouden.usefulapi.io/mcp |
| Authorisation server | https://e-boekhouden.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://e-boekhouden.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/e-boekhouden/ |
| http (plaintext) | http://e-boekhouden.usefulapi.io/mcp | Inconclusive | 302 | http://e-boekhouden.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 →
eboekhouden_create_invoice Create an invoice ~256
Create a sales invoice for a relation. PERMANENT: the API cannot change or delete invoices afterwards, and an invoice number is used up. The invoice is created only: it is NOT e-mailed to the customer, NOT booked as a mutation and no direct debit is set. Needs relation_id, template_id (eboekhouden_list_invoice_templates), term_of_payment in days and at least one item with a ledger_id. Returns the new id and invoice number. POST /v1/invoice.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Invoice date yyyy-mm-dd (default today). |
| in_ex_vat | string | – | Whether price_per_unit includes (IN) or excludes (EX) VAT. |
| invoice_number | string | – | Invoice number; must end with a number. Generated when omitted. |
| items | array | yes | 1-200 invoice items. |
| reference | string | – | Payment reference. |
| relation_id | integer | yes | The relation id (from eboekhouden_list_relations). |
| template_id | integer | yes | The invoice template id (from eboekhouden_list_invoice_templates). |
| term_of_payment | integer | yes | Payment term in days. |
| text | string | – | Text on the invoice. |
No output schema declared.
No examples provided.
eboekhouden_create_product Create a product ~274
Create a product or service. Needs code, description, a sale VAT code and a ledger id, and exactly one of price_excl or price_incl. Returns the new id. POST /v1/product.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Whether the product is active. |
| code | string | yes | Product code (max 20). |
| cost_center_id | integer | – | Cost center id from eboekhouden_list_cost_centers. |
| description | string | yes | Product description. |
| group_id | integer | – | Product group id from eboekhouden_list_product_groups. |
| in_stock_management | boolean | – | Include in automatic stock management. |
| ledger_id | integer | yes | Revenue ledger id (from eboekhouden_list_ledgers). |
| price_excl | number | – | Price excluding VAT (not with price_incl). |
| price_incl | number | – | Price including VAT (not with price_excl). |
| purchase_price_excl | number | – | Purchase price excluding VAT. |
| unit_id | integer | – | Unit id from eboekhouden_list_units. |
| vat | string | yes | Sale VAT code of the account's country, e.g. HOOG_VERK_21, LAAG_VERK_9, BE_21_VERK or GEEN (purchase codes are refused by the API). |
No output schema declared.
No examples provided.
eboekhouden_create_relation Create a relation ~312
Create a new relation (customer or supplier) in the administration. Only name is required; the code is generated when omitted. Returns the new id and code. POST /v1/relation.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| bic | string | – | – |
| city | string | – | – |
| code | string | – | Relation code (max 15; generated when empty on create). |
| company_registration_number | string | – | Chamber of Commerce (KvK) number; digits only. |
| contact | string | – | Contact person. |
| country | string | – | – |
| email_address | string | – | – |
| email_address_invoice | string | – | Address invoices are sent to. |
| email_address_reminder | string | – | Address payment reminders are sent to. |
| gender | string | – | m = male, v = female, a = department. |
| iban | string | – | – |
| ledger_id | integer | – | Ledger id of this relation (from eboekhouden_list_ledgers). |
| mobile_phone_number | string | – | – |
| name | string | yes | The (company) name (max 100). |
| note | string | – | – |
| phone_number | string | – | – |
| postal_code | string | – | – |
| salutation | string | – | – |
| term_of_payment | integer | – | Default payment term in days. |
| type | string | – | Business (B, default) or Private (P). |
| vat_number | string | – | – |
| website | string | – | – |
No output schema declared.
No examples provided.
eboekhouden_get_cost_center Get a cost center ~46
One cost center. GET /v1/costcenter/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The cost center id (from eboekhouden_list_cost_centers). |
No output schema declared.
No examples provided.
eboekhouden_get_invoice Get an invoice ~48
One invoice with its items, amounts and relation. GET /v1/invoice/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The invoice id (from eboekhouden_list_invoices). |
No output schema declared.
No examples provided.
eboekhouden_get_ledger Get a ledger ~43
One ledger account. GET /v1/ledger/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The ledger id (from eboekhouden_list_ledgers). |
No output schema declared.
No examples provided.
eboekhouden_get_ledger_balance Get a ledger's balance ~116
The balance of one ledger, optionally per cost center and for a period (from/to). GET /v1/ledger/{id}/balance.
| Name | Type | Req | Description |
|---|---|---|---|
| cost_center_id | integer | – | Only mutations of this cost center. |
| from | string | – | Balance over the period starting at this date (the difference), instead of the actual balance. |
| id | integer | yes | The ledger id (from eboekhouden_list_ledgers). |
| to | string | – | The balance at this date, inclusive (default today). |
No output schema declared.
No examples provided.
eboekhouden_get_member Get a member (clubs and associations) ~46
One member; only available to clubs and associations. GET /v1/member/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The member id (from eboekhouden_list_members). |
No output schema declared.
No examples provided.
eboekhouden_get_mutation Get a mutation (booking) ~57
One mutation with its rows (ledger, VAT code, amount, relation, invoice number). GET /v1/mutation/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The mutation number (from eboekhouden_list_mutations). |
No output schema declared.
No examples provided.
eboekhouden_get_product Get a product ~51
One product with price, VAT code, ledger, unit and stock setting. GET /v1/product/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The product id (from eboekhouden_list_products). |
No output schema declared.
No examples provided.
eboekhouden_get_relation Get a relation ~65
One relation with all its fields (addresses, e-mail addresses, VAT and KvK number, IBAN, payment term, ledger). GET /v1/relation/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The relation id (from eboekhouden_list_relations). |
No output schema declared.
No examples provided.
eboekhouden_list_cost_centers List cost centers ~145
List cost centers (kostenplaatsen), optionally by parent id or description. Paged: pass next_offset as offset. GET /v1/costcenter.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Description. |
| limit | integer | – | Results per page, 1-2000 (default 50). |
| match | string | – | How the text filters match: exact (default), contains or starts_with (case-insensitive wildcard match; % and ? in the text are wildcards). |
| offset | integer | – | Number of results to skip (default 0). Use next_offset from the previous reply. |
| parent_id | string | – | Parent cost center id. |
No output schema declared.
No examples provided.
eboekhouden_list_email_templates List e-mail templates ~77
List e-mail templates. Paged: pass next_offset as offset. GET /v1/emailtemplate.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-2000 (default 50). |
| offset | integer | – | Number of results to skip (default 0). Use next_offset from the previous reply. |
No output schema declared.
No examples provided.
eboekhouden_list_invoice_templates List invoice templates ~183
List invoice templates (the template_id for eboekhouden_create_invoice), optionally by name, type (E editor, A advanced) or active. Paged: pass next_offset as offset. GET /v1/invoicetemplate.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Only active (true) or inactive (false) templates. |
| limit | integer | – | Results per page, 1-2000 (default 50). |
| match | string | – | How the text filters match: exact (default), contains or starts_with (case-insensitive wildcard match; % and ? in the text are wildcards). |
| name | string | – | Template name. |
| offset | integer | – | Number of results to skip (default 0). Use next_offset from the previous reply. |
| type | string | – | Editor (E) or advanced (A). |
No output schema declared.
No examples provided.
eboekhouden_list_invoices List or search invoices ~206
Search the invoices created in the invoicing module, by invoice number, relation or date (exact, or from/to). Paged: pass next_offset as offset. GET /v1/invoice.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Only this exact date (yyyy-mm-dd). |
| date_from | string | – | From this date, inclusive (yyyy-mm-dd). |
| date_to | string | – | Up to this date, inclusive (yyyy-mm-dd). |
| invoice_number | string | – | Invoice number. |
| limit | integer | – | Results per page, 1-2000 (default 50). |
| match | string | – | How the text filters match: exact (default), contains or starts_with (case-insensitive wildcard match; % and ? in the text are wildcards). |
| offset | integer | – | Number of results to skip (default 0). Use next_offset from the previous reply. |
| relation_id | integer | – | Only invoices of this relation. |
No output schema declared.
No examples provided.
eboekhouden_list_ledger_balances List all ledger balances ~103
The balances of all ledgers (a trial balance), optionally per cost center and for a period (from/to). GET /v1/ledger/balances.
| Name | Type | Req | Description |
|---|---|---|---|
| cost_center_id | integer | – | Only mutations of this cost center. |
| from | string | – | Balance over the period starting at this date (the difference), instead of the actual balance. |
| to | string | – | The balance at this date, inclusive (default today). |
No output schema declared.
No examples provided.
eboekhouden_list_ledgers List ledgers (chart of accounts) ~203
The ledger accounts (grootboekrekeningen): id, code, description and category (BAL balance, VW profit and loss, FIN, DEB, CRED, AF6, AF19, AFOVERIG, VOOR, BTWRC, AF). Use the id as ledger_id in other tools. Paged: pass next_offset as offset. GET /v1/ledger.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category, e.g. BAL, VW, FIN, DEB, CRED. |
| code | string | – | Ledger code. |
| limit | integer | – | Results per page, 1-2000 (default 50). |
| match | string | – | How the text filters match: exact (default), contains or starts_with (case-insensitive wildcard match; % and ? in the text are wildcards). |
| offset | integer | – | Number of results to skip (default 0). Use next_offset from the previous reply. |
No output schema declared.
No examples provided.
eboekhouden_list_members List members (clubs and associations) ~160
List members; only available to clubs and associations (others get error MEM_056). Paged: pass next_offset as offset. GET /v1/member.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City. |
| string | – | E-mail address. | |
| limit | integer | – | Results per page, 1-2000 (default 50). |
| match | string | – | How the text filters match: exact (default), contains or starts_with (case-insensitive wildcard match; % and ? in the text are wildcards). |
| member_number | string | – | Member number. |
| name | string | – | Name. |
| offset | integer | – | Number of results to skip (default 0). Use next_offset from the previous reply. |
No output schema declared.
No examples provided.
eboekhouden_list_mutations List or search mutations (bookings) ~291
Search the bookkeeping mutations: type 1 invoice received, 2 invoice sent, 3 invoice payment received, 4 invoice payment sent, 5 money received, 6 money sent, 7 general journal entry. Filter by type, mutation number, description, invoice number or date. Paged: pass next_offset as offset. GET /v1/mutation.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Only this exact date (yyyy-mm-dd). |
| date_from | string | – | From this date, inclusive (yyyy-mm-dd). |
| date_to | string | – | Up to this date, inclusive (yyyy-mm-dd). |
| description | string | – | Description. |
| id | integer | – | Mutation number. |
| invoice_number | string | – | Invoice number. |
| limit | integer | – | Results per page, 1-2000 (default 50). |
| match | string | – | How the text filters match: exact (default), contains or starts_with (case-insensitive wildcard match; % and ? in the text are wildcards). |
| offset | integer | – | Number of results to skip (default 0). Use next_offset from the previous reply. |
| type | integer | – | Mutation type 1-7 (1 invoice received, 2 invoice sent, 3 payment received, 4 payment sent, 5 money received, 6 money sent, 7 journal entry). |
No output schema declared.
No examples provided.
eboekhouden_list_outstanding_invoices List outstanding invoices ~182
Open (unpaid) invoices: debtors (D, sales invoices customers still owe) or creditors (C, purchase invoices still to be paid). Paged: pass next_offset as offset. GET /v1/mutation/invoice/outstanding.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_number | string | – | Only this invoice number. |
| kind | string | yes | D = debtors (customers owing you), C = creditors (suppliers you still owe). |
| limit | integer | – | Results per page, 1-2000 (default 50). |
| match | string | – | How the text filters match: exact (default), contains or starts_with (case-insensitive wildcard match; % and ? in the text are wildcards). |
| offset | integer | – | Number of results to skip (default 0). Use next_offset from the previous reply. |
No output schema declared.
No examples provided.
eboekhouden_list_product_groups List product groups ~23
All product groups. GET /v1/product/groups.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
eboekhouden_list_products List products ~159
List products and services (articles) with price, VAT code, ledger and unit, optionally by code or group code. Paged: pass next_offset as offset. GET /v1/product.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | Product code. |
| group_code | string | – | Product group code (from eboekhouden_list_product_groups). |
| limit | integer | – | Results per page, 1-2000 (default 50). |
| match | string | – | How the text filters match: exact (default), contains or starts_with (case-insensitive wildcard match; % and ? in the text are wildcards). |
| offset | integer | – | Number of results to skip (default 0). Use next_offset from the previous reply. |
No output schema declared.
No examples provided.
eboekhouden_list_relations List or search relations ~202
List relations (customers and suppliers of the administration), optionally filtered (filters combine with AND). Text filters match exactly unless match is contains or starts_with. Paged: pass next_offset as offset. GET /v1/relation.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | Primary city. |
| code | string | – | Relation code. |
| contact | string | – | Contact information. |
| string | – | E-mail address. | |
| limit | integer | – | Results per page, 1-2000 (default 50). |
| match | string | – | How the text filters match: exact (default), contains or starts_with (case-insensitive wildcard match; % and ? in the text are wildcards). |
| name | string | – | (Company) name. |
| offset | integer | – | Number of results to skip (default 0). Use next_offset from the previous reply. |
| type | string | – | Business (B) or Private (P). |
No output schema declared.
No examples provided.
eboekhouden_list_units List units ~139
List product units (piece, hour, ...) with their ids. Paged: pass next_offset as offset. GET /v1/unit.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-2000 (default 50). |
| match | string | – | How the text filters match: exact (default), contains or starts_with (case-insensitive wildcard match; % and ? in the text are wildcards). |
| offset | integer | – | Number of results to skip (default 0). Use next_offset from the previous reply. |
| plural | string | – | Plural form. |
| singular | string | – | Singular form. |
No output schema declared.
No examples provided.
eboekhouden_update_relation Update a relation ~375
Change fields of an existing relation. The tool first reads the relation, then sends its current values with your changes on top (the API requires name on every update), so fields you do not pass keep their values. This overwrites the current values of the fields you pass. GET + PATCH /v1/relation/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| bic | string | – | – |
| city | string | – | – |
| code | string | – | Relation code (max 15; generated when empty on create). |
| company_registration_number | string | – | Chamber of Commerce (KvK) number; digits only. |
| contact | string | – | Contact person. |
| country | string | – | – |
| email_address | string | – | – |
| email_address_invoice | string | – | Address invoices are sent to. |
| email_address_reminder | string | – | Address payment reminders are sent to. |
| gender | string | – | m = male, v = female, a = department. |
| iban | string | – | – |
| id | integer | yes | The relation id (from eboekhouden_list_relations). |
| inactive | boolean | – | Mark the relation inactive (true) or active (false). |
| ledger_id | integer | – | Ledger id of this relation (from eboekhouden_list_ledgers). |
| mobile_phone_number | string | – | – |
| name | string | – | The (company) name (max 100). |
| note | string | – | – |
| phone_number | string | – | – |
| postal_code | string | – | – |
| salutation | string | – | – |
| term_of_payment | integer | – | Default payment term in days. |
| type | string | – | Business (B, default) or Private (P). |
| vat_number | string | – | – |
| website | string | – | – |
No output schema declared.
No examples provided.
How do I install the e-Boekhouden MCP by usefulapi server?
e-Boekhouden MCP by usefulapi is a hosted endpoint at https://e-boekhouden.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 · e-boekhouden.usefulapi.io
claude mcp add --transport http io-usefulapi-e-boekhouden 'https://e-boekhouden.usefulapi.io/mcp'
What is the e-Boekhouden MCP by usefulapi server?
e-Boekhouden MCP by usefulapi is listed in the public MCP registry as io.usefulapi/e-boekhouden. Read e-Boekhouden relations, invoices, ledgers, bookings and products; create relations, invoices. This page covers its hosted endpoint (https://e-boekhouden.usefulapi.io/mcp).
Is the e-Boekhouden MCP by usefulapi server safe to use?
e-Boekhouden MCP by usefulapi scores 63 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 e-Boekhouden MCP by usefulapi server expose?
e-Boekhouden MCP by usefulapi exposes 25 tools: eboekhouden_list_relations, eboekhouden_get_relation, eboekhouden_list_invoices, eboekhouden_get_invoice, eboekhouden_list_outstanding_invoices, and 20 more. Their descriptions and schemas cost roughly 3,762 tokens of context every time the server is loaded.
Does the e-Boekhouden MCP by usefulapi server require authentication?
Yes. e-Boekhouden 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 e-Boekhouden MCP by usefulapi server still maintained?
e-Boekhouden MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.