Lerider EU Compliance Checks

7 verificações de conformidade da UE com pagamento por resposta para agentes de IA — fraude com IBAN/faturas, IVA (VIES), licença financeira e listas de alerta (ESMA/EBA/MiCA), EORI, TIN, assinaturas eIDAS e validação de faturas eletrônicas. Vereditos ALLOW/REVIEW/BLOCK com justificativas.

Servidor MCP hospedado

npx add-mcp 'https://mcp.apify.com?tools=lerider/payee-check,lerider/eu-vat-validator,lerider/eu-licence-check,lerider/eori-validator,lerider/eu-tin-validator,lerider/eidas-signature-check,lerider/einvoice-validator'

Instala no Claude Code, Codex, Cursor e outros

Documentação

EU Compliance Actors

Source code of the EU compliance checks that Lerider Technologies runs on the Apify Store. You can read exactly what each check does with your data, run the tests, or host it yourself. The hosted versions are pay-per-answer: no subscription, and failed or unanswered checks are free.

FolderStore pageWhat it checksSource
eu-vat-validatorEU VAT ValidatorEU VAT numbers live in VIES, name matchopen
eu-id-validatorsEORI Validator · EU TIN ValidatorEORI numbers (EU EOS) and tax ids (EU TIN service)open
eidas-checkeIDAS Signature ValidatorSigned PDFs and XML against the EU trusted listsopen
einvoice-validatorE-Invoice ValidatorXRechnung, ZUGFeRD / Factur-X, Peppol BIS against the official rule setsopen
licence-checkEU Financial License CheckFirms in ESMA, EBA, MiCA and ECB registers and on national warning listsopen (data snapshot not included)
—Payee CheckInvoice and payment-fraud check before paying an IBANclosed, see below

Why Payee Check is closed

Payee Check looks for the signs of invoice and CEO fraud: a changed bank account, pressure wording, look-alike names. Publishing the exact rules would show fraudsters what to avoid. So that one stays closed. Everything else we run is here, so you can judge how we build before trusting the one you can't read. The parts it shares with the VAT validator (VAT number formats, VIES and Peppol Directory lookups, name matching) are open, in eu-vat-validator/eu_common/.

Principles

  • No data kept. Inputs are checked and returned, never stored or logged. VIES answers can contain personal data (sole traders); they live only in a 24-hour in-memory cache inside one run.
  • Fail closed. If an official register or service doesn't answer, the result says so (unavailable or REVIEW), never a pass. Each Store page lists exactly what is and isn't charged.
  • Official sources only. Every answer names the register that gave it and when.

Running a check yourself

Each folder is a self-contained Apify Actor: .actor/ holds the Dockerfile and input/output schemas, and the Python package next to it holds the logic. Tests run offline:

cd eu-vat-validator && python3 -m unittest discover tests

Some folders need extra packages (requirements-actor.txt) or a one-off build step: the e-invoice rule sets and the eIDAS trusted lists are downloaded and verified at build time. The licence check needs a register snapshot in data/ (built with python3 -m licence_check.index build from the register history we record every day). That history is not part of this repo, so the licence check can be read and tested here, but not run as is.

Licence

Apache-2.0 for our code (see LICENSE and NOTICE). Test fixtures and downloaded rule sets keep their own licences, listed next to them.

Found a way to fool a check? See SECURITY.md. Questions: hello@lerider.com.