MCP Universal EC E-Invoice Server
Related Servers
Alternatives to MCP Universal EC E-Invoice Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that exposes tools for Taiwan's ezPay e-invoice lifecycle, enabling AI assistants to issue, void, and query invoices and allowances through the standard MCP protocol.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to accept payments and issue Taiwanese government e-invoices via ECPay. Supports payment link creation, status query, invoice issue and void.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI clients to interact with a point-of-sale public API through 32 MCP tools for managing bills, customers, items, orders, receipts, stock, suppliers, taxes, and webhooks over stdio and HTTP transports.-
- AlicenseAqualityCmaintenanceEnables AI agents to stamp, cancel, and query Mexican CFDI 4.0 invoices through MCP tools, with support for local stdio and hosted HTTP transport.4220 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to create CVS store pickup and home delivery shipments in Taiwan, including label printing and tracking via the ECPay Logistics API.MIT
- AlicenseBqualityBmaintenanceMCP server wrapping ECOUNT ERP OpenAPI, enabling Claude to call inventory, sales, purchase, and accounting data as tools. Supports automating tax invoice journal entries and customer registration.4MIT
TDQS
Scored across 27 tools
Most tools have distinct purposes, but pairs like create_b2c_allowance and create_b2c_allowance_named differ only in field format, and get_invoice_numbers vs expanded versions may confuse agents. Overall, the set is well-disambiguated.
All tools follow a consistent verb_noun pattern with clear prefixes (create, void, cancel, get) and type qualifiers (b2b, b2c, allowance, invoice). Suffixes like '_named' and '_expanded' are used systematically.
27 tools is on the higher side, but the domain of e-invoice management requires many distinct operations for different transaction types, formats, and lifecycle stages. The count is justified given the comprehensive coverage.
The set covers creation, void, cancel, and number management well, but lacks a general tool to retrieve invoice details (e.g., get_invoice). Missing update operations are handled via exchange tools, but the absence of a retrieval tool is a notable gap.