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.

Swell MCP

NPM · SWELL-MCP

Model Context Protocol server for Swell e-commerce platform integration with AI assistants

Available components

0 this week 87 Trust /100

Last scanned (12 hours ago)

Scores higher than 91% of npm servers

Category E-commerce

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 Security74
  • 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
  • Declares code that runs automatically (postinstall) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
  • 39 of 119 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to devkindhq/swell-mcp). View diagnostics → Pass
  • Clear OSI-approved license (ISC).Pass
  • Actively maintained (last published 175 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2130 tokens (~152/item across 14 items; 14 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 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
What we tested

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 →

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.

  • 6 Nov 26 +1
    • Stability: 0.97 → pass security
  • 4 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 30 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 +1
    • Stability: 0.97 → pass security
    • Security disclosure: fail → unverified ▼ functional
  • 27 Oct 26 −1
    • Stability: pass → 0.93 functional
  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 17 Oct 26 +2
    • Stability: 0.83 → pass security
  • 16 Oct 26 −2
    • Stability: pass → 0.83 functional
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 6 Nov 2026 · Analysed npm/swell-mcp@1.1.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo devkindhq/swell-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/devkindhq/swell-mcp/.github/workflows/ci-semantic-release.yml@refs/heads/main
Rekor log index 1544383389
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:aa99823c77bf593bb7f7df73576b6594a08cc4a4afc42e4eb63427166d58165889417804e39ee9759d1afb103cf7201ea289465ecfa9aa33e71540ebf

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
postinstall Not reviewed node scripts/ensure-executable.js

Background: Why install scripts are a supply-chain risk →

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 119 packages
Packages resolved 119
Stale 39
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 14 exposed · ~2,130 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
swell_check_stock ~82

Check current stock levels and stock status for a specific product in your Swell store. Returns detailed stock information including levels, status, and availability messages. Optionally includes variant-level stock information.

NameTypeReqDescription
includeVariantsboolean–Whether to include variant stock information (default: true)
productIdstringyesThe ID of the product to check stock for

No output schema declared.

No examples provided.

swell_get_customer ~105

Get detailed information for a specific customer from your Swell store. Returns comprehensive customer profile including personal information, addresses, order history, and customer analytics. Use this tool when you need complete customer information.

NameTypeReqDescription
customerIdstringyesThe ID of the customer to retrieve
expandarray–Fields to expand in response (default: ["orders", "addresses"])
includeOrderHistoryboolean–Whether to include order history in the response (default: true)

No output schema declared.

No examples provided.

swell_get_order ~95

Get detailed information for a specific order from your Swell store. Returns comprehensive order details including items, customer information, billing and shipping addresses, payment details, and order history. Use this tool when you need complete order information.

NameTypeReqDescription
expandarray–Fields to expand in response (default: ["items", "account", "billing", "shipping"])
orderIdstringyesThe ID of the order to retrieve

No output schema declared.

No examples provided.

swell_get_product ~92

Get detailed information for a specific product from your Swell store. Returns comprehensive product details including variants, categories, images, pricing, inventory, SEO information, and custom attributes. Use this tool when you need complete product information.

NameTypeReqDescription
expandarray–Fields to expand in response (default: ["variants", "categories", "images"])
productIdstringyesThe ID of the product to retrieve

No output schema declared.

No examples provided.

swell_list_customers ~213

List customers from your Swell store with search and filtering options. Supports filtering by email, date range, and various sorting options. Returns a formatted table of customers with basic information including name, email, order count, total value, and registration date.

NameTypeReqDescription
dateFromstring–Filter customers created from this date (ISO format: YYYY-MM-DD)
dateTostring–Filter customers created to this date (ISO format: YYYY-MM-DD)
emailstring–Filter by specific email address
expandarray–Fields to expand in response (e.g., ["orders", "addresses"])
limitinteger–Number of customers per page (max: 100, default: 20)
pageinteger–Page number for pagination (default: 1)
searchstring–Search customers by name or email
sortstring–Sort order (e.g., "date_created_desc", "name_asc", "order_value_desc")

No output schema declared.

No examples provided.

swell_list_orders ~213

List orders from your Swell store with filtering options. Supports filtering by status, customer, date range, and various sorting options. Returns a formatted table of orders with basic information including order number, customer, status, total, and dates.

NameTypeReqDescription
customerIdstring–Filter by customer ID
dateFromstring–Filter orders from this date (ISO format: YYYY-MM-DD)
dateTostring–Filter orders to this date (ISO format: YYYY-MM-DD)
expandarray–Fields to expand in response (e.g., ["items", "account", "billing", "shipping"])
limitinteger–Number of orders per page (max: 100, default: 20)
pageinteger–Page number for pagination (default: 1)
sortstring–Sort order (e.g., "date_created_desc", "date_created_asc", "grand_total_desc")
statusstring–Filter by order status

No output schema declared.

No examples provided.

swell_list_products ~195

List products from your Swell store with filtering and pagination options. Supports filtering by active status, category, tags, and various sorting options. Returns a formatted table of products with basic information including ID, name, SKU, price, stock status, and availability.

NameTypeReqDescription
activeboolean–Filter by active status (true for active only, false for inactive only)
categorystring–Filter by category slug or ID
expandarray–Fields to expand in response (e.g., ["variants", "categories", "images"])
limitinteger–Number of products per page (max: 100, default: 20)
pageinteger–Page number for pagination (default: 1)
sortstring–Sort order (e.g., "date_created_desc", "name_asc", "price_asc")
tagsarray–Filter by product tags

No output schema declared.

No examples provided.

swell_search_customers ~197

Search for customers in your Swell store using text queries. Searches across customer names, email addresses, and phone numbers. Returns ranked results with match information and supports filtering by date range and sorting options.

NameTypeReqDescription
dateFromstring–Filter customers created from this date (ISO format: YYYY-MM-DD)
dateTostring–Filter customers created to this date (ISO format: YYYY-MM-DD)
expandarray–Fields to expand in response (e.g., ["orders", "addresses"])
limitinteger–Number of customers per page (max: 100, default: 20)
pageinteger–Page number for pagination (default: 1)
querystringyesSearch query to find customers (searches name, email, phone)
sortstring–Sort order (e.g., "relevance", "name_asc", "date_created_desc")

No output schema declared.

No examples provided.

swell_search_products ~198

Search for products in your Swell store using text queries with optional filtering. Searches across product names, SKUs, descriptions, and tags. Returns ranked results with match information and supports the same filtering options as product listing.

NameTypeReqDescription
activeboolean–Filter by active status (true for active only, false for inactive only)
categorystring–Filter by category slug or ID
expandarray–Fields to expand in response (e.g., ["variants", "categories", "images"])
limitinteger–Number of products per page (max: 100, default: 20)
pageinteger–Page number for pagination (default: 1)
querystringyesSearch query to find products
sortstring–Sort order (e.g., "relevance", "name_asc", "price_asc")
tagsarray–Filter by product tags

No output schema declared.

No examples provided.

swell_update_customer ~168

Update customer information in your Swell store. Allows modification of customer details including name, email, phone, notes, tags, and marketing preferences. Use this tool to correct customer information or update their profile.

NameTypeReqDescription
customerIdstringyesThe ID of the customer to update
emailstring–Customer's email address
emailOptinboolean–Email marketing opt-in status
firstNamestring–Customer's first name
groupIdstring–Customer group ID
lastNamestring–Customer's last name
notesstring–Customer notes
phonestring–Customer's phone number
smsOptinboolean–SMS marketing opt-in status
tagsarray–Customer tags

No output schema declared.

No examples provided.

swell_update_order_status ~95

Update the status of an order in your Swell store. Allows changing order status to pending, payment_pending, delivery_pending, complete, or canceled. Optionally add notes about the status change. Returns the updated order information.

NameTypeReqDescription
notesstring–Optional notes about the status change
orderIdstringyesThe ID of the order to update
statusstringyesNew status for the order

No output schema declared.

No examples provided.

swell_update_product ~223

Update product information in your Swell store. Allows modification of product details including name, description, pricing, stock, SEO fields, categories, tags, and custom attributes. Returns a summary of changes made with before/after values.

NameTypeReqDescription
activeboolean–Product active status
attributesobject–Custom product attributes
categoriesarray–Product categories (IDs or slugs)
descriptionstring–Product description
metaDescriptionstring–SEO meta description
metaTitlestring–SEO meta title
namestring–Product name
pricenumber–Product price (must be greater than 0)
productIdstringyesThe ID of the product to update
salePrice––Product sale price (must be greater than 0, null to remove)
skustring–Product SKU
stockLevelinteger–Stock level (must be non-negative)
stockStatusstring–Stock status
tagsarray–Product tags

No output schema declared.

No examples provided.

swell_update_product_pricing ~116

Update pricing information for a product in your Swell store. Allows modification of regular price, sale price, and currency. Includes validation to ensure sale price is not higher than regular price.

NameTypeReqDescription
currencystring–Currency code (e.g., USD, EUR)
pricenumber–Regular price (must be greater than 0)
productIdstringyesThe ID of the product to update pricing for
salePrice––Sale price (must be greater than 0, null to remove)

No output schema declared.

No examples provided.

swell_update_product_stock ~138

Update stock-specific information for a product in your Swell store. Allows modification of stock levels, stock status, and stock tracking settings. Use this tool for focused stock management operations.

NameTypeReqDescription
orderIdstring–Optional order ID when adjustment is related to an order
productIdstringyesThe ID of the product to update stock for
quantityintegeryesQuantity adjustment (positive to increase, negative to decrease)
reasonstring–Reason for the stock adjustment
reasonMessagestring–Optional message describing the reason
variantIdstring–Optional variant ID for variant-level adjustments

No output schema declared.

No examples provided.

Install

How do I install the Swell MCP server?

Swell MCP runs locally as an npm package, launched with npx -y swell-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 · swell-mcp

# add to Claude Code
claude mcp add devkindhq-swell -- npx -y swell-mcp
Common questions

What is the Swell MCP server?

Swell MCP is listed in the public MCP registry as io.github.devkindhq/swell. Model Context Protocol server for Swell e-commerce platform integration with AI assistants. This page covers its npm package (swell-mcp).

Is the Swell MCP server safe to use?

Swell MCP scores 87 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 6 November 2026. Its build provenance is signed and verified. 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 Swell MCP server expose?

Swell MCP exposes 14 tools: swell_list_products, swell_get_product, swell_search_products, swell_check_stock, swell_update_product, and 9 more. Their descriptions and schemas cost roughly 2,130 tokens of context every time the server is loaded.

Is the Swell MCP server still maintained?

Swell MCP is still listed as active in the MCP registry. We last reached this channel on 6 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 Swell MCP server under?

Swell MCP declares the ISC 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 Swell MCP server?

VerifyMCP ran 16 checks on Swell 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.