Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Stackin

REMOTE · MCP.STACKIN.IO

Issue and manage Brazilian fiscal documents: NF-e for goods, NFS-e for services.

Available components

+1 this week 92 Trust /100

Last scanned (18 hours ago)

Scores higher than 98% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security91
Transport & Reachability100
Schema Quality & AI Usability76
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 9866 tokens (~281/item across 35 items; 34 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 36 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “delete_webhook”, which the server declares destructive security
    • Tool “issue_invoice” rewrote its description, which is the text the model reads security
    • Schema quality: 7039 → 9866 ▼ functional
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • Destructive annotations: pass → 100 functional
    • MCP protocol version: 2025-11-25 → 2026-07-28 functional
    • Server version: 0.8.1 → 0.9.0 functional
    • Server version: 0.8.0 → 0.8.1 functional
    • New tool “classify_item” functional
    • New tool “create_webhook” functional
    • New tool “explain_rejection” functional
    • New tool “get_company_readiness” functional
    • New tool “invoice_stats” functional
    • New tool “list_invalidations” functional
    • New tool “list_webhook_deliveries” functional
    • New tool “list_webhooks” functional
    • New tool “search_cities” functional
    • “issue_invoice” added an optional parameter “contingency” cosmetic
    • “issue_invoice” added an optional parameter “discount” cosmetic
    • “issue_invoice” added an optional parameter “issued_at” cosmetic
    • “cancel_invoice” reworded the description of “access_key” cosmetic
    • “consult_invoice” reworded the description of “access_key” cosmetic
    • “correct_invoice” reworded the description of “access_key” cosmetic
    • “get_invoice_pdf” reworded the description of “access_key” cosmetic
    • “lookup_taxpayer” reworded the description of “tax_id” cosmetic
    • “manifest_received_invoice” reworded the description of “access_key” cosmetic
  • 19 Nov 26 0
    • Tool “list_received_invoices” rewrote its description, which is the text the model reads security
    • Schema quality: 6381 → 7039 ▼ functional
    • Server version: 0.7.1 → 0.8.0 functional
    • New tool “deactivate_client” functional
    • New tool “get_usage” functional
    • New tool “reactivate_client” functional
    • New tool “sync_received_invoices” functional
    • “list_clients” added an optional parameter “inactive” cosmetic
    • “list_invoices” added an optional parameter “external_reference” cosmetic
    • “list_clients” dropped the optional parameter “include_inactive” cosmetic
  • 18 Nov 26 +1
    • Tool “issue_invoice” rewrote its description, which is the text the model reads security
    • Tool coverage: 56% → 100% ▲ functional
    • Schema quality: good → excellent functional
    • New resource “invoice-item-schema” functional
    • Server version: 0.6.0 → 0.7.1 functional
    • “cancel_invoice” reworded the description of “access_key” cosmetic
    • “cancel_invoice” reworded the description of “company_id” cosmetic
    • “cancel_invoice” reworded the description of “company_tax_id” cosmetic
    • “cancel_invoice” reworded the description of “document_type” cosmetic
    • “cancel_invoice” reworded the description of “idempotency_key” cosmetic
    • “cancel_invoice” reworded the description of “reason” cosmetic
    • “consult_invoice” reworded the description of “access_key” cosmetic
    • “consult_invoice” reworded the description of “company_id” cosmetic
    • “consult_invoice” reworded the description of “company_tax_id” cosmetic
    • “consult_invoice” reworded the description of “document_type” cosmetic
    • “correct_invoice” reworded the description of “access_key” cosmetic
    • “correct_invoice” reworded the description of “company_id” cosmetic
    • “correct_invoice” reworded the description of “company_tax_id” cosmetic
    • “correct_invoice” reworded the description of “correction” cosmetic
    • “get_client” reworded the description of “client_id” cosmetic
    • “get_client” reworded the description of “company_id” cosmetic
    • “get_client” reworded the description of “company_tax_id” cosmetic
    • “get_invoice_pdf” reworded the description of “access_key” cosmetic
    • “get_invoice_pdf” reworded the description of “company_id” cosmetic
    • “get_invoice_pdf” reworded the description of “company_tax_id” cosmetic
    • “get_invoice_pdf” reworded the description of “document_type” cosmetic
    • “get_invoice_submissions” reworded the description of “company_id” cosmetic
    • “get_invoice_submissions” reworded the description of “company_tax_id” cosmetic
    • “get_invoice_submissions” reworded the description of “invoice_id” cosmetic
    • “invalidate_numbering” reworded the description of “company_id” cosmetic
    • “invalidate_numbering” reworded the description of “company_tax_id” cosmetic
    • “invalidate_numbering” reworded the description of “number_end” cosmetic
    • “invalidate_numbering” reworded the description of “number_start” cosmetic
    • “invalidate_numbering” reworded the description of “reason” cosmetic
    • “invalidate_numbering” reworded the description of “series” cosmetic
    • “issue_invoice” reworded the description of “company_id” cosmetic
    • “issue_invoice” reworded the description of “company_tax_id” cosmetic
    • “issue_invoice” reworded the description of “document_type” cosmetic
    • “issue_invoice” reworded the description of “export” cosmetic
    • “issue_invoice” reworded the description of “idempotency_key” cosmetic
    • “issue_invoice” reworded the description of “items” cosmetic
    • “issue_invoice” reworded the description of “number” cosmetic
    • “issue_invoice” reworded the description of “recipient_address” cosmetic
    • “issue_invoice” reworded the description of “series” cosmetic
    • “list_clients” reworded the description of “company_id” cosmetic
    • “list_clients” reworded the description of “company_tax_id” cosmetic
    • “list_clients” reworded the description of “include_inactive” cosmetic
    • “list_clients” reworded the description of “limit” cosmetic
    • “list_clients” reworded the description of “offset” cosmetic
    • “list_invoices” reworded the description of “company_id” cosmetic
    • “list_invoices” reworded the description of “company_tax_id” cosmetic
    • “list_invoices” reworded the description of “document_type” cosmetic
    • “list_invoices” reworded the description of “limit” cosmetic
    • “list_invoices” reworded the description of “offset” cosmetic
    • “list_invoices” reworded the description of “status” cosmetic
    • “list_received_invoices” reworded the description of “company_id” cosmetic
    • “list_received_invoices” reworded the description of “company_tax_id” cosmetic
    • “list_received_invoices” reworded the description of “limit” cosmetic
    • “list_received_invoices” reworded the description of “offset” cosmetic
    • “manifest_received_invoice” reworded the description of “access_key” cosmetic
    • “manifest_received_invoice” reworded the description of “company_id” cosmetic
    • “manifest_received_invoice” reworded the description of “company_tax_id” cosmetic
    • “manifest_received_invoice” reworded the description of “manifestation” cosmetic
    • “manifest_received_invoice” reworded the description of “reason” cosmetic
    • “reissue_invoice” reworded the description of “company_id” cosmetic
    • “reissue_invoice” reworded the description of “company_tax_id” cosmetic
    • “reissue_invoice” reworded the description of “idempotency_key” cosmetic
    • “reissue_invoice” reworded the description of “invoice_id” cosmetic
    • “save_client” reworded the description of “address” cosmetic
    • “save_client” reworded the description of “company_id” cosmetic
    • “save_client” reworded the description of “company_tax_id” cosmetic
    • “save_client” reworded the description of “email” cosmetic
    • “save_client” reworded the description of “foreign_id” cosmetic
    • “save_client” reworded the description of “name” cosmetic
    • “save_client” reworded the description of “notes” cosmetic
    • “save_client” reworded the description of “phone” cosmetic
    • “save_client” reworded the description of “state_registration” cosmetic
    • “validate_invoice_payload” reworded the description of “document_type” cosmetic
    • “validate_invoice_payload” reworded the description of “items” cosmetic
    • “validate_invoice_payload” reworded the description of “recipient_address” cosmetic
  • 17 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “issue_invoice” rewrote its description, which is the text the model reads security
    • Schema quality: 176 → 308 ▼ functional
    • Schema quality: 176 → 307 ▼ functional
    • Tool coverage: 23% → 56% ▲ functional
    • Tool coverage: 23% → 55% ▲ functional
    • Server version: 0.3.2 → 0.6.0 functional
    • Server version: 0.2.5 → 0.3.2 functional
    • New tool “get_client” functional
    • New tool “list_clients” functional
    • New tool “save_client” functional
    • New tool “list_authorized_companies” functional
    • “issue_invoice” added an optional parameter “client_id” cosmetic
    • “issue_invoice” added an optional parameter “update_client” cosmetic
    • “cancel_invoice” added an optional parameter “company_id” cosmetic
    • “cancel_invoice” added an optional parameter “company_tax_id” cosmetic
    • “consult_invoice” added an optional parameter “company_id” cosmetic
    • “consult_invoice” added an optional parameter “company_tax_id” cosmetic
    • “correct_invoice” added an optional parameter “company_id” cosmetic
    • “correct_invoice” added an optional parameter “company_tax_id” cosmetic
    • “get_invoice_pdf” added an optional parameter “company_id” cosmetic
    • “get_invoice_pdf” added an optional parameter “company_tax_id” cosmetic
    • “get_invoice_submissions” added an optional parameter “company_id” cosmetic
    • “get_invoice_submissions” added an optional parameter “company_tax_id” cosmetic
    • “invalidate_numbering” added an optional parameter “company_id” cosmetic
    • “invalidate_numbering” added an optional parameter “company_tax_id” cosmetic
    • “issue_invoice” added an optional parameter “company_id” cosmetic
    • “issue_invoice” added an optional parameter “company_tax_id” cosmetic
    • “issue_invoice” added an optional parameter “direction” cosmetic
    • “issue_invoice” added an optional parameter “export” cosmetic
    • “issue_invoice” added an optional parameter “external_reference” cosmetic
    • “issue_invoice” added an optional parameter “foreign_id” cosmetic
    • “issue_invoice” added an optional parameter “purpose” cosmetic
    • “issue_invoice” added an optional parameter “referenced_keys” cosmetic
    • “list_invoices” added an optional parameter “company_id” cosmetic
    • “list_invoices” added an optional parameter “company_tax_id” cosmetic
    • “list_invoices” added an optional parameter “include_items” cosmetic
    • “list_received_invoices” added an optional parameter “company_id” cosmetic
    • “list_received_invoices” added an optional parameter “company_tax_id” cosmetic
    • “manifest_received_invoice” added an optional parameter “company_id” cosmetic
    • “manifest_received_invoice” added an optional parameter “company_tax_id” cosmetic
    • “reissue_invoice” added an optional parameter “company_id” cosmetic
    • “reissue_invoice” added an optional parameter “company_tax_id” cosmetic
    • “issue_invoice” reworded the description of “client_name” cosmetic
    • “issue_invoice” reworded the description of “tax_id” cosmetic
    • “cancel_invoice” reworded the description of “idempotency_key” cosmetic
    • “issue_invoice” reworded the description of “idempotency_key” cosmetic
    • “reissue_invoice” reworded the description of “idempotency_key” cosmetic
    • “issue_invoice” made “client_name” optional cosmetic
    • “issue_invoice” made “tax_id” optional cosmetic
  • 16 Nov 26 0
    • Tool “get_invoice_pdf” rewrote its description, which is the text the model reads security
    • Server version: 0.2.1 → 0.2.5 functional
  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.stackin.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.stackin.io CN=Amazon RSA 2048 M04,O=Amazon,C=US 6 Sept 2026 22 Mar 2027 RSA 2048 SHA256-RSA 694ef604c679a3522b84112981821dd
SANs: mcp.stackin.io, www.mcp.stackin.io
CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 773124f2a952e3ed18a58bdb85d1bc0ce5f27
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.stackin.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
stackin.io. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://mcp.stackin.io/.well-known/oauth-protected-resource"

Bearer resource_metadata="https://mcp.stackin.io/.well-known/oauth-protected-resource"

Protected resource metadata

Document https://mcp.stackin.io/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://mcp.stackin.io
Authorisation server https://api.stackin.io

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.stackin.io/mcp Verified 200
http (plaintext) http://mcp.stackin.io/mcp HTTPS enforced
MCP tools · 34 exposed · ~9,575 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
cancel_invoice ~423

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 reaches the tax authority verbatim and must be at least 15 characters. Pass idempotency_key to make a retry safe: repeating the same key with the same access key and reason replays the first answer instead of cancelling a second time. Reuse the key only when retrying that exact call; a genuinely new cancellation needs a new key, or none. Nothing generates one for you — two calls without a key are two cancellations.

NameTypeReqDescription
access_keystringyesThe access key (chave de acesso) the authorizer assigned, as issue_invoice and list_invoices return it. An NF-e key has 44 characters; the issuer's CNPJ inside it may carry letters since July 2026, s…
company_id––UUID of the company this call acts for. Omit it when the connection covers a single company; with several it is required (see list_authorized_companies). Send company_id or company_tax_id, never both.
company_tax_id––CNPJ or CPF of the company this call acts for, never the recipient or a taxpayer being looked up. Omit it when the connection covers a single company; with several it is required (see list_authorized…
document_typestringyesnfse for a service invoice, nfe for goods.
idempotency_key––One per business event, e.g. order-1042. Sent as an HTTP header: printable ASCII up to 255, no leading or trailing space.
reasonstringyesWhy the document is cancelled, 15 to 256 characters. It reaches the tax authority verbatim, e.g. Erro no valor do servico prestado.
NameTypeReqDescription
access_key––The authorizer's key. Absent while the document is not authorized.
id––Local id. Use it for reissue and for submissions, and when a document was rejected and has no key.
protocol––The authorization protocol, when granted.
status––issued, rejected or cancelled.

No examples provided.

classify_item ~466

Suggest an NCM, CFOP, CST/CSOSN, CEST or service code for one item. A suggestion to confirm with the user — never issue on it blindly. Every code in a candidate was read from the published tables, but the NCM and the CFOP decide the tax owed, and a plausible wrong one is authorized by the SEFAZ and only caught at an audit. Show the primary candidate, its confidence and the alternatives, say it is a suggestion, and put a code on an item only after the user confirms it — whatever the confidence. lookup_fiscal_code can confirm one code against the table. When missing_information is not empty, ask the user those questions and call again with the answers in the matching arguments. Changes nothing.

NameTypeReqDescription
company_id––UUID of the company this call acts for. Omit it when the connection covers a single company; with several it is required (see list_authorized_companies). Send company_id or company_tax_id, never both.
company_tax_id––CNPJ or CPF of the company this call acts for, never the recipient or a taxpayer being looked up. Omit it when the connection covers a single company; with several it is required (see list_authorized…
contains_alcohol––Only when missing_information asked for it.
descriptionstringyesWhat the item is, as the user describes it, e.g. Cerveja artesanal IPA garrafa 500ml.
document_typestringyesnfe for goods, nfse for a service.
operation_scope––Only when missing_information asked for it.
purpose––Whether the buyer resells it or consumes it. Only when missing_information asked for it.
recipient_state––The buyer's UF, e.g. SP. It decides intrastate (5xxx) or interstate (6xxx) CFOP.
service_city_code––IBGE code of the city where the service is provided. Only when missing_information asked for it.
tax_retained––Whether the ISS is retained by the buyer. Only when missing_information asked for it.
NameTypeReqDescription
alternative_candidatesarray––
classification_type––product or service.
confidence––0 to 1. Not a guarantee at any value.
confirmation_requiredboolean–Always true: a suggestion goes on an item only after the user confirms it.
id–––
justification–––
missing_informationarray–Ask the user these and call again with the answers.
primary_candidate–––
warningsarray––

No examples provided.

consult_invoice ~221

Look up an invoice's current status by its access key. Read-only: it never changes the document.

NameTypeReqDescription
access_keystringyesThe access key (chave de acesso) the authorizer assigned, as issue_invoice and list_invoices return it. An NF-e key has 44 characters; the issuer's CNPJ inside it may carry letters since July 2026, s…
company_id––UUID of the company this call acts for. Omit it when the connection covers a single company; with several it is required (see list_authorized_companies). Send company_id or company_tax_id, never both.
company_tax_id––CNPJ or CPF of the company this call acts for, never the recipient or a taxpayer being looked up. Omit it when the connection covers a single company; with several it is required (see list_authorized…
document_typestringyesnfse for a service invoice, nfe for goods.
NameTypeReqDescription
access_key––The authorizer's key. Absent while the document is not authorized.
id––Local id. Use it for reissue and for submissions, and when a document was rejected and has no key.
protocol––The authorization protocol, when granted.
status––issued, rejected or cancelled.

No examples provided.

correct_invoice ~358

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 values, taxes, the recipient or the products — those still require cancelling and issuing again, and telling the user a CC-e will fix an amount is wrong in a way they only discover at an audit. Each letter supersedes the previous one and the SEFAZ keeps at most 20 per document. The text reaches the tax authority verbatim.

NameTypeReqDescription
access_keystringyesThe access key (chave de acesso) the authorizer assigned, as issue_invoice and list_invoices return it. An NF-e key has 44 characters; the issuer's CNPJ inside it may carry letters since July 2026, s…
company_id––UUID of the company this call acts for. Omit it when the connection covers a single company; with several it is required (see list_authorized_companies). Send company_id or company_tax_id, never both.
company_tax_id––CNPJ or CPF of the company this call acts for, never the recipient or a taxpayer being looked up. Omit it when the connection covers a single company; with several it is required (see list_authorized…
correctionstringyesThe corrected wording, 15 to 1000 characters, sent verbatim, e.g. Onde se le Rua A, leia-se Rua B. Replaces any earlier letter, so repeat what still applies.
NameTypeReqDescription
access_key––The authorizer's key. Absent while the document is not authorized.
id––Local id. Use it for reissue and for submissions, and when a document was rejected and has no key.
protocol––The authorization protocol, when granted.
status––issued, rejected or cancelled.

No examples provided.

create_webhook ~289

Register a URL to receive this company's document events. Every document authorized, rejected, cancelled or corrected is then sent there, with its data, signed with the secret. Confirm the URL with the user before calling: it is where their fiscal data goes. The API refuses a URL that is not HTTPS or points at a private network. Needs webhook:manage. Calling it twice registers two endpoints, and each receives every event: list_webhooks first.

NameTypeReqDescription
company_id––UUID of the company this call acts for. Omit it when the connection covers a single company; with several it is required (see list_authorized_companies). Send company_id or company_tax_id, never both.
company_tax_id––CNPJ or CPF of the company this call acts for, never the recipient or a taxpayer being looked up. Omit it when the connection covers a single company; with several it is required (see list_authorized…
events––Which events to send. Every one if omitted.
secretstringyes16 to 255 characters the user chose; every delivery is signed with it. It is never shown again, so do not repeat it back.
urlstringyesWhere to deliver, an https:// URL the user gave. Never one you made up.
NameTypeReqDescription
created_at–––
environment–––
eventsarray–The events sent there. Empty means every event.
id––Pass it to delete_webhook.
is_active–––
url–––

No examples provided.

deactivate_client ~147

Hide a saved client; reactivate_client brings it back.

NameTypeReqDescription
client_idstringyesThe client's id, from list_clients.
company_id––UUID of the company this call acts for. Omit it when the connection covers a single company; with several it is required (see list_authorized_companies). Send company_id or company_tax_id, never both.
company_tax_id––CNPJ or CPF of the company this call acts for, never the recipient or a taxpayer being looked up. Omit it when the connection covers a single company; with several it is required (see list_authorized…
NameTypeReqDescription
address–––
foreign_id––Document of a buyer abroad.
id––Pass it as client_id to issue_invoice or save_client.
is_active–––
last_used_at–––
name–––
source––manual, issued (imported from issued invoices) or issuance (saved by an issuance).
tax_id––CPF (11 digits) or CNPJ (14 characters, unpunctuated). A CNPJ may carry letters in its first 12 positions since July 2026, so never treat it as a number.
uses_count–––

No examples provided.

delete_webhook ~198

Stop delivering events to one endpoint. The user's integration stops hearing about new documents from that moment, so confirm which endpoint with them first. What was already delivered stays in list_webhook_deliveries. An id this company does not have is refused (404). Needs webhook:manage.

NameTypeReqDescription
company_id––UUID of the company this call acts for. Omit it when the connection covers a single company; with several it is required (see list_authorized_companies). Send company_id or company_tax_id, never both.
company_tax_id––CNPJ or CPF of the company this call acts for, never the recipient or a taxpayer being looked up. Omit it when the connection covers a single company; with several it is required (see list_authorized…
webhook_idstringyesThe endpoint's id, from list_webhooks.
NameTypeReqDescription
deletedboolean––
idstringyes–

No examples provided.

explain_rejection ~292

Explain why a rejected document was refused and what to change. get_invoice_submissions has the authority's reply as sent; this reads it for someone who does not speak SEFAZ: the code, the message verbatim, what it means, the steps to fix it, the field at fault and, when there is one, a suggested value. Quote the code and the message to the user; they are what they will search for. A suggested value is confirmed with the user before reissue_invoice, never applied on its own. transient means the authority was unavailable, not the data wrong. A document that is not rejected is refused (409). Read-only.

NameTypeReqDescription
company_id––UUID of the company this call acts for. Omit it when the connection covers a single company; with several it is required (see list_authorized_companies). Send company_id or company_tax_id, never both.
company_tax_id––CNPJ or CPF of the company this call acts for, never the recipient or a taxpayer being looked up. Omit it when the connection covers a single company; with several it is required (see list_authorized…
invoice_idstringyesThe local id of the rejected invoice, as list_invoices returns it. A rejected document has no access key.
NameTypeReqDescription
authority–––
code––The authority's own rejection code.
explanation––What it means, in plain words.
field––The field to fix, when there is one.
invoice_id–––
message––The authority's message, verbatim.
status––known (from the catalogue of rejection codes), generated (written for this case) or unknown.
stepsarray–What to change, in order.
suggested––A value for that field, when one can be suggested. Confirm it with the user before reissuing.
transient––True when the authority was unavailable rather than the data wrong: reissuing unchanged may work.

No examples provided.

get_client ~148

Read one saved client, with its full address. Read-only.

NameTypeReqDescription
client_idstringyesThe client's id, from list_clients.
company_id––UUID of the company this call acts for. Omit it when the connection covers a single company; with several it is required (see list_authorized_companies). Send company_id or company_tax_id, never both.
company_tax_id––CNPJ or CPF of the company this call acts for, never the recipient or a taxpayer being looked up. Omit it when the connection covers a single company; with several it is required (see list_authorized…
NameTypeReqDescription
address–––
foreign_id––Document of a buyer abroad.
id––Pass it as client_id to issue_invoice or save_client.
is_active–––
last_used_at–––
name–––
source––manual, issued (imported from issued invoices) or issuance (saved by an issuance).
tax_id––CPF (11 digits) or CNPJ (14 characters, unpunctuated). A CNPJ may carry letters in its first 12 positions since July 2026, so never treat it as a number.
uses_count–––

No examples provided.

get_company_readiness ~221

Whether the company can issue right now, and if not, why. Call it before a company's first document, and when issuing fails for a reason that is not the document's: ready is false with missing naming the cause (certificate, certificate_expired, certificate_unreadable, address), each fixed in the Stackin dashboard, not here. Also the certificate's expiry, the tax regime (CRT), the state and the default série per document type. Read-only.

NameTypeReqDescription
company_id––UUID of the company this call acts for. Omit it when the connection covers a single company; with several it is required (see list_authorized_companies). Send company_id or company_tax_id, never both.
company_tax_id––CNPJ or CPF of the company this call acts for, never the recipient or a taxpayer being looked up. Omit it when the connection covers a single company; with several it is required (see list_authorized…
NameTypeReqDescription
certificate_expires_at–––
company_id–––
default_series––The série used per document type when none is sent.
environment––homologation or production.
has_certificate–––
missingarray–Why not: certificate, certificate_expired, certificate_unreadable, address. Empty when ready.
name–––
ready–––
state–––
tax_id–––
tax_regime––CRT: 1 Simples, 2 Simples excesso, 3 normal, 4 MEI.

No examples provided.

get_invoice_pdf ~312

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, with its size in size_bytes; the XML, not this, is the legally valid document. A PDF above 2 MB is not inlined: the answer says to download it from the API instead. A 502 from here means the authorizer is unavailable, not that the invoice is wrong.

NameTypeReqDescription
access_keystringyesThe access key (chave de acesso) the authorizer assigned, as issue_invoice and list_invoices return it. An NF-e key has 44 characters; the issuer's CNPJ inside it may carry letters since July 2026, s…
company_id––UUID of the company this call acts for. Omit it when the connection covers a single company; with several it is required (see list_authorized_companies). Send company_id or company_tax_id, never both.
company_tax_id––CNPJ or CPF of the company this call acts for, never the recipient or a taxpayer being looked up. Omit it when the connection covers a single company; with several it is required (see list_authorized…
document_typestringyesnfse for a service invoice, nfe for goods.
NameTypeReqDescription
access_keystringyes–
content_base64stringyesThe PDF bytes, base64-encoded. Decode before saving.
content_typestring––
size_bytes––Size of the decoded PDF, in bytes.

No examples provided.

get_invoice_submissions ~300

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 they went over the wire. Read-only. It takes the invoice_id, like reissue_invoice — a rejected document has no access key to look it up by. Get the id from list_invoices. The rows are attempts, not documents: a reissued invoice has more than one, oldest first, and only the last describes the current state. Quote the authority's message rather than paraphrasing it; the code is what the user will search for.

NameTypeReqDescription
company_id––UUID of the company this call acts for. Omit it when the connection covers a single company; with several it is required (see list_authorized_companies). Send company_id or company_tax_id, never both.
company_tax_id––CNPJ or CPF of the company this call acts for, never the recipient or a taxpayer being looked up. Omit it when the connection covers a single company; with several it is required (see list_authorized…
invoice_idstringyesThe local invoice id (a UUID), as list_invoices and issue_invoice return it. Not the access key.
NameTypeReqDescription
attemptsarray––
invoice_id–––

No examples provided.

get_usage ~145

The plan's allowances, what is used and the credit left. Read it before saying an action is free. Read-only.

NameTypeReqDescription
company_id––UUID of the company this call acts for. Omit it when the connection covers a single company; with several it is required (see list_authorized_companies). Send company_id or company_tax_id, never both.
company_tax_id––CNPJ or CPF of the company this call acts for, never the recipient or a taxpayer being looked up. Omit it when the connection covers a single company; with several it is required (see list_authorized…
NameTypeReqDescription
companies_on_account–––
credit_balance–––
included_invoices–––
included_received–––
overage_price_cents–––
plan_name–––
plan_slug–––
received_free–––
received_price_cents–––
used_invoices–––
used_received–––

No examples provided.

invalidate_numbering ~341

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 be used. Only for numbers that were never authorized. An authorized document is cancelled, never invalidated. Confirm the range with the user and read it back before calling: the range is inclusive, and one digit wrong burns numbers the company still needs. The SDK refuses a backwards range and a reason outside 15-255 characters before anything is transmitted.

NameTypeReqDescription
company_id––UUID of the company this call acts for. Omit it when the connection covers a single company; with several it is required (see list_authorized_companies). Send company_id or company_tax_id, never both.
company_tax_id––CNPJ or CPF of the company this call acts for, never the recipient or a taxpayer being looked up. Omit it when the connection covers a single company; with several it is required (see list_authorized…
number_endintegeryesLast unused number, inclusive; equal to number_start for a single number.
number_startintegeryesFirst unused number, inclusive.
reasonstringyesWhy the numbers went unused, 15 to 255 characters, sent verbatim, e.g. Falha no sistema durante a emissao.
seriesstringyesThe NF-e series of the range, e.g. 1.
NameTypeReqDescription
access_key––The authorizer's key. Absent while the document is not authorized.
id––Local id. Use it for reissue and for submissions, and when a document was rejected and has no key.
protocol––The authorization protocol, when granted.
status––issued, rejected or cancelled.

No examples provided.

invoice_stats ~228

Count this company's documents, and compare recent days. The answer to "how many invoices this month", "how much did I bill" and "is rejection going up": totals by document type and by status over everything, then issued and rejected counts and the amount for the last `days` beside the `days` before them, and one row per day. In the connection's environment only. Read-only.

NameTypeReqDescription
company_id––UUID of the company this call acts for. Omit it when the connection covers a single company; with several it is required (see list_authorized_companies). Send company_id or company_tax_id, never both.
company_tax_id––CNPJ or CPF of the company this call acts for, never the recipient or a taxpayer being looked up. Omit it when the connection covers a single company; with several it is required (see list_authorized…
daysinteger–The window compared with the one before it, in days. 30 by default.
NameTypeReqDescription
by_document_type–––
by_status–––
current_period–––
daily_seriesarray–One row per day: date, count, amount.
period_days–––
previous_period–––
total–––

No examples provided.

issue_invoice ~1,333

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. Send unit_price with quantity when the user quotes a price per unit, amount when they quote the line. Sending both asserts they agree and is refused if they do not. nfse is a service invoice: the address is optional and service_code (LC 116/2003 item.subitem) falls back to the company's fiscal profile. nfe is for goods, and the SEFAZ rejects a partial one: ncm and cfop on every item and the full recipient_address. Call validate_invoice_payload first when any of that was inferred rather than given. A complementary, adjustment or return NF-e sets purpose and names the original in referenced_keys; a return the company receives back sets direction in. An export has recipient_address state EX with country_code, the export group, and foreign_id when the buyer has a passport. Look the recipient up with list_clients first and pass its id as client_id. A new recipient is saved as a client after a successful issuance. Pass idempotency_key when a retry is possible: the same key with the same payload replays the first answer instead of issuing a second document. Without one, a retry after a lost response issues again, burning another credit and number that only a cancellation within its deadline undoes. One key per business event, not per call; nothing generates it for you. Before a company's first document, get_company_readiness says whether it can issue at all.

NameTypeReqDescription
client_id––A saved client's id, from list_clients: its name, document and address fill whatever this call leaves out. Without it, client_name and tax_id are required.
client_namestring–Recipient's name. Required unless client_id is sent.
company_id––UUID of the company this call acts for. Omit it when the connection covers a single company; with several it is required (see list_authorized_companies). Send company_id or company_tax_id, never both.
company_tax_id––CNPJ or CPF of the company this call acts for, never the recipient or a taxpayer being looked up. Omit it when the connection covers a single company; with several it is required (see list_authorized…
contingencyboolean–nfe only: send through the state's contingency authorizer (SVC-AN or SVC-RS) because its own is down. Use it only when the user says the SEFAZ is unavailable, never as a retry for a rejection.
direction––out for an outgoing NF-e (CFOP 5/6/7); in for one the company issues for goods coming in, such as a sale the buyer returned (CFOP 1/2/3). nfe only; omitted means out.
discount––A discount on the whole document, in BRL, e.g. 15.50. The API spreads it over the lines in proportion to each line's amount. Omitted means none; a per-line discount goes on the item.
document_typestringyesnfse for a service invoice, nfe for goods.
exportobject|null–Where the goods leave Brazil (exporta): exit_state (UF) and place, e.g. Porto de Santos. Required for an nfe to a buyer abroad (recipient_address.state EX), refused otherwise.
external_reference––The caller's own id for this document, such as an order number. Stored as sent and returned on every read.
foreign_id––Passport or other document of a buyer abroad, used when recipient_address.state is EX. nfe only; may be omitted.
idempotency_key––One per business event, e.g. order-1042. Sent as an HTTP header: printable ASCII up to 255, no leading or trailing space.
issued_at––Emission date-time (dhEmi), ISO 8601 with a timezone offset, e.g. 2026-11-15T09:30:00-03:00; a value without an offset is refused. Omitted means now. nfe: at most 30 days back and 5 minutes ahead; nf…
itemsarrayyesOne entry per line. Each needs a description and a price: unit_price with quantity, or amount for the whole line. nfe also needs ncm (8 digits) and cfop (4 digits) on every item; nfse may carry servi…
number––Document number (número), e.g. 1532. Omitted means the next one from the company's counter; set it only to fill a known gap.
purpose––Why the NF-e is issued (finNFe): normal, complementary, adjustment or return of goods. nfe only; omitted means normal.
recipient_addressobject|null–The recipient's address. Required for nfe with street, number, neighborhood, city, state (UF, e.g. SP), zip_code (8 digits) and city_code (7-digit IBGE code, e.g. 3550308); optional for nfse. A buyer…
referenced_keys––Access keys of the NF-e this one refers to: the note being returned, complemented or adjusted. Required for complementary (exactly one) and for most returns. nfe only.
series––Document series (série), e.g. 1. Omitted means the company's default series.
tax_idstring–Recipient's CPF or CNPJ. Required unless client_id is sent.
update_clientboolean–Save the recipient data sent in this call back onto the client named by client_id.
NameTypeReqDescription
access_key––The authorizer's key. Absent while the document is not authorized.
id––Local id. Use it for reissue and for submissions, and when a document was rejected and has no key.
protocol––The authorization protocol, when granted.
status––issued, rejected or cancelled.

No examples provided.

list_authorized_companies ~118

List the companies this connection may act for, and what it may do on each. Call it before acting when the user has more than one company, or when a tool answered that it needs a company. Each row carries the company_id (UUID) and tax_id (CNPJ or CPF) the other tools accept as company_id or company_tax_id, and the permissions granted there. One connection may cover several companies; when it covers only one, the other tools need no company at all. Read-only.

Input schema present but exposes no named parameters.

NameTypeReqDescription
companiesarray––
environment––homologation or production, for every company here.

No examples provided.

list_clients ~242

Find the company's saved clients. Look a recipient up here before typing one into issue_invoice: when it is already saved, pass its id as client_id and the name, document and address come from the registry. Most recently used first. Read-only.

NameTypeReqDescription
company_id––UUID of the company this call acts for. Omit it when the connection covers a single company; with several it is required (see list_authorized_companies). Send company_id or company_tax_id, never both.
company_tax_id––CNPJ or CPF of the company this call acts for, never the recipient or a taxpayer being looked up. Omit it when the connection covers a single company; with several it is required (see list_authorized…
inactiveboolean–List the deactivated clients instead of the active ones.
limitinteger–Rows per page, 1 to 100.
offsetinteger–Rows to skip, for the next page: offset + limit.
search––Part of the name, or the CPF/CNPJ with or without punctuation.
NameTypeReqDescription
dataarray––
total––How many match, not how many are here.

No examples provided.

list_fiscal_kinds ~89

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.

NameTypeReqDescription
countrystring–ISO 3166-1 alpha-2 code. A code means nothing without it, and Brazil is the default rather than a guess.
NameTypeReqDescription
kindsarray––

No examples provided.

list_invalidations ~228

List the NF-e numbering ranges this company already declared unused, newest first. Read it before invalidate_numbering: a range reported twice is refused, and one that overlaps a past report means the gap was already explained. Each row has the series, the inclusive range, the reason, the SEFAZ status and its protocol. Read-only.

NameTypeReqDescription
company_id––UUID of the company this call acts for. Omit it when the connection covers a single company; with several it is required (see list_authorized_companies). Send company_id or company_tax_id, never both.
company_tax_id––CNPJ or CPF of the company this call acts for, never the recipient or a taxpayer being looked up. Omit it when the connection covers a single company; with several it is required (see list_authorized…
limitinteger–Rows per page, 1 to 100.
offsetinteger–Rows to skip, for the next page: offset + limit.
NameTypeReqDescription
dataarray––
next_page–––
page–––
per_page–––
prev_page–––
total–––

No examples provided.

list_invoices ~421

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 find a document whose access key the user does not have at hand. Read-only. An authorized document is stored as issued, which is the value the rows carry; authorized is accepted as a synonym and asks for the same thing. Every row carries both identifiers the other tools need: id, which reissue_invoice takes, and access_key, which consult_invoice, cancel_invoice and get_invoice_pdf take. A rejected row has an id and no access key — the authorizer never assigned one.

NameTypeReqDescription
company_id––UUID of the company this call acts for. Omit it when the connection covers a single company; with several it is required (see list_authorized_companies). Send company_id or company_tax_id, never both.
company_tax_id––CNPJ or CPF of the company this call acts for, never the recipient or a taxpayer being looked up. Omit it when the connection covers a single company; with several it is required (see list_authorized…
document_typestring–nfse for a service invoice, nfe for goods.
external_reference––Only documents with this external_reference.
include_itemsboolean–Keep each row's item lines and fiscal_operation. Off by default: they are most of the size, and a page of 100 NF-e with them is about 130 KB. consult_invoice brings one document's lines back.
limitinteger–Rows per page, 1 to 100.
offsetinteger–Rows to skip, for the next page: offset + limit.
status––Only rows in this state. authorized is a synonym for issued. All states when omitted.
NameTypeReqDescription
dataarray–The rows on this page.
next_page–––
page–––
per_page–––
prev_page–––
total––How many exist, not how many are here.
total_pages–––

No examples provided.

list_received_invoices ~289

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 authority; collection runs every six hours and sync_received_invoices asks now. Each row carries the issuer, the amount, has_full_document and, once one was filed, the manifestation; final_answer_due means only an awareness was filed. Before a manifestation the authority sends a summary only; the full document arrives after one. Past the plan's monthly allowance each new one costs credit (get_usage).

NameTypeReqDescription
company_id––UUID of the company this call acts for. Omit it when the connection covers a single company; with several it is required (see list_authorized_companies). Send company_id or company_tax_id, never both.
company_tax_id––CNPJ or CPF of the company this call acts for, never the recipient or a taxpayer being looked up. Omit it when the connection covers a single company; with several it is required (see list_authorized…
limitinteger–Rows per page, 1 to 100.
offsetinteger–Rows to skip, for the next page: offset + limit.
NameTypeReqDescription
dataarray––
next_page–––
page–––
per_page–––
prev_page–––
total–––

No examples provided.

list_webhook_deliveries ~220

Show every delivery attempt, newest first. The answer to "is my webhook receiving": each row has the event, its status, how many attempts, what the endpoint answered (response_status), the last error and when it was delivered or will be tried again. Needs webhook:manage. Read-only.

NameTypeReqDescription
company_id––UUID of the company this call acts for. Omit it when the connection covers a single company; with several it is required (see list_authorized_companies). Send company_id or company_tax_id, never both.
company_tax_id––CNPJ or CPF of the company this call acts for, never the recipient or a taxpayer being looked up. Omit it when the connection covers a single company; with several it is required (see list_authorized…
limitinteger–Rows per page, 1 to 100.
offsetinteger–Rows to skip, for the next page: offset + limit.
NameTypeReqDescription
dataarray––
next_page–––
page–––
per_page–––
prev_page–––
total–––

No examples provided.

list_webhooks ~165

List where this company's events are delivered. One row per endpoint: its id (what delete_webhook takes), URL, events and whether it is active. Secrets are never returned. Needs webhook:manage. Read-only.

NameTypeReqDescription
company_id––UUID of the company this call acts for. Omit it when the connection covers a single company; with several it is required (see list_authorized_companies). Send company_id or company_tax_id, never both.
company_tax_id––CNPJ or CPF of the company this call acts for, never the recipient or a taxpayer being looked up. Omit it when the connection covers a single company; with several it is required (see list_authorized…
NameTypeReqDescription
webhooksarray––

No examples provided.

lookup_fiscal_code ~223

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 not there answers 404. That means the code is wrong, not that the lookup failed; do not retry it. `metadata` differs per kind and is passed through as published: utrib on an NCM, ncm_code on a CEST, tax_type on a CST, and nothing at all on an ISS service.

NameTypeReqDescription
codestringyesThe code itself, as published: 84716052 for an NCM, 5102 for a CFOP. Digits only, no dots.
countrystring–ISO 3166-1 alpha-2 code. A code means nothing without it, and Brazil is the default rather than a guess.
kindstringyescfop, ncm, cest, cst, csosn, ...
NameTypeReqDescription
code–––
country–––
description–––
kind––cfop, ncm, cest, cst, csosn, ...
metadata––Whatever the classification carries beyond a code and a description, and it differs per kind: utrib on an NCM, ncm_code on a CEST, tax_type on a CST, null on an ISS service.

No examples provided.

lookup_taxpayer ~238

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 not be: the registry holds the names and addresses of real people. A 404 does not mean the company does not exist. The registry reloads monthly from the RFB's dump, so a recently registered CNPJ is simply not in it yet. Say that to the user rather than reporting the tax id as invalid, and never turn a 404 here into a validation rule.

NameTypeReqDescription
countrystring–ISO 3166-1 alpha-2 code. A code means nothing without it, and Brazil is the default rather than a guess.
tax_idstringyesThe exact tax id. A CNPJ is 14 characters and may carry letters in its first 12 since July 2026 (e.g. 12ABC34501DE35); a CPF is 11 digits. Punctuation is fine.
NameTypeReqDescription
activity_code–––
city_code–––
country–––
kind––Whether it is a company or a person.
metadata––Whatever the registry holds beyond these.
name–––
postal_code–––
started_at–––
state–––
status–––
tax_id–––
trade_name–––

No examples provided.

manifest_received_invoice ~360

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 being filed. Denying a document (210220) or declaring the operation did not happen (210240) is an accusation against whoever issued it. Never pick either because the user sounds unsure — ask. 210200 confirms the operation happened, 210210 acknowledges the document exists, 210220 denies knowing it, and 210240 states the operation was not carried out. Only 210240 takes a reason, and it requires one; the others are refused if a reason is sent.

NameTypeReqDescription
access_keystringyesThe 44-character access key of the received NF-e, as list_received_invoices returns it.
company_id––UUID of the company this call acts for. Omit it when the connection covers a single company; with several it is required (see list_authorized_companies). Send company_id or company_tax_id, never both.
company_tax_id––CNPJ or CPF of the company this call acts for, never the recipient or a taxpayer being looked up. Omit it when the connection covers a single company; with several it is required (see list_authorized…
manifestationstringyes210200 confirms the operation, 210210 acknowledges the document, 210220 denies knowing it, 210240 states the operation was not carried out.
reason––Required with 210240 and refused with any other code, e.g. Mercadoria nao foi entregue.
NameTypeReqDescription
access_key–––
manifestation––The code that was filed.
protocol––The receipt, when the authority gave one.
status–––

No examples provided.

reactivate_client ~145

Bring a deactivated client back to the registry.

NameTypeReqDescription
client_idstringyesFrom list_clients with inactive=true.
company_id––UUID of the company this call acts for. Omit it when the connection covers a single company; with several it is required (see list_authorized_companies). Send company_id or company_tax_id, never both.
company_tax_id––CNPJ or CPF of the company this call acts for, never the recipient or a taxpayer being looked up. Omit it when the connection covers a single company; with several it is required (see list_authorized…
NameTypeReqDescription
address–––
foreign_id––Document of a buyer abroad.
id––Pass it as client_id to issue_invoice or save_client.
is_active–––
last_used_at–––
name–––
source––manual, issued (imported from issued invoices) or issuance (saved by an issuance).
tax_id––CPF (11 digits) or CNPJ (14 characters, unpunctuated). A CNPJ may carry letters in its first 12 positions since July 2026, so never treat it as a number.
uses_count–––

No examples provided.

reissue_invoice ~264

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 same reason issue_invoice does. An authorized invoice is corrected or cancelled, never reissued.

NameTypeReqDescription
company_id––UUID of the company this call acts for. Omit it when the connection covers a single company; with several it is required (see list_authorized_companies). Send company_id or company_tax_id, never both.
company_tax_id––CNPJ or CPF of the company this call acts for, never the recipient or a taxpayer being looked up. Omit it when the connection covers a single company; with several it is required (see list_authorized…
idempotency_key––One per business event, e.g. order-1042. Sent as an HTTP header: printable ASCII up to 255, no leading or trailing space.
invoice_idstringyesThe local invoice id (a UUID), as list_invoices and issue_invoice return it. Not the access key.
NameTypeReqDescription
access_key––The authorizer's key. Absent while the document is not authorized.
id––Local id. Use it for reissue and for submissions, and when a document was rejected and has no key.
protocol––The authorization protocol, when granted.
status––issued, rejected or cancelled.

No examples provided.

save_client ~376

Save a client in the company's registry, or update a saved one. It records a recipient for later issuances; it issues nothing. A document already saved is refused with the existing client's id — call get_client or pass that id here to update it instead. Confirm the data with the user when any of it was inferred.

NameTypeReqDescription
addressobject|null–Postal address: street, number, neighborhood, city, state (UF), zip_code and city_code (IBGE). An NF-e to this client needs all of them.
client_id––Update this saved client instead of creating one. Only the fields sent change.
company_id––UUID of the company this call acts for. Omit it when the connection covers a single company; with several it is required (see list_authorized_companies). Send company_id or company_tax_id, never both.
company_tax_id––CNPJ or CPF of the company this call acts for, never the recipient or a taxpayer being looked up. Omit it when the connection covers a single company; with several it is required (see list_authorized…
email––Contact email, e.g. financeiro@empresa.com.
foreign_id––Passport or other document of a buyer abroad, used instead of tax_id.
namestringyesLegal name (razao social) or full name.
notes––Free text kept with the client.
phone––Contact phone with area code, e.g. 11987654321.
state_registration––State registration (IE), digits or ISENTO. Leave it out for a non-contributor.
tax_id––CPF or CNPJ. Required, except for a buyer abroad (address.state EX).
NameTypeReqDescription
address–––
foreign_id––Document of a buyer abroad.
id––Pass it as client_id to issue_invoice or save_client.
is_active–––
last_used_at–––
name–––
source––manual, issued (imported from issued invoices) or issuance (saved by an issuance).
tax_id––CPF (11 digits) or CNPJ (14 characters, unpunctuated). A CNPJ may carry letters in its first 12 positions since July 2026, so never treat it as a number.
uses_count–––

No examples provided.

search_cities ~161

Find a municipality's IBGE code from its name. Issuing resolves city_code from city and state by itself, so this is for the name that matches more than one city, or an address the API answered CITY_NOT_FOUND for. Returns at most 20, each with its code, name and state; ask the user which one when more than one fits. Read-only.

NameTypeReqDescription
countrystring–ISO 3166-1 alpha-2 code. A code means nothing without it, and Brazil is the default rather than a guess.
namestringyesThe start of the city's name, accents optional, e.g. santa rita.
state––Narrows to one UF, e.g. SP.
NameTypeReqDescription
citiesarray––

No examples provided.

search_fiscal_codes ~231

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 a lookup. Leaving `kind` unset searches every classification of that country at once, which is the most expensive call here. Set it whenever the question already names one. Rows come back ordered by kind then code; there is no sort argument, and asking for one changes nothing.

NameTypeReqDescription
countrystring–ISO 3166-1 alpha-2 code. A code means nothing without it, and Brazil is the default rather than a guess.
kind––Narrows to one classification. All if unset.
limitinteger–Rows per page. 20 by default.
offsetinteger–Rows to skip. Use it to page, not to narrow — a term is cheaper than paging to find one row.
term––Matches the code or the description.
NameTypeReqDescription
dataarray––
next_page–––
page–––
per_page–––
prev_page–––
total–––

No examples provided.

sync_received_invoices ~177

Ask the tax authority now for NF-e issued against this company. Collection already runs every six hours. After a read that finds nothing more the authority imposes a one-hour wait; inside it this is refused with the time to retry. Never retry in a loop.

NameTypeReqDescription
company_id––UUID of the company this call acts for. Omit it when the connection covers a single company; with several it is required (see list_authorized_companies). Send company_id or company_tax_id, never both.
company_tax_id––CNPJ or CPF of the company this call acts for, never the recipient or a taxpayer being looked up. Omit it when the connection covers a single company; with several it is required (see list_authorized…
NameTypeReqDescription
next_sync_at–––
pages–––
stored–––

No examples provided.

validate_invoice_payload ~206

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 on every item, and a complete recipient address. Worth calling before issue_invoice whenever a field was inferred rather than given. This does not replace issuing: the authorizer's cross-field and fiscal rules are only checked when the document is transmitted.

NameTypeReqDescription
document_typestringyesnfse for a service invoice, nfe for goods.
itemsarrayyesThe items exactly as they would go to issue_invoice, e.g. [{"description": "Cadeira", "amount": 450, "ncm": "94013000", "cfop": "5102"}].
recipient_address––The recipient_address exactly as it would go to issue_invoice. Required for nfe.
NameTypeReqDescription
checkedstringyesWhat was checked, so the answer is not read as more than it is.
document_typestringyes–
errorsarray––
validbooleanyesTrue when no field rule was broken. It does not promise the authorizer will accept the document.

No examples provided.

Install

How do I install the Stackin MCP server?

Stackin is a hosted endpoint at https://mcp.stackin.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.stackin.io

# add to Claude Code
claude mcp add --transport http stackin-io-stackin 'https://mcp.stackin.io/mcp'
Common questions

What is the Stackin MCP server?

Stackin is an MCP server listed in the public MCP registry as io.github.stackin-io/stackin. Issue and manage Brazilian fiscal documents: NF-e for goods, NFS-e for services. This page covers its hosted endpoint (https://mcp.stackin.io/mcp).

Is the Stackin MCP server safe to use?

Stackin scores 92 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Stackin MCP server expose?

Stackin exposes 34 tools: issue_invoice, consult_invoice, cancel_invoice, get_invoice_pdf, reissue_invoice, and 29 more. Their descriptions and schemas cost roughly 9,575 tokens of context every time the server is loaded.

Does the Stackin MCP server require authentication?

Yes. Stackin asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Stackin MCP server still maintained?

Stackin is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Stackin MCP server?

VerifyMCP ran 13 checks on Stackin, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.