mcp-nfs-emissor
Related Servers
Alternatives to mcp-nfs-emissor
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAllows consultation of NFS-e (electronic service invoices) from the Brazilian Federal Revenue official source, with a single read-only tool.MIT
- AlicenseAqualityCmaintenanceEnables searching, downloading, and querying Brazilian electronic service invoices (NFS-e) through ISSWeb/Fiorilli municipal portals, including XML and PDF retrieval, access-key and CNPJ lookups, and multi-client configuration.10Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables retrieving inbound Brazilian electronic fiscal documents (supplier invoices, CT-e, events) directly from SEFAZ using your company's A1 digital certificate, with incremental NSU sync, query-budget protection, and DANFE PDF generation.MIT
- AlicenseNot gradedqualityCmaintenanceEnables consulting Brazilian electronic invoices (NFE) from official Receita Federal sources through a read-only MCP tool.MIT
- AlicenseAqualityAmaintenanceModel Context Protocol (MCP) server for Brazilian Electronic Invoicing (NF-e / NFC-e, modelo 55/65, schema 4.00). Provides CPF/CNPJ validation tools, with NF-e/NFC-e generation and SEFAZ integration planned.22Apache 2.0
- AlicenseAqualityDmaintenanceMCP server for querying Brazilian electronic service invoices (NFSe) from the national portal. Allows AI agents to authenticate with digital certificates and search, detail, and download PDFs of issued NFSe.342 npm16ISC
TDQS
Scored across 7 tools
Each tool addresses a distinct step in the NFS-e emission workflow: configuration, CSV loading, dry-run preview, actual emission, status checking, reprocessing failures, and listing historical outputs. There is no functional overlap.
All tool names follow a consistent verb_noun pattern in Portuguese (e.g., configurar_prestador, carregar_csv), using lowercase with underscores throughout. No naming style conflicts are present.
With 7 tools, the server covers all essential phases of batch NFS-e generation from setup to post-processing. The count is neither sparse nor excessive for the domain.
The tool set covers the core workflow (config, load, preview, emit, check status, reprocess failures, list history). A minor gap is the lack of a tool for individual note viewing or manual adjustment, but the overall lifecycle is well-supported.