Skip to main content
Glama
cmendezs

mcp-fattura-elettronica-it

Related Servers

Alternatives to mcp-fattura-elettronica-it

No user-submitted related servers found.

    Related Servers

    • 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
      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
      Apache 2.0
    • 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
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      Model Context Protocol (MCP) server for United Arab Emirates Electronic Invoicing (PINT AE / Peppol 5-Corner Model). Provides tools to validate, generate, and explore API specifications for FTA / Peppol interoperability.
      4
      17
      1
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      Model Context Protocol (MCP) server for Spanish Electronic Invoicing. Provides tools to generate, validate, and submit invoices across VERI\*FACTU, Facturae/FACe, SII, TicketBAI, and Crea y Crece B2B.
      20
      2
      Apache 2.0

    TDQS

    A4/5.0

    Scored across 43 tools

    Disambiguation4/5

    Tools are mostly distinct, each targeting a specific invoice-building step or format. The only clear duplication is validate_partita_iva and validate_partita_iva_format, which are explicitly equivalent and could cause misselection. Other overlaps (e.g., generate_fattura_xml vs generate_fattura_semplificata) are well-differentiated by output format.

    Naming Consistency4/5

    Names follow a consistent verb_noun pattern (build_, generate_, validate_, parse_, get_, etc.) with snake_case throughout. Minor deviations: the it__ prefix for SDI/archiving operations and slight verb variation (lookup vs get, compute vs build) but no mixing of conventions or camelCase.

    Tool Count2/5

    At 43 tools, this is far beyond the typical 3-15 range. While the FatturaPA domain is complex and covers generation, validation, conversion, signing, submission, and archiving, the sheer number feels excessive and may overwhelm agents. It is not an extreme mismatch (50+), but it is still too many for most practical uses.

    Completeness5/5

    The tool surface is remarkably complete: it covers the full invoice lifecycle—building blocks (seller, buyer, transmission, line items, totals), multiple output formats (FatturaPA, simplified, UBL, CII), validation (XSD, structural), parsing, signing, SDI submission/status/notification handling, and archiving with retrieval and integrity checks. No obvious gaps exist for the domain.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week