mx-fiscal-mcp-server
Related Servers
Alternatives to mx-fiscal-mcp-server
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityCmaintenanceProvides AI assistants with live, authenticated access to official Mexican data sources including CURP, RFC, postal codes, phone numbers, SPEI payments, CFDI status, DOF semantic search, and geocoding via INEGI/INE.MIT- AlicenseNot gradedqualityBmaintenanceEnables AI agents to issue Mexico CFDI 4.0 electronic invoices (factura electrónica) via Facturapi, with tools for creating, querying, canceling, and sending invoices.MIT
- AlicenseNot gradedqualityCmaintenanceValidates LatAm banking and tax IDs (Mexican CLABE, Brazilian CNPJ/CPF checksums) and performs BrasilAPI company, CEP, and bank lookups, enabling AI agents to verify financial and tax information in Latin America.141 npmMIT
- 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.471 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to query Mexican postal codes, validate addresses, and search settlements using natural language from the official SEPOMEX catalog.1-
- AlicenseAqualityBmaintenanceEnables AI agents to audit Spanish VERI*FACTU invoice chains and exported XML by recomputing AEAT fingerprints and verifying record links, generate AEAT tax QR codes and images, and build or validate Facturae 3.2.2 invoices offline. It also exposes helpers for NIF checks, QR URL checks, compliance deadlines, and credit balances.11Business Source 1.1
TDQS
Scored across 9 tools
Each tool targets a distinct artifact: CFDI parsing (parse_cfdi), SAT status queries (cfdi_status / cfdi_batch_status), catalogue lookups (sat_catalog_lookup), identifier validators (validate_rfc/curp/clabe/nss) and fixture generation. The only near-pair, cfdi_status vs cfdi_batch_status, is explicitly delimited in the descriptions (single invoice vs up to 25, with caching/dedup semantics). An agent can pick correctly from names alone.
All names are snake_case and grouped by systematic prefixes: validate_* for the four validators, cfdi_* for the three document/status tools. The deviations are that the verb position varies (parse_cfdi, generate_test_data are verb-first while cfdi_status and sat_catalog_lookup put the resource first), but every name remains self-explanatory.
Nine tools is well inside the sweet spot and every one earns its place: parsing, single status, batch status, catalogue lookup, four validators and a fixture generator. No filler tools and no missing obvious utility within the same surface.
The read-only analysis/validation lifecycle is essentially covered: parse, verify against SAT, decode catalogues, validate every identifier the documents contain, and generate test data. Gaps are deliberate and documented (no signature verification, no cancellation submission, no Pagos/Nómina complement extraction, Retenciones refused), so agents hit dead ends only on out-of-scope operations.