Tiendanube MCP
NPM · @COMMENTEME/TIENDANUBE-MCP
Live Tiendanube / Nuvemshop docs, Admin API endpoints, OAuth scopes, webhook events and scaffolds
Available components
Last scanned (21 hours ago)
Scores higher than 56% of npm servers
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 15 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1004 tokens (~143/item across 7 items; 7 tools + 0 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 Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 (29% 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
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 13 Nov 26 +1
- Security disclosure: fail → unverified ▼ functional
- 11 Nov 26 +1
- Security disclosure: unverified → fail ▼ functional
- 10 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
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 · Analysed npm/@commenteme/tiendanube-mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
lookup-endpoint Look up an Admin API endpoint ~142
Look up Tiendanube / Nuvemshop Admin API endpoints by path, resource or keywords: method, path, full URL with version and store_id, the OAuth scope it needs and the reference page. Works offline from an index of the 2025-03 reference. Use it when writing or reviewing API calls.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results for keyword search (default 15) |
| method | string | – | HTTP method |
| query | string | yes | A path ("/orders/{id}/fulfill", "/products/123/variants"), a resource name ("Fulfillment Order") or keywords ("tracking event", "custom fields product") |
No output schema declared.
No examples provided.
lookup-scope Look up OAuth scopes ~101
List the OAuth scopes of Tiendanube / Nuvemshop apps and the resources each one opens, or find the scope for a resource, endpoint path or scope name. Use it when choosing the scopes of an app in the Partners Portal or debugging a 401/403.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | A scope ("write_fulfillment_orders"), a resource ("Draft Order") or a path ("/orders/{id}"). Empty lists every scope. |
No output schema declared.
No examples provided.
lookup-webhook-event Look up webhook events ~96
List the webhook events of Tiendanube / Nuvemshop (orders, products, customers, fulfillment orders, locations, billing, app lifecycle and the required privacy webhooks), or find one, with how to register and verify them. Use it before registering webhooks or writing a receiver.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | An event ("order/paid"), a group ("fulfillment_order") or empty for the full list |
No output schema declared.
No examples provided.
read-doc Read a Tiendanube / Nuvemshop doc page ~188
Read a page of the official docs, or one section of it, by URL or site path. Fetched live as Markdown from nuvemshop.dev or tiendanube.dev; other hosts are refused. Use it after search-docs, lookup-endpoint or when the user pastes a docs link.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Docs language: en-US (default), pt-BR (Nuvemshop) or es (Tiendanube) |
| maxChars | integer | – | Truncate the answer to this many characters (default 20000) |
| section | string | – | Heading or anchor of one section to return instead of the whole page |
| url | string | yes | Page URL on nuvemshop.dev or tiendanube.dev (with or without .md, an #anchor selects a section), or a site path such as "api/resources/2025-03/order" |
No output schema declared.
No examples provided.
scaffold-oauth-callback Scaffold the OAuth install flow ~144
Generate the Express (TypeScript) OAuth 2 authorization code flow of a Tiendanube / Nuvemshop app: install redirect with state, callback that exchanges the code with a JSON body and stores the token per app and store. Returns the files for the caller to write. For a full app, it points to the official templates.
| Name | Type | Req | Description |
|---|---|---|---|
| appId | string | yes | App ID (client_id) from the Partners Portal |
| brand | string | – | Which domain the merchant sees (default tiendanube); the two token URLs are equivalent |
| dir | string | – | Folder for the generated files, relative to the project root (default "src") |
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | Files to write. The server never writes to disk. |
| notes | array | yes | Next steps and caveats |
No examples provided.
scaffold-webhook-handler Scaffold a webhook receiver ~127
Generate an Express (TypeScript) webhook receiver for Tiendanube / Nuvemshop: x-linkedstore-hmac-sha256 verification over the raw body, immediate 200, one case per event and a node:test for the signature. Returns the files for the caller to write; the server never writes to disk.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | Folder for the generated files, relative to the project root (default "src") |
| events | array | yes | Events to handle, as in lookup-webhook-event (e.g. ["order/paid", "app/uninstalled"]) |
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | Files to write. The server never writes to disk. |
| notes | array | yes | Next steps and caveats |
No examples provided.
search-docs Search Tiendanube / Nuvemshop docs ~206
Search the official Tiendanube / Nuvemshop developer docs (Admin API, apps, NubeSDK, themes, Storefront API, AI and agents), fetched live from nuvemshop.dev. Returns matching pages with URL and, for the top three, the best matching section. Use it first for any "how do I" question; follow up with read-doc.
| Name | Type | Req | Description |
|---|---|---|---|
| excerpts | boolean | – | Also fetch the top 3 pages and quote the best matching section (default true) |
| limit | integer | – | Max results (default 5, max 15) |
| locale | string | – | Docs language: en-US (default), pt-BR (Nuvemshop) or es (Tiendanube) |
| query | string | yes | Keywords to look for in the official Tiendanube / Nuvemshop developer docs (e.g. "webhook signature", "fulfillment order tracking", "NubeSDK checkout slot", "sectionable theme schema") |
No output schema declared.
No examples provided.
How do I install the Tiendanube MCP server?
Tiendanube MCP runs locally as an npm package, launched with npx -y @commenteme/tiendanube-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @commenteme/tiendanube-mcp
claude mcp add commentemeapp-tiendanube-mcp -- npx -y @commenteme/tiendanube-mcp
What is the Tiendanube MCP server?
Tiendanube MCP is listed in the public MCP registry as io.github.commentemeapp/tiendanube-mcp. Live Tiendanube / Nuvemshop docs, Admin API endpoints, OAuth scopes, webhook events and scaffolds. This page covers its npm package (@commenteme/tiendanube-mcp).
Is the Tiendanube MCP server safe to use?
Tiendanube MCP scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 Tiendanube MCP server expose?
Tiendanube MCP exposes 7 tools: search-docs, read-doc, lookup-endpoint, lookup-scope, lookup-webhook-event, and 2 more. Their descriptions and schemas cost roughly 1,004 tokens of context every time the server is loaded.
Is the Tiendanube MCP server still maintained?
Tiendanube MCP 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 licence is the Tiendanube MCP server under?
Tiendanube MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Tiendanube MCP server?
VerifyMCP ran 16 checks on Tiendanube MCP, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.