No user-submitted related servers found.
Scored across 6 tools
Each tool maps to a distinct pipeline stage: build (cfdi/pago), seal, validate, verify, and scope introspection. The only adjacent pair, build_cfdi and build_pago, is explicitly differentiated by document type (Ingreso/Egreso vs Complemento de Pagos). No overlapping purposes remain.
All tools use a consistent namespace prefix (mx__) plus a snake_case verb_noun pattern: build_cfdi, seal_cfdi, validate_cfdi, build_pago, verify_tfd, get_supported_scope. No mixing of conventions.
Six tools cleanly cover the described Phase-1 CFDI lifecycle without redundancy. Each tool earns its place and the count is well within the 3-15 ideal range.
The surface covers building (both document types), sealing, XSD validation, and TFD verification, which is a coherent end-to-end flow for the stated scope. PAC submission transport and later-phase complementos are deliberately absent, a minor gap agents must work around externally.