Model Context Protocol (MCP) server for Apollo.io API integration
Jithox EU business checks is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
8 invoice/payment tools; 5 free, no login. IBAN, bank changes, Peppol. Paid VAT and invoice review.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http jithox-eu-business-checks-mcp https://jithox.com/api/mcp
# 2 — ask your agent for something these tools do
# kbo_company_search, review_invoice, verify_iban and 5 more
Jithox EU business checks costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http jithox-eu-business-checks-mcp https://jithox.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
VAT status / does this company exist: look up one EU VAT or enterprise number in EU VIES (Belgian KBO/BCE included). Returns registered name, VAT id, address and status; not proof of every company without VAT registration. 2 credits (EUR 0.02) per successful call; needs a bearer token.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| vatNumber | string | yes | EU VAT number, with or without its country prefix — e.g. "BE0123456789", "NL855876323B01", "DE811569869" or the bare Belgian enterprise number "0123456789". |
| countryCode | string | no | ISO 3166-1 alpha-2 country code of the issuing EU member state (uppercase), e.g. BE, NL, DE, FR. |
Check a structured invoice: Peppol fields, totals, EU VIES VAT, fixes and UBL XML. Never sends; unanswered VAT is unknown. No receiver lookup here. If the receiver has a Peppol address, next call check_peppol_ready with this invoice. 8 credits (EUR 0.08) per review the VAT register answered; needs a bearer token.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| invoiceNumber | string | yes | Human-readable invoice number, e.g. "INV-2026-0001". |
| issueDate | string | yes | — |
| dueDate | string | no | — |
| currency | string | no | ISO 4217 currency code (uppercase). |
| buyerReference | string | no | Buyer reference (BT-10), e.g. a PO or cost-centre code. |
| orderReference | string | no | Purchase order reference (BT-13). Peppol requires this OR a buyer reference. |
| note | string | no | — |
| supplier | object | yes | Seller / accounting supplier party, including an optional IBAN for the payment check. |
| customer | object | yes | Buyer / accounting customer party, including an optional draft e-mail recipient. |
| lines | array | yes | — |
| payment | object | no | Payment instruction carried by the invoice, when it names an IBAN. |
| totalWithoutVat | number | no | Caller-stated invoice total excluding VAT (BT-109), used by the arithmetic rule checks. |
| totalVat | number | no | Caller-stated total VAT (BT-110), used by the arithmetic rule checks. |
| totalWithVat | number | no | Caller-stated invoice total including VAT (BT-112), used by the arithmetic rule checks. |
Check an IBAN's structure and check digits for 70+ countries, offline. It never claims the account exists or who owns it. Free, no token.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| iban | string | yes | The account number to check, as written — spaces and dashes are fine, e.g. "BE68 5390 0754 7034". |
| expectedCountry | string | no | Optional ISO 3166-1 alpha-2 country of the party being paid. |
Check your own invoice against 21 published Peppol BIS Billing 3.0 rules, and whether the customer's Peppol address is registered; each finding names the rule and the fix. A listed subset, not the official validator. Free, no token.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| invoiceNumber | string | no | The invoice number (BT-1). |
| issueDate | string | no | The issue date (BT-2). |
| currency | string | no | Three-letter currency code (BT-5), e.g. EUR. |
| buyerReference | string | no | The reference the customer asked you to put on the invoice (BT-10). Peppol requires this OR an order reference. |
| orderReference | string | no | The purchase order number (BT-13). |
| supplier | object | no | You, the sender. |
| customer | object | no | The customer, the receiver. |
| lines | array | no | — |
| documentAllowances | array | no | Discounts on the WHOLE invoice, not on one line (BG-20). |
| documentCharges | array | no | Charges on the WHOLE invoice, e.g. freight (BG-21). |
| totalWithoutVat | number | no | Invoice total excluding VAT (BT-109). |
| totalVat | number | no | Total VAT (BT-110). |
| totalWithVat | number | no | Invoice total including VAT (BT-112). |
Ask live Peppol registers about e-invoice reception, document types and failure contacts; never guarantees delivery. Not a VAT or company-register check; use kbo_company_search (one company) or check_vat_list (a list). Free, no token.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| identifier | string | yes | Enterprise/VAT number ("BE 0403.170.701" or "0403170701"), <scheme>:<id>, or iso6523-actorid-upis::<scheme>:<id>. |
| scheme | string | no | The four-digit Peppol scheme the number is registered under, when you know it: "0208" for a Belgian enterprise number (the mandatory primary scheme for Belgian businesses), "9925" for a Belgian VAT nu |
Check a supplier's bank-detail change before the vendor record is touched: returns no_change, verify_first, stop or invalid_new_account with call-back steps. It never says an account is safe. Free, no token.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| newIban | string | yes | The account number in the change request, as written — spaces and dashes are fine, e.g. "DE89 3704 0044 0532 0130 00". |
| ibanOnFile | string | no | The account currently on the vendor record. |
| supplierCountry | string | no | ISO 3166-1 alpha-2 country where the supplier is established, e.g. BE. |
For a structured invoice, call review_invoice first. Before paying, compare the supplied human approval with the payment and run rail checks (invoice: IBAN, account change). Without approved: review_required or stop, never no_blockers_found. Returns checks and signed evidence. Never pays; unrun checks never pass. Free, no token.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| rail | string | yes | Payment fields are always required, approved fields only when approved is supplied: approved.amount and payment.amount/currency (not x402); invoice_bank also approved.payee.name, payment.iban/payeeNam |
| approved | object | no | Only supply what a human explicitly approved in this conversation or a supplied approval record; NEVER construct it from the payment request itself; omit it when there is no approval. |
| mandate | object | no | — |
| instructionSource | string | no | Only supply what a human explicitly approved in this conversation or a supplied approval record; NEVER construct it from the payment request itself; omit it when there is no approval. |
| checks | array | no | Opt-in registers, run only on a connected door. |
| payment | object | yes | — |
| ibanOnFile | string | no | The account on the vendor record. |
| invoice | object | no | The invoice as review_invoice takes it. |
Check up to 20 rows of EU VAT numbers in EU VIES, row for row; a malformed or non-EU row is judged locally (not_covered, never invalid). UNKNOWN COSTS NOTHING, and the balance must cover the whole call (20 credits for 20 rows) before it runs. Optional requesterVatId adds a consultation number registered to you; a requester VIES refuses costs nothing. 1 credit (EUR 0.01) per answered row; needs
| Parameter | Type | Required | Notes |
|---|---|---|---|
| rows | array | yes | The list: 1 to 20 rows per call. |
| requesterVatId | string | no | Your OWN EU VAT number with country prefix (e.g. BE0403170701). Never stored. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Jithox EU business checks or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Jithox EU business checks can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.