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.

VTEX IO MCP

NPM · VTEX-IO-MCP · SCANNED OCT 7

Scaffold VTEX IO apps, Node services and GraphQL, look up Store Framework block props, search docs

Available components

+5 this week 77 Trust /100
Trust breakdown (7 categories)

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 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
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 Management37
  • Stability observed for 11 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
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
Install

How do I install the VTEX IO MCP server?

VTEX IO MCP runs locally as an npm package, launched with npx -y 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 · vtex-io-mcp

# add to Claude Code
claude mcp add zeluizr-vtex-io-mcp -- npx -y vtex-io-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "zeluizr-vtex-io-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "vtex-io-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "zeluizr-vtex-io-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "vtex-io-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add zeluizr-vtex-io-mcp -- npx -y vtex-io-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "zeluizr-vtex-io-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "vtex-io-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add zeluizr-vtex-io-mcp --command npx --arg -y --arg vtex-io-mcp
# ~/.hermes/config.yaml
mcp_servers:
  zeluizr-vtex-io-mcp:
    command: "npx"
    args: ["-y", "vtex-io-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "zeluizr-vtex-io-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "vtex-io-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add zeluizr-vtex-io-mcp -t stdio -c npx -a -y vtex-io-mcp
// mcp.json
{
  "mcpServers": {
    "zeluizr-vtex-io-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "vtex-io-mcp"
      ]
    }
  }
}
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.

  • 7 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 37. That category is still filling its 30-day observation window: 8 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.

  • 4 Oct 26 +4
    • Stability: unverified → 0.27 ▲ functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Sept 26 72

    First indexed and scored.

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 7 Oct 2026 · Analysed npm/vtex-io-mcp@0.1.8

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 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~1,063 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
add-block ~159

Generate a JSONC snippet for a VTEX IO block ready to paste into blocks.jsonc. Validates props against the block schema.

NameTypeReqDescription
blockIdstring–Unique block identifier appended after #. Example: if blockId is "hero", result is "rich-text#hero". Defaults to the blockName.
blockNamestringyesVTEX IO block name to generate (e.g. "rich-text", "flex-layout.row", "shelf", "image", "info-card")
childrenarray–List of child block references (e.g. ["rich-text#title", "image#hero"])
propsobject–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.

NameTypeReqDescription
conceptstringyesID 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)

NameTypeReqDescription
blockNamestringyesName 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

NameTypeReqDescription
apistringyesAPI 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

NameTypeReqDescription
appNamestringyesApp name in kebab-case
mutationsarray–GraphQL mutations to generate
queriesarray–GraphQL queries to generate
vendorstringyesVTEX 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

NameTypeReqDescription
appNamestringyesApp name in kebab-case
eventsarray–Event handlers to register
memorynumber–Memory in MB (default: 256, max: 512)
routesarray–HTTP routes to expose
timeoutnumber–Request timeout in seconds (default: 10)
vendorstringyesVTEX 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)

NameTypeReqDescription
appNamestringyesApp name in kebab-case (e.g. "my-store-theme", "product-recommender")
buildersarrayyesList of VTEX IO builders to include in the app
descriptionstring–App description
vendorstringyesVTEX account vendor name (e.g. "mystore", "vtex")
versionstring–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.

NameTypeReqDescription
maxResultsnumber–Max number of results to return (default: 5, max: 10)
querystringyesSearch 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.

NameTypeReqDescription
courseIdstring–Optionally restrict search to a specific course ID (e.g. "service-course", "store-block", "basic-blocks")
querystringyesSearch term to find in VTEX IO courses (e.g. "flex-layout", "CSS handles", "service.json", "GraphQL resolver")

No output schema declared.

No examples provided.

Common questions

What is the VTEX IO MCP server?

VTEX IO MCP is listed in the public MCP registry as io.github.zeluizr/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 (vtex-io-mcp).

Is the VTEX IO MCP server safe to use?

VTEX IO MCP scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 7 October 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 7 October 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.