Skip to main content
Glama
cmendezs

mcp-einvoicing-ae

Related Servers

Alternatives to mcp-einvoicing-ae

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Model Context Protocol (MCP) server for Singapore Electronic Invoicing (InvoiceNow / PINT-SG / Peppol 5-Corner Model). Provides tools to validate, generate, and explore API specifications for IRAS / Peppol interoperability.
      17
      162 PyPI
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      Model Context Protocol (MCP) server for French Electronic Invoicing (NF XP Z12-013). Provide tools to validate, generate, and explore API specifications for PDP/OD interoperability.
      2
      34
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      Model Context Protocol (MCP) server for Italian Electronic Invoicing (FatturaPA / SDI). Provide tools to validate, generate, and explore API specifications for Sistema di Interscambio (SDI) interoperability.
      43
      1
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Model Context Protocol (MCP) server for Polish Electronic Invoicing (KSeF / FA(2)). Provides tools to validate, generate, and explore API specifications for KSeF interoperability.
      10
      181 PyPI
      3
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      Model Context Protocol (MCP) server for Mexican Electronic Invoicing (CFDI 4.0, Complemento de Pagos 2.0). Provide tools to validate, generate, and explore API specifications for SAT/PAC interoperability.
      6
      150 PyPI
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      Model Context Protocol (MCP) server for Belgian Electronic Invoicing (Peppol BIS 3.0 / PINT-BE / Mercurius). Provides tools to validate, generate, and transform UBL 2.1 e-invoices, and look up BCE/KBO enterprise data and Peppol participants.
      50
      Apache 2.0

    TDQS

    A3.6/5.0

    Scored across 17 tools

    Disambiguation4/5

    The three network lookup tools (resolve_peppol_dns, peppol_lookup_participant, peppol_get_service_endpoint) layer on the same DNS/SMP pipeline and could be confused, though descriptions clearly delineate DNS-only vs registration vs endpoint retrieval. The codelist list_*/check_* families and the generate/parse/validate/send invoice tools are otherwise cleanly separated.

    Naming Consistency4/5

    All names use snake_case, but the convention varies: most tools follow verb_noun (list_document_type_ids, check_process_id_in_codelist), while several network tools use a peppol_ prefix (peppol_send, peppol_get_service_endpoint) or a noun_verb order (peppol_directory_search). Overall readable and mostly predictable with minor deviations.

    Tool Count3/5

    17 tools sits just above the ideal range and includes redundant families: three list_* and three check_* codelist tools that could be parameterized, plus three overlapping DNS/SMP lookup tools. Each tool is individually defensible, but the set feels heavier than necessary for this domain.

    Completeness3/5

    Core generate/parse/validate/send lifecycle is covered, but AE-specific validation is explicitly incomplete (no PINT-AE jurisdiction overlay rules, TDD validation always returns unavailable), and there is no inbound AS4 receipt or message handling. These are notable gaps for a full AE e-invoicing surface.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive