com.jithox/einvoice-readiness

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

Au dernier audit MCP Hub, le serveur MCP « com.jithox/einvoice-readiness » 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 5 outils

• get_einvoice_readiness≈ 732 tokens

  Readiness snapshot for YOUR canary workspace: one plain state, what is ready, what is missing, and the next safe step. Diagnostics, not a compliance certificate. Validation and readiness only; never sends a Peppol invoice and gives no legal, fiscal or compliance guarantee.

  Paramètres, retour & exemple (1)

  Paramètres

  • verifyWithProvider · boolean · optionnel
    Also confirm the bound legal entity with the provider (one provider call).

  Exemple d'appel

  {"name": "get_einvoice_readiness", "arguments": {"verifyWithProvider": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": {}, "billing": {}, "product": "texte", "receipt": "texte", "decision": "ready", "retryable": true, "capability": "texte", "provenance": {}, "generatedAt": "texte", "limitations": [], "schemaVersion": "texte", "receiptEnvelope": {}}}

• lookup_peppol_participant≈ 960 tokens

  Check whether a receiver is registered on the Peppol network and accepts BIS Billing 3.0 invoices, via the official SML/SMP discovery route when enabled (otherwise an honest mock that says so). Only status registered/not_registered is definitive; unavailable/not_configured are truthful and never a hidden "no". Provide vatId or endpointId (at least one) plus the receiver country. Lookup only — never a send action, and no send tool exists here. Validation and readiness only; never sends a Peppol invoice and gives no legal, fiscal or compliance guarantee.

  Paramètres, retour & exemple (4)

  Paramètres

  • vatId · string · optionnel
    VAT / enterprise number, e.g. "BE0123456749".
  • endpointId · string · optionnel
    Peppol endpoint identifier (GLN or scheme-specific id).
  • countryCode · string · requis · AT | BE | BG | HR | CY | CZ | DE | DK
    Receiver country (drives the scheme derivation).
  • endpointScheme · string · optionnel
    EAS scheme id. Derived when omitted (BE VAT → 0208, else 0088).

  Exemple d'appel

  {"name": "lookup_peppol_participant", "arguments": {"countryCode": "AT"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": {}, "billing": {}, "product": "texte", "receipt": "texte", "decision": "ready", "retryable": true, "capability": "texte", "provenance": {}, "generatedAt": "texte", "limitations": [], "schemaVersion": "texte", "receiptEnvelope": {}}}

• validate_invoice≈ 734 tokens

  Structurally validate a draft EU invoice and report machine-readable issues (schema problems, VAT-id format, date sanity, BIS 3.0 completeness, computed totals). Full report, never fails fast. Not legal approval. Validation and readiness only; never sends a Peppol invoice and gives no legal, fiscal or compliance guarantee.

  Paramètres, retour & exemple (1)

  Paramètres

  • invoice · object · requis
    The invoice payload to check.

  Exemple d'appel

  {"name": "validate_invoice", "arguments": {"invoice": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": {}, "billing": {}, "product": "texte", "receipt": "texte", "decision": "ready", "retryable": true, "capability": "texte", "provenance": {}, "generatedAt": "texte", "limitations": [], "schemaVersion": "texte", "receiptEnvelope": {}}}

• validate_vat_number≈ 780 tokens

  Deterministic structure/checksum validation of an EU VAT number (incl. the Belgian modulo-97 checksum) with the normalized identifier and a stable issue code. Format plausibility only — not a live VIES result. Validation and readiness only; never sends a Peppol invoice and gives no legal, fiscal or compliance guarantee.

  Paramètres, retour & exemple (2)

  Paramètres

  • vatNumber · string · requis
    A VAT number, e.g. "BE0123456749".
  • countryCode · string · optionnel
    ISO alpha-2, used only when the VAT has no prefix.

  Exemple d'appel

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

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": {}, "billing": {}, "product": "texte", "receipt": "texte", "decision": "ready", "retryable": true, "capability": "texte", "provenance": {}, "generatedAt": "texte", "limitations": [], "schemaVersion": "texte", "receiptEnvelope": {}}}

• verify_vat_vies≈ 785 tokens

  Check a VAT number's ACTIVE status against the official EU VIES source. Returns valid / invalid / invalid_input / unavailable with provenance (source, checkedAt). When VIES is unavailable it says so truthfully and makes no validity claim. Validation and readiness only; never sends a Peppol invoice and gives no legal, fiscal or compliance guarantee.

  Paramètres, retour & exemple (2)

  Paramètres

  • vatNumber · string · requis
    A VAT number, e.g. "BE0123456749".
  • countryCode · string · optionnel
    ISO alpha-2, used only when the VAT has no prefix.

  Exemple d'appel

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

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": {}, "billing": {}, "product": "texte", "receipt": "texte", "decision": "ready", "retryable": true, "capability": "texte", "provenance": {}, "generatedAt": "texte", "limitations": [], "schemaVersion": "texte", "receiptEnvelope": {}}}

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://mcp.jithox.com/mcp