F
licenseA
qualityD
maintenanceEnables AI assistants to interact with Brazilian electronic invoices (NF-e, NFC-e, NFS-e) via Nuvem Fiscal API, including CNPJ lookup, invoice issuance, cancellation, and PDF generation.
16
1
-
Brazil Invoices (NFS-e nota fiscal de serviço)
by app.wishpool
Server Details
Brazil NFS-e service invoices for AI agents via Focus NFe and NFe.io. Stateless, never stores data.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Server Listing
- brazil-invoice-mcp
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
3 tool updates
- Changed
cancel_invoice3 fields changed- changed
Input schema / properties / justificativa / descriptionPrevious value: -"Reason for cancellation (justificativa), 15-255 characters — required by the prefeitura."New value: +"Reason for cancellation (justificativa), 15-255 characters — required by the prefeitura (Focus NFe). NFe.io cancels without a mandatory reason but this is still collected for parity." - added
Input schema / properties / providerAdded value: +{ + "description": "Optional explicit provider. Omit to auto-route by credential headers. Overrides header x-invoice-provider.", + "enum": [ + "focusnfe", + "nfeio" + ], + "type": "string" +} - changed
Input schema / properties / ref / descriptionPrevious value: -"The ref returned by create_invoice."New value: +"The ref returned by create_invoice (your ref for Focus NFe; NFe.io's invoice id for NFe.io)."
- Changed
create_invoice2 fields changed- added
Input schema / properties / providerAdded value: +{ + "description": "Optional explicit provider. Omit to auto-route by which credential headers you sent (x-focusnfe-token -> focusnfe, x-nfeio-key -> nfeio). Overrides header x-invoice-provider.", + "enum": [ + "focusnfe", + "nfeio" + ], + "type": "string" +} - changed
Input schema / properties / ref / descriptionPrevious value: -"Optional caller-chosen unique reference for this NFS-e (used to poll/cancel). Auto-generated if omitted and returned to you."New value: +"Optional caller-chosen unique reference for this NFS-e (used to poll/cancel). Applies to Focus NFe only (auto-generated if omitted); NFe.io ignores it and returns its own invoice id as the ref."
- Changed
query_invoice2 fields changed- added
Input schema / properties / providerAdded value: +{ + "description": "Optional explicit provider. Omit to auto-route by credential headers. Overrides header x-invoice-provider.", + "enum": [ + "focusnfe", + "nfeio" + ], + "type": "string" +} - changed
Input schema / properties / ref / descriptionPrevious value: -"The ref returned by create_invoice."New value: +"The ref returned by create_invoice (your ref for Focus NFe; NFe.io's invoice id for NFe.io)."
3 tool updates
- First observed
cancel_invoice - First observed
create_invoice - First observed
query_invoice
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Issue and manage Brazilian service invoices (NFS-e) by chatting with your agent, platform-hosted, no
Brazilian AI-powered accounting & tax automation: NFS-e invoicing, CBS/IBS tax reform, compliance.
Brazilian SEFAZ e-invoices (NF-e, CT-e) issued against your company. A1 cert, DANFE PDF.
Chile DTE for AI agents - boleta/factura electronica via OpenFactura or LibreDTE. Stateless BYO.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceProvides read-only consultation of Rio de Janeiro's electronic service invoices (NFS-e) from official sources, with pay-per-use credits.MIT
- AlicenseNot gradedqualityCmaintenanceEmita e gerencie notas fiscais de serviço (NFS-e) conversando com o agente, hospedado pela plataforma, sem precisar de conta na nfe.io.8MIT
- AlicenseNot gradedqualityCmaintenanceEnables querying issued electronic service invoices (NFS-e) from the Brazilian Federal Revenue via natural language, providing read-only access to official invoice data.MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.5/5.0
Disambiguation5/5
Each tool has a clearly distinct purpose: create, query, cancel. No overlap in functionality.
Naming Consistency5/5
All tools follow a consistent verb_noun snake_case pattern (cancel_invoice, create_invoice, query_invoice).
Tool Count4/5
Three tools is a minimal but reasonable set for the core lifecycle of an invoice (create, query, cancel). Could benefit from a list tool, but still scoped appropriately.
Completeness3/5
The set covers create, query, and cancel, but lacks a list/search tool, which would be helpful for managing multiple invoices. No update or other operations, but those are often not needed for invoices.