Jithox payment preflight: check an invoice payment before your AI agent pays
REMOTE · JITHOX.COM · SCANNED SEP 28
Call preflight_payment before an agent pays an invoice: approval, IBAN, bank change; signed, free.
Available components
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1819 tokens (~227/item across 8 items; 8 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 Management0
- Stability check failed: schema churn in the 5 days we've observed: 12 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Jithox payment preflight: check an invoice payment before… MCP server?
Jithox payment preflight: check an invoice payment before… is a hosted endpoint at https://jithox.com/api/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 · jithox.com
claude mcp add --transport http com-jithox-jithox 'https://jithox.com/api/mcp'
{
"mcpServers": {
"com-jithox-jithox": {
"url": "https://jithox.com/api/mcp"
}
}
} {
"servers": {
"com-jithox-jithox": {
"type": "http",
"url": "https://jithox.com/api/mcp"
}
}
} [mcp_servers.com-jithox-jithox] url = "https://jithox.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-jithox-jithox": {
"type": "remote",
"url": "https://jithox.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-jithox-jithox --url 'https://jithox.com/api/mcp' --transport streamable-http
mcp_servers:
com-jithox-jithox:
url: "https://jithox.com/api/mcp" {
"McpServers": {
"com-jithox-jithox": {
"Transport": "http",
"Url": "https://jithox.com/api/mcp"
}
}
} assistant mcp add com-jithox-jithox -t streamable-http -u 'https://jithox.com/api/mcp'
{
"mcpServers": {
"com-jithox-jithox": {
"type": "http",
"url": "https://jithox.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 −1
- Stability: 0.07 → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “analyze_kbo_financials” was removed ▼ security
- Tool “check_vat_list_format” was removed ▼ security
- Tool “core_condition” was removed ▼ security
- Tool “draft_social_content” was removed ▼ security
- Tool “fetch_web_markdown” was removed ▼ security
- Tool “file_to_data_inspect” was removed ▼ security
- Tool “file_to_data_transform” was removed ▼ security
- Tool “format_peppol_invoice” was removed ▼ security
- Tool “generate_pdf_invoice” was removed ▼ security
- Tool “monitor_sources” was removed ▼ security
- Tool “parse_receipt_vision” was removed ▼ security
- Tool “transcribe_and_slice_audio” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “analyze_kbo_financials” rewrote its description, which is the text the model reads security
- Tool “check_payment_change” rewrote its description, which is the text the model reads security
- Tool “check_peppol_ready” rewrote its description, which is the text the model reads security
- Tool “check_vat_list” rewrote its description, which is the text the model reads security
- Tool “check_vat_list_format” rewrote its description, which is the text the model reads security
- Tool “core_condition” rewrote its description, which is the text the model reads security
- Tool “draft_social_content” rewrote its description, which is the text the model reads security
- Tool “fetch_web_markdown” rewrote its description, which is the text the model reads security
- Tool “file_to_data_inspect” rewrote its description, which is the text the model reads security
- Tool “file_to_data_transform” rewrote its description, which is the text the model reads security
- Tool “format_peppol_invoice” rewrote its description, which is the text the model reads security
- Tool “generate_pdf_invoice” rewrote its description, which is the text the model reads security
- Tool “kbo_company_search” rewrote its description, which is the text the model reads security
- Tool “lookup_peppol_participant” rewrote its description, which is the text the model reads security
- Tool “monitor_sources” rewrote its description, which is the text the model reads security
- Tool “parse_receipt_vision” rewrote its description, which is the text the model reads security
- Tool “review_invoice” rewrote its description, which is the text the model reads security
- Tool “transcribe_and_slice_audio” rewrote its description, which is the text the model reads security
- Tool “verify_iban” rewrote its description, which is the text the model reads security
- Tool coverage: 100% → 80% ▼ functional
- Tool coverage: 100% → 83% ▼ functional
- Schema quality: 275 → 221 ▲ functional
- Schema quality: 275 → 181 ▲ functional
- Tool “analyze_kbo_financials” now declares an output schema ▲ functional
- Tool “check_payment_change” now declares an output schema ▲ functional
- Tool “check_peppol_ready” now declares an output schema ▲ functional
- Tool “check_vat_list” now declares an output schema ▲ functional
- Tool “check_vat_list_format” now declares an output schema ▲ functional
- Tool “core_condition” now declares an output schema ▲ functional
- Tool “draft_social_content” now declares an output schema ▲ functional
- Tool “fetch_web_markdown” now declares an output schema ▲ functional
- Tool “file_to_data_inspect” now declares an output schema ▲ functional
- Tool “file_to_data_transform” now declares an output schema ▲ functional
- Tool “format_peppol_invoice” now declares an output schema ▲ functional
- Tool “generate_pdf_invoice” now declares an output schema ▲ functional
- Tool “kbo_company_search” now declares an output schema ▲ functional
- Tool “lookup_peppol_participant” now declares an output schema ▲ functional
- Tool “monitor_sources” now declares an output schema ▲ functional
- Tool “parse_receipt_vision” now declares an output schema ▲ functional
- Tool “review_invoice” now declares an output schema ▲ functional
- Tool “transcribe_and_slice_audio” now declares an output schema ▲ functional
- Tool “verify_iban” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- New tool “preflight_payment” functional
- “review_invoice” added an optional parameter “payment” cosmetic
- “review_invoice” added an optional parameter “totalVat” cosmetic
- “review_invoice” added an optional parameter “totalWithVat” cosmetic
- “review_invoice” added an optional parameter “totalWithoutVat” cosmetic
- “review_invoice” reworded the description of “customer” cosmetic
- “review_invoice” reworded the description of “supplier” cosmetic
- “check_payment_change” reworded the description of “ibanOnFile” cosmetic
- “check_payment_change” reworded the description of “supplierCountry” cosmetic
- “check_peppol_ready” reworded the description of “issueDate” cosmetic
- “check_peppol_ready” reworded the description of “lines” cosmetic
- “check_peppol_ready” reworded the description of “orderReference” cosmetic
- “check_peppol_ready” reworded the description of “totalWithoutVat” cosmetic
- “check_vat_list” reworded the description of “requesterVatId” cosmetic
- “check_vat_list” reworded the description of “rows” cosmetic
- “check_vat_list_format” reworded the description of “rows” cosmetic
- “core_condition” reworded the description of “label” cosmetic
- “draft_social_content” reworded the description of “topic” cosmetic
- “file_to_data_inspect” reworded the description of “content” cosmetic
- “file_to_data_inspect” reworded the description of “contentBase64” cosmetic
- “file_to_data_inspect” reworded the description of “fileName” cosmetic
- “file_to_data_inspect” reworded the description of “headerRow” cosmetic
- “file_to_data_inspect” reworded the description of “sheet” cosmetic
- “file_to_data_transform” reworded the description of “content” cosmetic
- “file_to_data_transform” reworded the description of “contentBase64” cosmetic
- “file_to_data_transform” reworded the description of “fileName” cosmetic
- “file_to_data_transform” reworded the description of “headerRow” cosmetic
- “file_to_data_transform” reworded the description of “limit” cosmetic
- “file_to_data_transform” reworded the description of “offset” cosmetic
- “file_to_data_transform” reworded the description of “sheet” cosmetic
- “format_peppol_invoice” reworded the description of “currency” cosmetic
- “format_peppol_invoice” reworded the description of “dueDate” cosmetic
- “format_peppol_invoice” reworded the description of “issueDate” cosmetic
- “format_peppol_invoice” reworded the description of “lines” cosmetic
- “format_peppol_invoice” reworded the description of “note” cosmetic
- “generate_pdf_invoice” reworded the description of “currency” cosmetic
- “generate_pdf_invoice” reworded the description of “lines” cosmetic
- “generate_pdf_invoice” reworded the description of “notes” cosmetic
- “kbo_company_search” reworded the description of “countryCode” cosmetic
- “lookup_peppol_participant” reworded the description of “scheme” cosmetic
- “review_invoice” reworded the description of “currency” cosmetic
- “review_invoice” reworded the description of “dueDate” cosmetic
- “review_invoice” reworded the description of “issueDate” cosmetic
- “review_invoice” reworded the description of “lines” cosmetic
- “review_invoice” reworded the description of “note” cosmetic
- “verify_iban” reworded the description of “expectedCountry” cosmetic
- “draft_social_content” dropped the optional parameter “avoidSignatures” cosmetic
- “draft_social_content” dropped the optional parameter “campaign” cosmetic
- “draft_social_content” dropped the optional parameter “contract” cosmetic
- “draft_social_content” dropped the optional parameter “feedbackNote” cosmetic
- “draft_social_content” dropped the optional parameter “format” cosmetic
- “draft_social_content” dropped the optional parameter “learnings” cosmetic
- “draft_social_content” dropped the optional parameter “minAnchors” cosmetic
- “draft_social_content” dropped the optional parameter “ownerUpdate” cosmetic
- “draft_social_content” dropped the optional parameter “pillar” cosmetic
- “draft_social_content” dropped the optional parameter “recentNote” cosmetic
- “draft_social_content” dropped the optional parameter “requireFreshBasis” cosmetic
- “draft_social_content” dropped the optional parameter “signals” cosmetic
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- “format_peppol_invoice” added an optional parameter “orderReference” cosmetic
- “review_invoice” added an optional parameter “orderReference” cosmetic
- 23 Sept 26 71
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 28 Sept 2026 · Probed https://jithox.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.jithox.com | CN=YR2,O=Let's Encrypt,C=US | 30 Aug 2026 | 28 Nov 2026 | RSA 2048 | SHA256-RSA | 69263dd4105dcf90c36a1fc86fd18fef5ce |
| SANs: *.jithox.com, jithox.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of jithox.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| jithox.com. | absent | 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=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(self) |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://jithox.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://jithox.com/api/mcp | HTTPS enforced | 308 | https://jithox.com/api/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 →
check_payment_change ~144
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ibanOnFile | string | – | The account currently on the vendor record. |
| 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". |
| supplierCountry | string | – | ISO 3166-1 alpha-2 country where the supplier is established, e.g. BE. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| evidence | object | – | Signed decision evidence, present when a signing key is configured. |
| kind | string | yes | – |
No examples provided.
check_peppol_ready ~288
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.
| Name | Type | Req | Description |
|---|---|---|---|
| buyerReference | string | – | The reference the customer asked you to put on the invoice (BT-10). Peppol requires this OR an order reference. |
| currency | string | – | Three-letter currency code (BT-5), e.g. EUR. |
| customer | object | – | The customer, the receiver. |
| documentAllowances | array | – | Discounts on the WHOLE invoice, not on one line (BG-20). |
| documentCharges | array | – | Charges on the WHOLE invoice, e.g. freight (BG-21). |
| invoiceNumber | string | – | The invoice number (BT-1). |
| issueDate | string | – | The issue date (BT-2). |
| lines | array | – | – |
| orderReference | string | – | The purchase order number (BT-13). |
| supplier | object | – | You, the sender. |
| totalVat | number | – | Total VAT (BT-110). |
| totalWithVat | number | – | Invoice total including VAT (BT-112). |
| totalWithoutVat | number | – | Invoice total excluding VAT (BT-109). |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| kind | string | yes | – |
No examples provided.
check_vat_list ~159
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 a bearer token.
| Name | Type | Req | Description |
|---|---|---|---|
| requesterVatId | string | – | Your OWN EU VAT number with country prefix (e.g. BE0403170701). Never stored. |
| rows | array | yes | The list: 1 to 20 rows per call. |
| Name | Type | Req | Description |
|---|---|---|---|
| billing | object | yes | – |
| data | object | yes | – |
| kind | string | yes | – |
No examples provided.
kbo_company_search ~154
Look up an EU company by VAT or enterprise number in the EU VIES register, Belgian KBO/BCE included: name, VAT id, address, status. 2 credits (EUR 0.02) per successful call; needs a bearer token.
| Name | Type | Req | Description |
|---|---|---|---|
| countryCode | string | – | ISO 3166-1 alpha-2 country code of the issuing EU member state (uppercase), e.g. BE, NL, DE, FR. |
| vatNumber | string | yes | EU VAT number, with or without its country prefix — e.g. "BE0123456789", "NL855876323B01", "DE811569869" or the bare Belgian enterprise number "0123456789". |
| Name | Type | Req | Description |
|---|---|---|---|
| billing | object | yes | – |
| data | object | yes | – |
| kind | string | yes | – |
No examples provided.
lookup_peppol_participant ~164
Ask the live Peppol registers whether a third party can receive e-invoices, which document types, and who to call when a send fails. Never a promise that an invoice arrives. Free, no token.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | The customer's enterprise or VAT number, as written on the invoice — "BE 0403.170.701", "0403170701" and "BE0403170701" are all accepted. |
| scheme | string | – | 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 n… |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| kind | string | yes | – |
No examples provided.
preflight_payment ~247
Call once before you move money for a person: compares what they approved (payee, amount, currency) with what is about to be paid and runs the rail's checks (invoice: IBAN, account change). Returns stop, review_required or no_blockers_found with every check and signed evidence. Never pays; a check that did not run is never a pass. Free, no token.
| Name | Type | Req | Description |
|---|---|---|---|
| approved | object | yes | – |
| checks | array | – | Opt-in registers, run only on a connected door. |
| ibanOnFile | string | – | The account on the vendor record. |
| instructionSource | string | – | – |
| invoice | object | – | The invoice as review_invoice takes it. |
| mandate | object | – | – |
| payment | object | yes | – |
| rail | string | yes | Required: approved.amount and payment.amount/currency (not x402); invoice_bank also approved.payee.name, payment.iban/payeeName; card_or_giftcard approved.payee.merchant, payment.merchant/instrument;… |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| evidence | object | – | Signed decision evidence, present when a signing key is configured. |
| kind | string | yes | – |
No examples provided.
review_invoice ~360
Check one structured invoice before it is sent: Peppol fields, totals and both VAT numbers in EU VIES, with a fix per finding and the UBL XML. It never sends, and a VAT check VIES did not answer is `unknown`, never a pass. It does not look the receiver up: check_peppol_ready does. 8 credits (EUR 0.08) per review the VAT register answered; needs a bearer token.
| Name | Type | Req | Description |
|---|---|---|---|
| buyerReference | string | – | Buyer reference (BT-10), e.g. a PO or cost-centre code. |
| currency | string | – | ISO 4217 currency code (uppercase). |
| customer | object | yes | Buyer / accounting customer party, including an optional draft e-mail recipient. |
| dueDate | string | – | – |
| invoiceNumber | string | yes | Human-readable invoice number, e.g. "INV-2026-0001". |
| issueDate | string | yes | – |
| lines | array | yes | – |
| note | string | – | – |
| orderReference | string | – | Purchase order reference (BT-13). Peppol requires this OR a buyer reference. |
| payment | object | – | Payment instruction carried by the invoice, when it names an IBAN. |
| supplier | object | yes | Seller / accounting supplier party, including an optional IBAN for the payment check. |
| totalVat | number | – | Caller-stated total VAT (BT-110), used by the arithmetic rule checks. |
| totalWithVat | number | – | Caller-stated invoice total including VAT (BT-112), used by the arithmetic rule checks. |
| totalWithoutVat | number | – | Caller-stated invoice total excluding VAT (BT-109), used by the arithmetic rule checks. |
| Name | Type | Req | Description |
|---|---|---|---|
| billing | object | yes | – |
| data | object | yes | – |
| kind | string | yes | – |
No examples provided.
verify_iban ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| expectedCountry | string | – | Optional ISO 3166-1 alpha-2 country of the party being paid. |
| iban | string | yes | The account number to check, as written — spaces and dashes are fine, e.g. "BE68 5390 0754 7034". |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| kind | string | yes | – |
No examples provided.
What is the Jithox payment preflight: check an invoice payment before… MCP server?
Jithox payment preflight: check an invoice payment before… is an MCP server listed in the public MCP registry as com.jithox/jithox. Call preflight_payment before an agent pays an invoice: approval, IBAN, bank change; signed, free. This page covers its hosted endpoint (https://jithox.com/api/mcp).
Is the Jithox payment preflight: check an invoice payment before… MCP server safe to use?
Jithox payment preflight: check an invoice payment before… scores 71 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 Jithox payment preflight: check an invoice payment before… MCP server expose?
Jithox payment preflight: check an invoice payment before… exposes 8 tools: kbo_company_search, review_invoice, verify_iban, check_peppol_ready, lookup_peppol_participant, and 3 more. Their descriptions and schemas cost roughly 1,620 tokens of context every time the server is loaded.
Does the Jithox payment preflight: check an invoice payment before… MCP server require authentication?
No. We connected to Jithox payment preflight: check an invoice payment before… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Jithox payment preflight: check an invoice payment before… MCP server still maintained?
Jithox payment preflight: check an invoice payment before… is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.