VTEX IO MCP
NPM · @COMMENTEME/VTEX-IO-MCP
Scaffold VTEX IO apps, Node services and GraphQL, look up Store Framework block props, search docs
Available components
Last scanned (1 hour ago)
Scores higher than 34% of npm servers
Category Developer Tools
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 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 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability86
- 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
- Tool/resource definitions use about 9915 tokens (~24/item across 412 items; 9 tools + 403 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 52
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@commenteme/vtex-io-mcp@0.2.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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
add-block ~159
Generate a JSONC snippet for a VTEX IO block ready to paste into blocks.jsonc. Validates props against the block schema.
| Name | Type | Req | Description |
|---|---|---|---|
| blockId | string | – | Unique block identifier appended after #. Example: if blockId is "hero", result is "rich-text#hero". Defaults to the blockName. |
| blockName | string | yes | VTEX IO block name to generate (e.g. "rich-text", "flex-layout.row", "shelf", "image", "info-card") |
| children | array | – | List of child block references (e.g. ["rich-text#title", "image#hero"]) |
| props | object | – | Props to set on the block. Keys must match valid prop names for the block. |
No output schema declared.
No examples provided.
explain-concept ~113
Get full documentation for a VTEX concept by exact ID (e.g. "vtex-io-builders", "vtex-io-css-handles", "vtex-io-service-json"). Use search-concepts to find the right ID first.
| Name | Type | Req | Description |
|---|---|---|---|
| concept | string | yes | ID of the VTEX IO concept to explain (e.g. "workspaces", "css-handles", "builders", "events", "clients", "master-data", "vtex-cli", "service-json", "interfaces") |
No output schema declared.
No examples provided.
lookup-block-props ~83
Look up the props, description, and usage examples for any VTEX IO Store Framework block (e.g. rich-text, flex-layout.row, shelf, image, info-card)
| Name | Type | Req | Description |
|---|---|---|---|
| blockName | string | yes | Name of the VTEX IO block to look up (e.g. "rich-text", "flex-layout.row", "shelf", "image") |
No output schema declared.
No examples provided.
lookup-vtex-api ~124
Look up VTEX REST API reference (endpoints, auth, request/response models) for any VTEX API: catalog, orders, checkout, master-data, logistics, pricing, intelligent-search, session, headless-cms, promotions, payments-gateway, license-manager
| Name | Type | Req | Description |
|---|---|---|---|
| api | string | yes | API name or keyword to look up (e.g. "catalog", "orders", "checkout", "master-data", "logistics", "pricing", "intelligent-search", "session", "headless-cms", "promotions", "payments") |
No output schema declared.
No examples provided.
scaffold-graphql ~89
Generate a GraphQL schema and resolver files for a VTEX IO app, including schema.graphql and TypeScript resolver stubs for queries and mutations
| Name | Type | Req | Description |
|---|---|---|---|
| appName | string | yes | App name in kebab-case |
| mutations | array | – | GraphQL mutations to generate |
| queries | array | – | GraphQL queries to generate |
| vendor | string | yes | VTEX account vendor name |
No output schema declared.
No examples provided.
scaffold-node-service ~122
Generate a complete Node.js service scaffold for VTEX IO including index.ts, service.json, clients, and middleware handlers for specified routes and events
| Name | Type | Req | Description |
|---|---|---|---|
| appName | string | yes | App name in kebab-case |
| events | array | – | Event handlers to register |
| memory | number | – | Memory in MB (default: 256, max: 512) |
| routes | array | – | HTTP routes to expose |
| timeout | number | – | Request timeout in seconds (default: 10) |
| vendor | string | yes | VTEX account vendor name |
No output schema declared.
No examples provided.
scaffold-vtex-app ~142
Generate a complete VTEX IO app scaffold with manifest.json and all folder structures for the selected builders (store, react, node, graphql, styles, messages, admin, pixel)
| Name | Type | Req | Description |
|---|---|---|---|
| appName | string | yes | App name in kebab-case (e.g. "my-store-theme", "product-recommender") |
| builders | array | yes | List of VTEX IO builders to include in the app |
| description | string | – | App description |
| vendor | string | yes | VTEX account vendor name (e.g. "mystore", "vtex") |
| version | string | – | App version (default: "0.0.1") |
No output schema declared.
No examples provided.
search-concepts ~104
Search across 391 VTEX documentation files by keywords. Returns ranked results with excerpts. Use this to find concepts before calling explain-concept.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | number | – | Max number of results to return (default: 5, max: 10) |
| query | string | yes | Search query — keywords to find in VTEX documentation (e.g. "css handles", "master data triggers", "node builder routes", "catalog API", "checkout orderform") |
No output schema declared.
No examples provided.
search-courses ~127
Search for a term across all VTEX IO official courses (basic-blocks, layout-blocks, styles-course, store-block, service-course, admin, calling-commerce-apis, content-workflow, store-performance). Returns excerpts with surrounding context.
| Name | Type | Req | Description |
|---|---|---|---|
| courseId | string | – | Optionally restrict search to a specific course ID (e.g. "service-course", "store-block", "basic-blocks") |
| query | string | yes | Search term to find in VTEX IO courses (e.g. "flex-layout", "CSS handles", "service.json", "GraphQL resolver") |
No output schema declared.
No examples provided.
How do I install the VTEX IO MCP server?
VTEX IO MCP runs locally as an npm package, launched with npx -y @commenteme/vtex-io-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/vtex-io-mcp
claude mcp add commentemeapp-vtex-io-mcp -- npx -y @commenteme/vtex-io-mcp
What is the VTEX IO MCP server?
VTEX IO MCP is listed in the public MCP registry as io.github.commentemeapp/vtex-io-mcp. Scaffold VTEX IO apps, Node services and GraphQL, look up Store Framework block props, search docs. This page covers its npm package (@commenteme/vtex-io-mcp).
Is the VTEX IO MCP server safe to use?
VTEX IO MCP scores 67 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 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 VTEX IO MCP server expose?
VTEX IO MCP exposes 9 tools: lookup-block-props, add-block, scaffold-vtex-app, scaffold-node-service, scaffold-graphql, and 4 more. Their descriptions and schemas cost roughly 1,063 tokens of context every time the server is loaded.
Is the VTEX IO MCP server still maintained?
VTEX IO MCP is still listed as active in the MCP registry. We last reached this channel on 5 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 VTEX IO MCP server under?
VTEX IO 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.