No user-submitted related servers found.
Scored across 8 tools
Each tool targets a distinct resource and action: validators are split by identifier type (CLABE, CURP, NSS, RFC), and the CFDI tools cleanly separate parsing, SAT status lookup, and catalogue lookup. Even the two CFDI tools are unambiguous because one explicitly parses XML while the other explicitly queries the SAT.
The four validators follow a consistent validate_<identifier> pattern, and parse_cfdi and generate_test_data also use verb_noun naming. However, cfdi_status and sat_catalog_lookup deviate from the pattern with noun-based or suffix-based names, creating minor inconsistency across the set.
Eight tools is a well-scoped count for a Mexican fiscal and identifier validation server. Each tool covers a meaningful operation, and none feel redundant or extraneous.
The server covers the core lifecycle for Mexican fiscal identifiers and CFDI invoices: validation, decoding, parsing, SAT status lookup, catalogue reference, and test data generation. Minor gaps exist, such as no digital signature verification for CFDI XML, but the primary validation use cases are well covered.