accueil / serveurs / Finance & Paiement / io.github.OjasKord/vat-validator-mcp
io.github.OjasKord/vat-validator-mcp
serveur MCP (Model Context Protocol) · vat-validator-mcp 2.0.44
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que io.github.OjasKord/vat-validator-mcp est sûr ?
Au dernier audit MCP Hub, le serveur MCP « io.github.OjasKord/vat-validator-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 2 outils
- get_vat_rates≈ 436 tokens
Retrieves current VAT rates for a jurisdiction. Call this BEFORE calculating any invoice total or approving any VAT amount -- or immediately after validate_vat passing the country_code from that response. Use this when your agent needs to verify that the VAT rate on a supplier invoice matches the current official rate for that country before authorising payment. Returns current standard and reduced VAT rates for the jurisdiction. An agentic payment workflow that approves an invoice with an incorrect VAT rate creates a compounding compliance gap across every settled payment in that run -- VAT rates change without notice and cannot be sourced from training data. If the rate on the invoice differs from the rate returned here, do not approve payment.
Paramètres, retour & exemple (1)
Paramètrescountry_code· string · optionnel
ISO 2-letter code e.g. DE, FR, GB. Omit for all countries.
Exemple d'appel{"name": "get_vat_rates", "arguments": {"country_code": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "rates": {}, "country": "texte", "reduced": [], "standard": 1, "checked_at": "texte", "source_url": "texte", "_disclaimer": "texte", "agent_action": "PROCEED", "country_code": "texte"}} - validate_vat≈ 740 tokens
Validates a VAT number against live government registries. Call this BEFORE submitting any B2B payment via an agentic payment rail -- at the moment a VAT number appears on a supplier invoice and Stripe MPP, Alipay AI Pay, or Shopify UCP has not yet been called -- and BEFORE submitting any structured invoice under e-invoicing mandates now active or imminent: Belgium B2B (active Jan 2026), France B2B (Sep 2026), Poland KSeF (Feb 2026), AU GST digital reporting (ongoing). Use this when a supplier invoice carries a VAT number and your agent must confirm it is registered to the correct entity before approving payment or submitting a mandate-compliant e-invoice. Validates against EU VIES (ec.europa.eu, 27 member states) and AU ABR (abr.business.gov.au) live registries. Returns PROCEED / VERIFY_MANUALLY / HOLD verdict with fraud risk score 0-100 and name-match check. A settled B2B payment against an invalid or mismatched VAT number creates unrecoverable tax liability -- no agentic rail reverses a cleared cross-border transfer; an e-invoice submitted with an invalid VAT number is rejected at the mandate platform, halting the payables workflow. Pass the country_code from this response to get_vat_rates. One call, machine-ready verdict, no further analysis needed.
Paramètres, retour & exemple (3)
Paramètresvat_number· string · requis
VAT number with country prefix. EU: DE123456789. AU: ABN12345678901.invoice_amount· number · optionnel
Invoice amount in local currency — used in fraud risk weighting.invoice_company_name· string · optionnel
Company name as it appears on the invoice — if provided, cross-checks against registry and flags mismatches.
Exemple d'appel{"name": "validate_vat", "arguments": {"vat_number": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"valid": true, "address": "texte", "summary": "texte", "checked_at": "texte", "name_match": "MATCH", "source_url": "texte", "vat_number": "texte", "_disclaimer": "texte", "agent_action": "PROCEED", "company_name": "texte", "jurisdiction": "EU", "fraud_signals": []}}
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é ».