io.github.zifengw/eu-business-data-mcp

Est-ce que io.github.zifengw/eu-business-data-mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.zifengw/eu-business-data-mcp » 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 12 outils

• check_fr_pa_registry≈ 256 tokens

  Is this e-invoicing platform on France's official list of Plateformes Agréées (PA)? name = platform or company name (e.g. 'Pennylane'), website = its site (e.g. 'https://www.acubeapi.com/'); give at least one. Checks the DGFiP lists on impots.gouv.fr: registered PAs (with registration date) and operators awaiting interoperability tests. Returns on_official_list, status (approved | awaiting_interop_tests | possible_match | not_found), scored matches, list date and the official source. Use for supplier due diligence before the French reform (receive from 1 Sep 2026, SMEs issue from 1 Sep 2027). A 'solution compatible' is not a PA itself. Unofficial copy; the official lists prevail.

  Paramètres, retour & exemple (3)

  Paramètres

  • name · string · optionnel
  • limit · integer · optionnel
  • website · string · optionnel

  Exemple d'appel

  {"name": "check_fr_pa_registry", "arguments": {"name": "texte", "limit": 1, "website": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• create_einvoice≈ 206 tokens

  Create a validated EU e-invoice (UBL 2.1) from simple JSON. invoice = {format: en16931|xrechnung|peppol-bis3, invoice_number, issue_date (YYYY-MM-DD), due_date?, tax_point_date?, delivery_date?, currency (EUR), buyer_reference?, seller: {name, vat_id, street, city, postal_code, country, email, phone, contact_name, company_id?, company_id_scheme?, legal_form?}, buyer: {...}, lines: [{description, quantity, unit_price, unit?, vat_category (S|Z|E|AE|K|G|O), vat_rate}], payment: {iban, bic?, terms?}}. Totals and VAT breakdown are computed; returns {valid, xml, totals, errors}.

  Paramètres, retour & exemple (1)

  Paramètres

  • invoice · object · requis

  Exemple d'appel

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

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• due_diligence_report≈ 156 tokens

  Counterparty due-diligence report in one call: VIES VAT, official business register, EU/UN/OFAC/UK sanctions, EC EORI, GLEIF LEI and Peppol e-invoice route, with deterministic risk flags, 0-100 risk score, pass/review/fail verdict, sources and UTC timestamp. company: VAT ID (best), registry number or name; country: ISO code for names.

  Paramètres, retour & exemple (2)

  Paramètres

  • company · string · requis
  • country · string · optionnel

  Exemple d'appel

  {"name": "due_diligence_report", "arguments": {"company": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• einvoice_route≈ 133 tokens

  'Can I e-invoice this company?' id = EU VAT number (e.g. 'BE0403170701') or Peppol id ('0208:0403170701'). Returns VIES VAT status, Peppol Directory registration (BIS 3 invoice support), the country's B2B e-invoice mandate (dates, format, source) and the recommended format for create_einvoice. France's PPF directory is not included yet.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis

  Exemple d'appel

  {"name": "einvoice_route", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• kyb_check≈ 169 tokens

  One-call KYB check of a supplier/customer: EU VAT validation (VIES) + official business register + EU/UN/OFAC/UK sanctions screening, returning a pass / review / fail verdict with reasons. company: a VAT ID ('FR40303265045'), a company name, or a registry id; country: optional ISO code (e.g. 'NO').

  Paramètres, retour & exemple (3)

  Paramètres

  • company · string · requis
  • country · string · optionnel
  • requester · ? · optionnel

  Exemple d'appel

  {"name": "kyb_check", "arguments": {"company": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• lookup_company≈ 183 tokens

  Look up a company in official European business registers by name or registry number. country: FR (SIREN), NO (org.nr), FI (Y-tunnus), CZ (ICO), PL (KRS number), EE, or any other ISO code / 'LEI' (GLEIF). Returns legal name, ID, status/active, address, VAT ID, activity code and official source link. Use to confirm a company exists and is active, find its registry number, or map a name to a VAT ID.

  Paramètres, retour & exemple (3)

  Paramètres

  • limit · integer · optionnel
  • query · string · requis
  • country · string · optionnel

  Exemple d'appel

  {"name": "lookup_company", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• screen_sanctions≈ 188 tokens

  Screen a person or company name against official EU, UN, OFAC SDN and UK sanctions lists. Fuzzy matching with transliteration; returns candidate matches with 0-100 scores, list, programme, DOB. A potential match needs human review; this is a screening aid, not legal advice.

  Paramètres, retour & exemple (4)

  Paramètres

  • name · string · requis
  • country · ? · optionnel
  • threshold · number · optionnel
  • birth_year · ? · optionnel

  Exemple d'appel

  {"name": "screen_sanctions", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• send_einvoice_sandbox≈ 232 tokens

  SANDBOX ONLY - never reaches a real buyer. Runs the full send flow on an invoice (same JSON as create_einvoice): VIES check of the buyer VAT, sanctions screen of the buyer name, EN 16931 create + validate, route lookup (Peppol/mandate), transport hand-off and an Ed25519-signed evidence receipt (JWS). transport: "mock" (simulated, default), "recommand" or "e-invoice-be" (the UBL is really submitted to that Peppol access point's sandbox, addressed to W System's own sandbox company; the partner document id is returned). Use it to build and test an integration before live sending exists.

  Paramètres, retour & exemple (2)

  Paramètres

  • invoice · object · requis
  • transport · string · optionnel

  Exemple d'appel

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

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• validate_einvoice≈ 217 tokens

  Validate an EU e-invoice XML (UBL 2.1 Invoice/CreditNote or UN/CEFACT CII, e.g. XRechnung, Factur-X/ZUGFeRD XML) against the official CEN EN 16931 rules and, for XRechnung, the KoSIT XRechnung 3.0 rules. Returns valid, and every error with its rule ID (e.g. BR-CO-10), a plain-English message, XPath and a fix hint. rules: auto | en16931 | xrechnung. Slovak sellers also get eFaktúra field checks (FR SR transposition v1.12, warnings with ruleset SK-FS); Norwegian sellers get NO-LAW field checks. Peppol-specific rules are not checked yet. For PDFs use the REST endpoint POST /einvoice/validate.

  Paramètres, retour & exemple (2)

  Paramètres

  • xml · string · requis
  • rules · string · optionnel

  Exemple d'appel

  {"name": "validate_einvoice", "arguments": {"xml": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• verify_batch≈ 190 tokens

  Validate up to 100 EU VAT numbers in one call via VIES (supplier/customer list cleanup, onboarding, invoice runs). Same per-item result as verify_vat; items with member_state_unavailable should be retried later.

  Paramètres, retour & exemple (2)

  Paramètres

  • vats · array · requis
  • requester · ? · optionnel

  Exemple d'appel

  {"name": "verify_batch", "arguments": {"vats": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": []}}

• verify_eori≈ 153 tokens

  Validate an EU EORI (customs Economic Operators Registration and Identification) number, e.g. 'SE5560360793', 'DE1234567890123', against the official European Commission EOS service. Use for import/export, customs declarations and freight-forwarder onboarding. Returns valid/invalid and trader name/address only when the trader consented to publication. UK (GB) EORIs are not in EOS (HMRC checks those); XI EORIs are.

  Paramètres, retour & exemple (1)

  Paramètres

  • eori · string · requis

  Exemple d'appel

  {"name": "verify_eori", "arguments": {"eori": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• verify_eori_batch≈ 141 tokens

  Validate up to 100 EU EORI numbers in one call via the official EC EOS service (customs / import-export KYB).

  Paramètres, retour & exemple (1)

  Paramètres

  • eoris · array · requis

  Exemple d'appel

  {"name": "verify_eori_batch", "arguments": {"eoris": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": []}}

• verify_vat≈ 252 tokens

  Validate an EU VAT number against the official European Commission VIES service (27 EU states + XI Northern Ireland). Use when asked whether a VAT ID is valid/active, before zero-rated reverse-charge B2B invoices, or to get a company's registered name/address from its VAT number. Input: VAT with country prefix, e.g. 'IE6388047V', 'DE811193231' (spaces/dots ok). Returns status: valid | invalid | invalid_format | member_state_unavailable (VIES/member state down - retry later, valid=null) | error, plus name, address (if the member state discloses them; DE/ES often don't) and consultation_number (audit proof) when requester is set. For GB VAT numbers use HMRC instead; for >1 number use verify_batch.

  Paramètres, retour & exemple (2)

  Paramètres

  • vat · string · requis
  • requester · ? · optionnel

  Exemple d'appel

  {"name": "verify_vat", "arguments": {"vat": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

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://api.wsystem.dev/mcp/