Skip to main content
Glama
theYahia

factura-uz-mcp

by theYahia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to factura-uz-mcp

No user-submitted related servers found.

    Related Servers

    • einvoice-mcp

      makririch
      A
      license
      A
      quality
      D
      maintenance
      MCP server for DACH e-invoicing. Create XRechnung (UBL) and ZUGFeRD 2.3 (Factur-X CII) invoices, validate against EN 16931 rules, extract data from XML, and convert between UBL, CII and JSON formats.
      6
      22 npm
      2
      MIT

    • mcp-facturacion-electronica-es

      cmendezs
      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
      321 PyPI
      2
      Apache 2.0

    • keycae-mcp

      AMKRS3
      A
      license
      A
      quality
      F
      maintenance
      Argentine electronic invoicing (facturación electrónica) MCP Server for ARCA/AFIP. Emit invoices, manage credentials, check delegations, and look up taxpayers. 10 tools.
      12
      378 npm
      MIT

    • @invapi/mcp-server

      invapi-org
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for the Invapi E-Invoicing API, enabling conversion, validation, and extraction of invoices in UBL, CII, ZUGFeRD, Excel, and more.
      19 npm
      MIT

    • facturx-mcp

      SamDreamsMaker
      A
      license
      A
      quality
      D
      maintenance
      An MCP server for electronic invoicing that enables generating, validating, and parsing Factur-X and ZUGFeRD compliant XML invoices. It supports the French 2026 B2B reform and provides integration with Chorus Pro for automated invoice submission and status tracking.
      9
      31 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool maps to a distinct action or resource: invoice lifecycle actions (create, sign, get, list, accept, reject) are mutually exclusive, and company/product lookups are clearly separate. No two tools overlap in purpose.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_invoice, list_products). The verbs are clear and uniform, with no mixed conventions or vague phrasing.

    Tool Count5/5

    Eight tools is well-scoped for an e-invoicing server, covering core operations without redundancy. The count feels neither sparse nor overwhelming for the domain.

    Completeness4/5

    The set covers the main invoice lifecycle (create, sign, retrieve, list, accept/reject) plus necessary lookups (company, products). A minor gap exists—no update or cancel/void operation for invoices—but core workflows can be completed without it.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing

    Resources