servers / brazil-invoices-nfs-e-nota-fiscal-de-servico
Brazil Invoices (NFS-e nota fiscal de serviço) MCP server
communitystreamable_httpremotebrokenbroken
Brazil NFS-e service invoices for AI agents via Focus NFe. Stateless, never stores data.
01Tools · 3
How to read this: tool names here are observed from a live tools/list handshake. The Risk label is a heuristic inferred from the tool name (write/destructive verbs), not from executing the tool — a conservative guess, not a verified capability. We never escalate risk from a description. Found one that's wrong? Tell us — we fix on report.
| Tool | Risk | Side effects | Approval |
|---|---|---|---|
| cancel_invoice Cancel (void) an authorized Brazil NFS-e at the prefeitura, using its ref. Requires a justificativa (cancellation reason) of 15 to 255 characters. Only an AUTHORIZED NFS-e can be canceled; cancellation is permanent. | destructive | true | true |
| create_invoice Issue a Brazil NFS-e (nota fiscal de serviço eletrônica — the electronic service invoice municipalities/prefeituras require). Two interchangeable providers behind one tool (bring your own credentials as HTTP headers; this server stores nothing, and the merchant certificate + municipal registration stay in the merchant's own provider account): (A) FOCUS NFe — header x-focusnfe-token (free homologação/sandbox token issues test NFS-e with no fiscal effect; the produção token issues real ones; add x-focusnfe-mode: production to switch, default is the safer sandbox). (B) NFE.IO — headers x-nfeio-key (your NFe.io API key) + x-nfeio-company-id (the id of your issuing company/empresa in NFe.io, which holds the CNPJ, municipal registration and certificate; whether it is a Test or Production company — and thus fiscal effect — is set in your NFe.io account, not per request). Routing: whichever credential headers you send picks the provider; if both are present Focus NFe wins unless you set header x-invoice-provider: nfeio. ISSUANCE IS ASYNCHRONOUS: this returns status PROCESSING plus a ref — poll query_invoice with that ref until AUTHORIZED (nota autorizada) or ERROR. Ref semantics differ: with Focus NFe the ref is yours (auto-generated if omitted); with NFe.io the ref returned is NFe.io's own invoice id (a passed-in ref is ignored). For NFe.io the issuer comes from x-nfeio-company-id, so the prestador_* fields are validated but not forwarded. This is for service invoices (serviços); NF-e for physical goods is on the v2 roadmap. | write | true | unknown |
| query_invoice Check a Brazil NFS-e created by create_invoice, using its ref. Status values: PROCESSING (prefeitura is still authorizing — poll again shortly), AUTHORIZED (nota autorizada — numero and codigo_verificacao are populated, url links the official NFS-e), ERROR (authorization was rejected — see message for the reason), CANCELED (voided). Safe to call anytime. | read | false | unknown |
02Install & source
https://inv-br.wishpool.app/mcp
remote_url- repohttps://github.com/junter1989k-ai/brazil-invoice-mcp
- homepagehttps://inv-br.wishpool.app/mcp
- licenseMIT
- adoption0 stars · 0 forks
03Access granted
Process payments · destructive
The access this server can exercise, inferred from its verified tools — not a declared OAuth scope.
05Provenance & freshness
sourcesOfficial MCP Registry [p1]
last_checked2026-08-24 01:28Z
next_check2026-08-24 04:28Z
cadenceevery 3h
verifiedhandshake:failed metadata:failed handshake:failed metadata:failed handshake:failed metadata:failed handshake:failed metadata:failed handshake:failed metadata:failed
index_statusindex — 9 unique facts >= 5
06Badge
Add the “as seen on MCPExplorer” badge to your README.
[](https://mcpexplorer.com/servers/brazil-invoices-nfs-e-nota-fiscal-de-servico)
Next step
This is one server. A loadout combines the right servers, governance, and proven plays for a whole job — assembled deliberately, not tool-dumped.
Explore loadouts →