Stackin MCP server
io.github.stackin-io/stackinstackin-iostreamable-httpv1.3.0Scanned
Issue and manage Brazilian fiscal documents: NF-e for goods, NFS-e for services.
34 tools: 7 can delete or cancel things, 8 change things and 19 only read.
- Reads private data · 4
- Reads text others write · 8
- Can send data out · 2
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
7 tools here can delete or cancel things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Stackin MCP server can do
The Stackin MCP server is published by the GitHub account stackin-io. It has 34 tools. It can delete or cancel things (7 tools: issue_invoice, cancel_invoice, reissue_invoice, correct_invoice and 3 more) and create or change data (8 tools: consult_invoice, sync_received_invoices, lookup_fiscal_code, save_client and 4 more). 19 tools only read.
4 tools read private data (get_invoice_pdf, invoice_stats, list_received_invoices and 1 more); 8 tools bring in text other people can write (issue_invoice, cancel_invoice, reissue_invoice and 5 more); 2 tools can send data out of your system (save_client and create_webhook). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 3 times since Anlyon Radar first saw them.
Last scanned Nov 20, 2026, version 1.3.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
34 tools
Deletes or cancels 7Claude Code: deny
cancel_invoiceCancel an authorized invoice.Reads text others writeNo findings
Why it is in this group
- The name "cancel_invoice" says "cancel": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
correct_invoiceFile an electronic correction letter (CC-e) against an NF-e.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
delete_webhookStop delivering events to one endpoint.No findings
Why it is in this group
- The name "delete_webhook" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
invalidate_numberingDeclare an NF-e numbering range reserved but never used.Reads text others writeNo findings
Why it is in this group
- The description says "Irreversible".
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
issue_invoiceIssue a Brazilian fiscal document: NFS-e or NF-e.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
manifest_received_invoiceDeclare this company's position on a document issued against it.Reads text others writeNo findings
Why it is in this group
- The description says "irreversible".
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
reissue_invoiceRetry a rejected invoice after the data that caused the rejection was fixed.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
Changes things 8Claude Code: ask
classify_itemSuggest an NCM, CFOP, CST/CSOSN, CEST or service code for one item.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
consult_invoiceLook up an invoice's current status by its access key.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Look up an invoice's current status by its access key. Read-only: it never changes the document.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
create_webhookRegister a URL to receive this company's document events.Can send data outNo findings
Why it is in this group
- The name "create_webhook" says "create": a word for a change.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
deactivate_clientHide a saved client; reactivate_client brings it back.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Hide a saved client; reactivate_client brings it back.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
lookup_fiscal_codeResolve one code of one classification, when you know both.1 finding
Why it is in this group
- The name "lookup_fiscal_code" says "lookup": a word for reading.
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "lookup_fiscal_code" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "lookup_fiscal_code" says "lookup": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
reactivate_clientBring a deactivated client back to the registry.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Bring a deactivated client back to the registry.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
save_clientSave a client in the company's registry, or update a saved one.Can send data outNo findings
Why it is in this group
- The name "save_client" says "save": a word for a change.
What it can reach
- outboundThe input takes a destination (input.phone): what the tool writes goes there.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
sync_received_invoicesAsk the tax authority now for NF-e issued against this company.Reads text others writeNo findings
Why it is in this group
- The name "sync_received_invoices" says "sync": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 19Show 19 read-only tools
explain_rejectionExplain why a rejected document was refused and what to change.No findings
Why it is in this group
- The name "explain_rejection" says "explain": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_clientRead one saved client, with its full address.No findings
Why it is in this group
- The name "get_client" says "get": a word for reading.
Description, as the server wrote it Read one saved client, with its full address. Read-only.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_company_readinessWhether the company can issue right now, and if not, why.Reads text others writeNo findings
Why it is in this group
- The name "get_company_readiness" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "issue": it reads issues, which other people can write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_invoice_pdfReturn the printable rendering of a document, as a PDF.Reads private dataNo findings
Why it is in this group
- The name "get_invoice_pdf" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "return" and "document": it reads documents.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_invoice_submissionsShow every attempt made for one invoice and what came back.No findings
Why it is in this group
- The name "get_invoice_submissions" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_usageThe plan's allowances, what is used and the credit left.No findings
Why it is in this group
- The name "get_usage" says "get": a word for reading.
Description, as the server wrote it The plan's allowances, what is used and the credit left. Read it before saying an action is free. Read-only.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
invoice_statsCount this company's documents, and compare recent days.Reads private dataNo findings
Why it is in this group
- The description's first verb is "count": a word for reading.
What it can reach
- private-dataThe description's first sentence says "count" and "document": it reads documents.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_authorized_companiesList the companies this connection may act for, and what it may do on each.No findings
Why it is in this group
- The name "list_authorized_companies" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_clientsFind the company's saved clients.No findings
Why it is in this group
- The name "list_clients" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_fiscal_kindsWhich classifications this country has data for, right now.No findings
Why it is in this group
- The name "list_fiscal_kinds" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_invalidationsList the NF-e numbering ranges this company already declared unused, newest first.No findings
Why it is in this group
- The name "list_invalidations" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_invoicesList the invoices this company issued, newest first.No findings
Why it is in this group
- The name "list_invoices" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_received_invoicesList NF-e documents other companies issued against this one.Reads private dataNo findings
Why it is in this group
- The name "list_received_invoices" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "document": it reads documents.
Description, as the server wrote it 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).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_webhook_deliveriesShow every delivery attempt, newest first.No findings
Why it is in this group
- The name "list_webhook_deliveries" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_webhooksList where this company's events are delivered.No findings
Why it is in this group
- The name "list_webhooks" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
lookup_taxpayerLook up one taxpayer by exact tax id, to confirm who it is.No findings
Why it is in this group
- The name "lookup_taxpayer" says "lookup": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_citiesFind a municipality's IBGE code from its name.No findings
Why it is in this group
- The name "search_cities" says "search": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_fiscal_codesFind a code from a description, or page through a table.Reads private dataNo findings
Why it is in this group
- The name "search_fiscal_codes" says "search": a word for reading.
What it can reach
- private-dataThe description's first sentence says "find" and "table": it reads databases.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
validate_invoice_payloadCheck invoice data against the field rules without issuing anything.No findings
Why it is in this group
- The name "validate_invoice_payload" says "validate": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
64 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 2 outbound tools breaks every one.
- Reads private data4
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write8
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__stackin__create_webhook",
"mcp__stackin__save_client"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:11 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 15
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.stackin.io/.well-known/oauth-protected-resource
- Authorization servers
- https://api.stackin.io
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 15 tools that change things (7 destructive, 8 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.stackin.io/mcp: tools/list returned 34 tools to an anonymous client, including issue_invoice (destructive), cancel_invoice (destructive), reissue_invoice (destructive), correct_invoice (destructive), invalidate_numbering (destructive) and 10 more
Posture changes
- Nov 20, 2026
- Tools that change things, listed without credentials: 8 to 15
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to yes
Findings
Matches of fixed checks, with the text they matched.
The server marks "lookup_fiscal_code" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "lookup_fiscal_code" says "lookup": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 8 -> 15; Dynamic client registration: not observed -> yes; Client ID metadata documents: not observed -> yes.View diff
- Tools that change things, listed without credentials: 8 to 15
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to yes
Tools10 added, 8 changed.+10 added~8 changedView diff
- Added:classify_itemChanges things
- Added:create_webhookChanges things
- Added:delete_webhookDeletes or cancels
- Added:explain_rejectionOnly reads
- Added:get_company_readinessOnly reads
- Added:invoice_statsOnly reads
- Added:list_invalidationsOnly reads
- Added:list_webhook_deliveriesOnly reads
- Added:list_webhooksOnly reads
- Added:search_citiesOnly reads
- Changed:cancel_invoiceDeletes or cancelsinputSchema
- Changed:consult_invoiceChanges thingsinputSchema
- Changed:correct_invoiceDeletes or cancelsinputSchema
- Changed:get_invoice_pdfOnly readsinputSchema
- Changed:issue_invoiceDeletes or cancelsdescriptioninputSchema
- Changed:list_invoicesOnly readsinputSchema
- Changed:lookup_taxpayerOnly readsinputSchema
- Changed:manifest_received_invoiceDeletes or cancelsinputSchema
Tools4 added, 20 changed.+4 added~20 changedView diff
- Added:deactivate_clientChanges things
- Added:get_usageOnly reads
- Added:reactivate_clientChanges things
- Added:sync_received_invoicesChanges things
- Changed:cancel_invoiceDeletes or cancelsinputSchema
- Changed:consult_invoiceChanges thingsinputSchema
- Changed:correct_invoiceDeletes or cancelsinputSchema
- Changed:get_clientOnly readsinputSchema
- Changed:get_invoice_pdfOnly readsinputSchema
- Changed:get_invoice_submissionsOnly readsinputSchema
- Changed:invalidate_numberingDeletes or cancelsinputSchema
- Changed:issue_invoiceDeletes or cancelsdescriptioninputSchema
- Changed:list_authorized_companiesOnly readsinputSchema
- Changed:list_clientsOnly readsinputSchema
- Changed:list_fiscal_kindsOnly readsinputSchema
- Changed:list_invoicesOnly readsinputSchema
- Changed:list_received_invoicesOnly readsdescriptioninputSchema
- Changed:lookup_fiscal_codeChanges thingsinputSchema
- Changed:lookup_taxpayerOnly readsinputSchema
- Changed:manifest_received_invoiceDeletes or cancelsinputSchema
- Changed:reissue_invoiceDeletes or cancelsinputSchema
- Changed:save_clientChanges thingsinputSchema
- Changed:search_fiscal_codesOnly readsinputSchema
- Changed:validate_invoice_payloadOnly readsinputSchema
Tools4 added, 11 changed.+4 added~11 changedView diff
- Added:get_clientOnly reads
- Added:list_authorized_companiesOnly reads
- Added:list_clientsOnly reads
- Added:save_clientChanges things
- Changed:cancel_invoiceDeletes or cancelsinputSchema
- Changed:consult_invoiceChanges thingsinputSchema
- Changed:correct_invoiceDeletes or cancelsinputSchema
- Changed:get_invoice_pdfOnly readsdescriptioninputSchema
- Changed:get_invoice_submissionsOnly readsinputSchema
- Changed:invalidate_numberingDeletes or cancelsinputSchema
- Changed:issue_invoiceDeletes or cancelsdescriptioninputSchema
- Changed:list_invoicesOnly readsinputSchema
- Changed:list_received_invoicesOnly readsinputSchema
- Changed:manifest_received_invoiceDeletes or cancelsinputSchema
- Changed:reissue_invoiceDeletes or cancelsinputSchema
Install
Pinned to version 1.3.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http stackin https://mcp.stackin.io/mcpclaude mcp add --transport http stackin https://mcp.stackin.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__stackin__get_invoice_pdf",
"mcp__stackin__list_invoices",
"mcp__stackin__get_invoice_submissions",
"mcp__stackin__invoice_stats",
"mcp__stackin__list_invalidations",
"mcp__stackin__validate_invoice_payload",
"mcp__stackin__list_received_invoices",
"mcp__stackin__search_fiscal_codes",
"mcp__stackin__list_fiscal_kinds",
"mcp__stackin__lookup_taxpayer",
"mcp__stackin__search_cities",
"mcp__stackin__list_authorized_companies",
"mcp__stackin__get_usage",
"mcp__stackin__get_company_readiness",
"mcp__stackin__list_clients",
"mcp__stackin__get_client",
"mcp__stackin__explain_rejection",
"mcp__stackin__list_webhooks",
"mcp__stackin__list_webhook_deliveries"
],
"ask": [
"mcp__stackin__consult_invoice",
"mcp__stackin__sync_received_invoices",
"mcp__stackin__lookup_fiscal_code",
"mcp__stackin__save_client",
"mcp__stackin__deactivate_client",
"mcp__stackin__reactivate_client",
"mcp__stackin__classify_item",
"mcp__stackin__create_webhook"
],
"deny": [
"mcp__stackin__issue_invoice",
"mcp__stackin__cancel_invoice",
"mcp__stackin__reissue_invoice",
"mcp__stackin__correct_invoice",
"mcp__stackin__invalidate_numbering",
"mcp__stackin__manifest_received_invoice",
"mcp__stackin__delete_webhook"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as stackin. Review it before you use it.
Capability tags behind 14 rules
- mcp__stackin__issue_invoice untrusted-input
- mcp__stackin__cancel_invoice untrusted-input
- mcp__stackin__get_invoice_pdf private-data
- mcp__stackin__reissue_invoice untrusted-input
- mcp__stackin__correct_invoice untrusted-input
- mcp__stackin__invalidate_numbering untrusted-input
- mcp__stackin__invoice_stats private-data
- mcp__stackin__list_received_invoices private-data
- mcp__stackin__sync_received_invoices untrusted-input
- mcp__stackin__manifest_received_invoice untrusted-input
- mcp__stackin__search_fiscal_codes private-data
- mcp__stackin__get_company_readiness untrusted-input
- mcp__stackin__save_client outbound
- mcp__stackin__create_webhook outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.stackin-io/stackin/verify?hash=ef4955ede2fb750ccbed0d149f5cf702755a9fc95cd74753793d4d103a5d51cd" | jq -e '.changed == false'Pinned hash ef4955ede2fb, from Nov 20, 2026, 18:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.stackin-io/stackin/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.stackin-io/stackin)Source: MCP Registry · repository. Synced Nov 20, 2026, 18:18 UTC.
Stackin MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Stackin MCP server safe?
- No scan can promise that. What its definitions show: 34 tools, 15 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Stackin MCP server delete data?
- Yes. 7 tools can delete, cancel or revoke something: issue_invoice, cancel_invoice, reissue_invoice, correct_invoice, invalidate_numbering, manifest_received_invoice and 1 more.
Can the Stackin MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Stackin MCP server have?
- 34 tools: 7 destructive, 8 write, 19 read. issue_invoice, cancel_invoice, reissue_invoice, correct_invoice, invalidate_numbering, manifest_received_invoice, delete_webhook, consult_invoice and 26 more.
Does the Stackin MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Stackin MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): save_client and create_webhook.
Has the Stackin MCP server changed its tools?
- Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.