Connect Stackin and your agent gets 16 tools, among them cancel_invoice, consult_invoice, correct_invoice. It answers at https://mcp.stackin.io/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 24 October 2026, succeeded.
Issue and manage Brazilian fiscal documents: NF-e for goods, NFS-e for services.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
cancel_invoice | Cancel an authorized invoice. Legal cancellation, with fiscal and accounting effect, inside a window the NFS-e authorizer enforces for the municipality. Ask the human to confirm before calling; never call it speculatively. The reason reache Inputs: access_key, document_type, reason, idempotency_key |
consult_invoice | Look up an invoice's current status by its access key. Read-only: it never changes the document. Inputs: access_key, document_type |
correct_invoice | File an electronic correction letter (CC-e) against an NF-e. NF-e only: there is no correction letter for an NFS-e, where a wrong document is cancelled and issued again. It corrects wording and non-fiscal fields only. It cannot change value Inputs: access_key, correction |
get_invoice_pdf | Return the printable rendering of a document, as a PDF. Works for both types — a DANFE for nfe, a DANFSe for nfse. The PDF comes back base64-encoded in content_base64; the XML, not this, is the legally valid document. A 502 from here means Inputs: access_key, document_type |
get_invoice_submissions | Show every attempt made for one invoice and what came back. This is the tool that answers "why was it rejected". consult_invoice gives the status; this gives the tax authority's own code, its message, and the request and response exactly as Inputs: invoice_id |
invalidate_numbering | Declare an NF-e numbering range reserved but never used. NF-e numbering has to be continuous, so a gap left by a failed issuance is explained to the SEFAZ with this — not with a new document. Irreversible: a number declared unused can never Inputs: series, number_start, number_end, reason |
issue_invoice | Issue a Brazilian fiscal document: NFS-e or NF-e. This produces a legal fiscal document. Confirm the data with the user before calling when you inferred any field. Every item needs a price: unit_price is what one unit costs and amount is th |
list_fiscal_kinds | Which classifications this country has data for, right now. Ask this before assuming a classification exists. The answer grows as the source data does, so a name absent here is absent today rather than absent forever. Inputs: country |
list_invoices | List the invoices this company issued, newest first. One document type at a time: pass nfse for services or nfe for goods. A company that issues both has to be asked twice. Use it for "my last invoices", "what was rejected today", and to fi Inputs: document_type, status, limit, offset |
list_received_invoices | List NF-e documents other companies issued against this one. The mirror of list_invoices: that one shows what this company issued, this one what it received. Read-only. It reads what the API already collected and never calls the tax authori Inputs: limit, offset |
lookup_fiscal_code | Resolve one code of one classification, when you know both. Use this to confirm a code before putting it on a document — an NCM that does not exist is rejected by the tax authority after issuing, which costs a cancellation. A code that is n Inputs: kind, code, country |
lookup_taxpayer | Look up one taxpayer by exact tax id, to confirm who it is. Use it to check a recipient's name before issuing against them. It takes the id exactly — punctuation is fine, but there is no search by name, by prefix or by state, and there will Inputs: tax_id, country |
manifest_received_invoice | Declare this company's position on a document issued against it. Legally binding and irreversible once the tax authority accepts it — ask the human to confirm before calling, and read back which document and which of the four positions is b Inputs: access_key, manifestation, reason |
reissue_invoice | Retry a rejected invoice after the data that caused the rejection was fixed. Takes the local invoice_id, not the access key: a rejected document never got one. Consumes a credit like a new issuance, so it takes an idempotency_key for the sa Inputs: invoice_id, idempotency_key |
search_fiscal_codes | Find a code from a description, or page through a table. This is the tool for "what NCM is a keyboard" — the one the user actually asks. Prefer it over guessing a code from memory: the tables change, and a plausible wrong code is worse than Inputs: kind, term, limit, offset, country |
validate_invoice_payload | Check invoice data against the field rules without issuing anything. Nothing is sent to the tax authority and no document is created. The SDK models check field formats, and for nfe the rules the SEFAZ refuses a document over: ncm and cfop Inputs: document_type, items, recipient_address |
Every block below points at https://mcp.stackin.io/mcp. Pick your client and copy.
claude mcp add --transport http stackin https://mcp.stackin.io/mcp
{
"mcpServers": {
"stackin": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.stackin.io/mcp"]
}
}
}{
"mcpServers": {
"stackin": {
"url": "https://mcp.stackin.io/mcp"
}
}
}{
"servers": {
"stackin": {
"type": "http",
"url": "https://mcp.stackin.io/mcp"
}
}
}{
"context_servers": {
"stackin": {
"url": "https://mcp.stackin.io/mcp"
}
}
}{
"mcpServers": {
"stackin": {
"serverUrl": "https://mcp.stackin.io/mcp"
}
}
}{
"mcpServers": {
"stackin": {
"url": "https://mcp.stackin.io/mcp"
}
}
}name: Stackin
version: 0.0.1
schema: v1
mcpServers:
- name: Stackin
type: streamable-http
url: https://mcp.stackin.io/mcp{
"mcpServers": {
"stackin": {
"httpUrl": "https://mcp.stackin.io/mcp"
}
}
}{
"mcpServers": {
"stackin": {
"type": "http",
"url": "https://mcp.stackin.io/mcp"
}
}
}{
"mcpServers": {
"stackin": {
"url": "https://mcp.stackin.io/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.stackin.io%2Fmcp&type=streamable_http&id=stackin&name=Stackin
It answered our last check on 24 October 2026 in 937 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
16, as returned by the server's own tools/list on 21 September 2026: cancel_invoice, consult_invoice, correct_invoice, get_invoice_pdf, get_invoice_submissions, invalidate_numbering, issue_invoice, list_fiscal_kinds, and 8 more.
It answered our last check on 24 October 2026 in 937 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.stackin.io/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.stackin-io. Endpoint host: mcp.stackin.io. ARD identifier: urn:air:io.github.stackin-io:mcp:stackin.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.