com.jithox/jithox

Est-ce que com.jithox/jithox est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.jithox/jithox » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 8 outils

• check_payment_change≈ 304 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • newIban · string · requis
    The account number in the change request, as written — spaces and dashes are fine, e.g. "DE89 3704 0044 0532 0130 00".
  • ibanOnFile · string · optionnel
    The account currently on the vendor record.
  • supplierCountry · string · optionnel
    ISO 3166-1 alpha-2 country where the supplier is established, e.g. BE.

  Exemple d'appel

  {"name": "check_payment_change", "arguments": {"newIban": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": {}, "kind": "texte", "evidence": {}}}

• check_peppol_ready≈ 1039 tokens

  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.

  Paramètres, retour & exemple (13)

  Paramètres

  • lines · array · optionnel
  • currency · string · optionnel
    Three-letter currency code (BT-5), e.g. EUR.
  • customer · object · optionnel
    The customer, the receiver.
  • supplier · object · optionnel
    You, the sender.
  • totalVat · number · optionnel
    Total VAT (BT-110).
  • issueDate · string · optionnel
    The issue date (BT-2).
  • totalWithVat · number · optionnel
    Invoice total including VAT (BT-112).
  • invoiceNumber · string · optionnel
    The invoice number (BT-1).
  • buyerReference · string · optionnel
    The reference the customer asked you to put on the invoice (BT-10). Peppol requires this OR an order reference.
  • orderReference · string · optionnel
    The purchase order number (BT-13).
  • documentCharges · array · optionnel
    Charges on the WHOLE invoice, e.g. freight (BG-21).
  • totalWithoutVat · number · optionnel
    Invoice total excluding VAT (BT-109).
  • documentAllowances · array · optionnel
    Discounts on the WHOLE invoice, not on one line (BG-20).

  Exemple d'appel

  {"name": "check_peppol_ready", "arguments": {"lines": [], "currency": "texte", "customer": {}, "supplier": {}, "totalVat": 1, "issueDate": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": {}, "kind": "texte"}}

• check_vat_list≈ 375 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • rows · array · requis
    The list: 1 to 20 rows per call.
  • requesterVatId · string · optionnel
    Your OWN EU VAT number with country prefix (e.g. BE0403170701). Never stored.

  Exemple d'appel

  {"name": "check_vat_list", "arguments": {"rows": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": {}, "kind": "texte", "billing": {}}}

• kbo_company_search≈ 287 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • vatNumber · string · requis
    EU VAT number, with or without its country prefix — e.g. "BE0123456789", "NL855876323B01", "DE811569869" or the bare Belgian enterprise number "0123456789".
  • countryCode · string · optionnel
    ISO 3166-1 alpha-2 country code of the issuing EU member state (uppercase), e.g. BE, NL, DE, FR.

  Exemple d'appel

  {"name": "kbo_company_search", "arguments": {"vatNumber": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": {}, "kind": "texte", "billing": {}}}

• lookup_peppol_participant≈ 290 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • scheme · string · optionnel
    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 number, "0192" for a Norwegian organisation number.
  • identifier · string · requis
    Enterprise/VAT number ("BE 0403.170.701" or "0403170701"), <scheme>:<id>, or iso6523-actorid-upis::<scheme>:<id>.

  Exemple d'appel

  {"name": "lookup_peppol_participant", "arguments": {"identifier": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": {}, "kind": "texte"}}

• preflight_payment≈ 1026 tokens

  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.

  Paramètres, retour & exemple (8)

  Paramètres

  • rail · string · requis · invoice_bank | x402 | card_or_giftcard | crypto_bridge
    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/payeeName; card_or_giftcard approved.payee.merchant, payment.merchant/instrument; crypto_bridge approved.payee.merchant, payment.provider/merchant; x402 approved.amountAtomic/asset/network/payee.payTo, payment.challenge/resourceUrl.
  • checks · array · optionnel
    Opt-in registers, run only on a connected door.
  • invoice · object · optionnel
    The invoice as review_invoice takes it.
  • mandate · object · optionnel
  • payment · object · requis
  • approved · object · optionnel
    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.
  • ibanOnFile · string · optionnel
    The account on the vendor record.
  • instructionSource · string · optionnel · human | ingested_content | third_party
    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.

  Exemple d'appel

  {"name": "preflight_payment", "arguments": {"rail": "invoice_bank", "payment": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": {}, "kind": "texte", "evidence": {}}}

• review_invoice≈ 1202 tokens

  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.

  Paramètres, retour & exemple (14)

  Paramètres

  • note · string · optionnel
  • lines · array · requis
  • dueDate · string · optionnel
  • payment · object · optionnel
    Payment instruction carried by the invoice, when it names an IBAN.
  • currency · string · optionnel
    ISO 4217 currency code (uppercase).
  • customer · object · requis
    Buyer / accounting customer party, including an optional draft e-mail recipient.
  • supplier · object · requis
    Seller / accounting supplier party, including an optional IBAN for the payment check.
  • totalVat · number · optionnel
    Caller-stated total VAT (BT-110), used by the arithmetic rule checks.
  • issueDate · string · requis
  • totalWithVat · number · optionnel
    Caller-stated invoice total including VAT (BT-112), used by the arithmetic rule checks.
  • invoiceNumber · string · requis
    Human-readable invoice number, e.g. "INV-2026-0001".
  • buyerReference · string · optionnel
    Buyer reference (BT-10), e.g. a PO or cost-centre code.
  • orderReference · string · optionnel
    Purchase order reference (BT-13). Peppol requires this OR a buyer reference.
  • totalWithoutVat · number · optionnel
    Caller-stated invoice total excluding VAT (BT-109), used by the arithmetic rule checks.

  Exemple d'appel

  {"name": "review_invoice", "arguments": {"lines": [], "customer": {}, "supplier": {}, "issueDate": "texte", "invoiceNumber": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": {}, "kind": "texte", "billing": {}}}

• verify_iban≈ 207 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • iban · string · requis
    The account number to check, as written — spaces and dashes are fine, e.g. "BE68 5390 0754 7034".
  • expectedCountry · string · optionnel
    Optional ISO 3166-1 alpha-2 country of the party being paid.

  Exemple d'appel

  {"name": "verify_iban", "arguments": {"iban": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": {}, "kind": "texte"}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://jithox.com/api/mcp