Vtex (leosepulveda) MCP Server

mcp-vtex npm v1.6.0

Published by leosepulveda — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for VTEX API - Complete integration for e-commerce management

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

medium Hardcoded egress to an external endpoint (dist/vtex-client.js)MTC-SRC-003

In the server's implementation (`dist/vtex-client.js:885`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const response = await axios.get(`https://${this.accountName}.${this.environment}.com.br/api/checkout/pub/orderForm/${o

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/vtex-client.js

Tools 131

Each tool and what it can reach — statically extracted from the published source.

  • vtex_send_emailnetwork egress
  • vtex_add_coupon_to_cartno sensitive capability
  • vtex_add_item_to_cartno sensitive capability
  • vtex_approve_reviewno sensitive capability
  • vtex_approve_skuno sensitive capability
  • vtex_archive_couponno sensitive capability
  • vtex_archive_promotionno sensitive capability
  • vtex_assign_sku_specification_valueno sensitive capability
  • vtex_authenticate_userno sensitive capability
  • vtex_autocompleteno sensitive capability
Show 121 more tools ↓
  • vtex_cancel_orderno sensitive capability
  • vtex_cancel_subscriptionno sensitive capability
  • vtex_clear_cartno sensitive capability
  • vtex_create_app_tokenno sensitive capability
  • vtex_create_brandno sensitive capability
  • vtex_create_categoryno sensitive capability
  • vtex_create_cms_templateno sensitive capability
  • vtex_create_couponno sensitive capability
  • vtex_create_dockno sensitive capability
  • vtex_create_documentno sensitive capability
  • vtex_create_email_templateno sensitive capability
  • vtex_create_gift_cardno sensitive capability
  • vtex_create_gift_card_transactionno sensitive capability
  • vtex_create_or_update_priceno sensitive capability
  • vtex_create_payment_providerno sensitive capability
  • vtex_create_productno sensitive capability
  • vtex_create_promotionno sensitive capability
  • vtex_create_reviewno sensitive capability
  • vtex_create_skuno sensitive capability
  • vtex_create_specificationno sensitive capability
  • vtex_create_specification_fieldno sensitive capability
  • vtex_create_specification_field_valueno sensitive capability
  • vtex_create_specification_groupno sensitive capability
  • vtex_create_subscriptionno sensitive capability
  • vtex_create_warehouseno sensitive capability
  • vtex_delete_brandno sensitive capability
  • vtex_delete_categoryno sensitive capability
  • vtex_delete_cms_templateno sensitive capability
  • vtex_delete_dockno sensitive capability
  • vtex_delete_documentno sensitive capability
  • vtex_delete_payment_providerno sensitive capability
  • vtex_delete_priceno sensitive capability
  • vtex_delete_productno sensitive capability
  • vtex_delete_reviewno sensitive capability
  • vtex_delete_warehouseno sensitive capability
  • vtex_deny_skuno sensitive capability
  • vtex_get_brandno sensitive capability
  • vtex_get_categoryno sensitive capability
  • vtex_get_client_by_emailno sensitive capability
  • vtex_get_cms_templateno sensitive capability
  • vtex_get_computed_priceno sensitive capability
  • vtex_get_couponno sensitive capability
  • vtex_get_dockno sensitive capability
  • vtex_get_documentno sensitive capability
  • vtex_get_email_templateno sensitive capability
  • vtex_get_facetsno sensitive capability
  • vtex_get_gift_cardno sensitive capability
  • vtex_get_gift_card_by_codeno sensitive capability
  • vtex_get_inventoryno sensitive capability
  • vtex_get_orderno sensitive capability
  • vtex_get_orderformno sensitive capability
  • vtex_get_payment_providerno sensitive capability
  • vtex_get_priceno sensitive capability
  • vtex_get_productno sensitive capability
  • vtex_get_product_and_sku_idsno sensitive capability
  • vtex_get_product_by_identifierno sensitive capability
  • vtex_get_promotionno sensitive capability
  • vtex_get_reviewno sensitive capability
  • vtex_get_review_summaryno sensitive capability
  • vtex_get_segmentno sensitive capability
  • vtex_get_seller_commissionsno sensitive capability
  • vtex_get_sessionno sensitive capability
  • vtex_get_skuno sensitive capability
  • vtex_get_sku_approval_statusno sensitive capability
  • vtex_get_sku_by_refidno sensitive capability
  • vtex_get_sku_specificationsno sensitive capability
  • vtex_get_specification_fieldno sensitive capability
  • vtex_get_subscriptionno sensitive capability
  • vtex_get_transactionno sensitive capability
  • vtex_get_user_profileno sensitive capability
  • vtex_get_warehouseno sensitive capability
  • vtex_invite_sellerno sensitive capability
  • vtex_invoice_orderno sensitive capability
  • vtex_list_app_tokensno sensitive capability
  • vtex_list_brandsno sensitive capability
  • vtex_list_categoriesno sensitive capability
  • vtex_list_category_specificationsno sensitive capability
  • vtex_list_cms_templatesno sensitive capability
  • vtex_list_couponsno sensitive capability
  • vtex_list_docksno sensitive capability
  • vtex_list_email_templatesno sensitive capability
  • vtex_list_gift_card_providersno sensitive capability
  • vtex_list_gift_cardsno sensitive capability
  • vtex_list_inventory_by_warehouseno sensitive capability
  • vtex_list_ordersno sensitive capability
  • vtex_list_payment_methodsno sensitive capability
  • vtex_list_payment_providersno sensitive capability
  • vtex_list_pricesno sensitive capability
  • vtex_list_productsno sensitive capability
  • vtex_list_promotionsno sensitive capability
  • vtex_list_reviewsno sensitive capability
  • vtex_list_sellersno sensitive capability
  • vtex_list_skusno sensitive capability
  • vtex_list_specification_field_valuesno sensitive capability
  • vtex_list_specification_groupsno sensitive capability
  • vtex_list_subscriptionsno sensitive capability
  • vtex_list_warehousesno sensitive capability
  • vtex_pause_subscriptionno sensitive capability
  • vtex_remove_item_from_cartno sensitive capability
  • vtex_search_documentsno sensitive capability
  • vtex_search_productsno sensitive capability
  • vtex_simulate_shippingno sensitive capability
  • vtex_start_handlingno sensitive capability
  • vtex_unarchive_promotionno sensitive capability
  • vtex_update_brandno sensitive capability
  • vtex_update_categoryno sensitive capability
  • vtex_update_dockno sensitive capability
  • vtex_update_documentno sensitive capability
  • vtex_update_email_templateno sensitive capability
  • vtex_update_inventoryno sensitive capability
  • vtex_update_item_quantityno sensitive capability
  • vtex_update_payment_providerno sensitive capability
  • vtex_update_productno sensitive capability
  • vtex_update_promotionno sensitive capability
  • vtex_update_reviewno sensitive capability
  • vtex_update_seller_commissionno sensitive capability
  • vtex_update_sessionno sensitive capability
  • vtex_update_skuno sensitive capability
  • vtex_update_subscriptionno sensitive capability
  • vtex_update_warehouseno sensitive capability
  • vtex_validate_tokenno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.6.0 latest A 96/100 1 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-vtex/badge.svg)](https://mcptrustchecker.com/registry/mcp-vtex)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-vtex"><img src="https://mcptrustchecker.com/registry/mcp-vtex/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-vtex/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan mcp-vtex --online

Use the free API → How scoring works

Other implementations of Vtex 3

Independent packages implementing the same tool, scanned with the same engine. Compare all 4 side by side →

More in Productivity & Workflow