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.

io.github.48x-ai/marketbasketanalysis-mcp

NPM · @MARKETBASKETANALYSIS/MCP · SCANNED AUG 7

Co-purchase intelligence and merchant ops tools for AI shopping, ecommerce, and B2B agents

59 Trust /100
Trust breakdown (6 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 →

Supply Chain Security99
  • 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 126 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
Schema Quality & AI Usability67
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3130 tokens (~164/item across 19 items; 19 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 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
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.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @marketbasketanalysis/mcp

# add to Claude Code
claude mcp add 48x-ai-marketbasketanalysis-mcp -- npx -y @marketbasketanalysis/mcp
# add to Codex CLI
codex mcp add 48x-ai-marketbasketanalysis-mcp -- npx -y @marketbasketanalysis/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "48x-ai-marketbasketanalysis-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@marketbasketanalysis/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add 48x-ai-marketbasketanalysis-mcp --command npx --arg -y --arg @marketbasketanalysis/mcp
# ~/.hermes/config.yaml
mcp_servers:
  48x-ai-marketbasketanalysis-mcp:
    command: "npx"
    args: ["-y", "@marketbasketanalysis/mcp"]
// mcp.json
{
  "mcpServers": {
    "48x-ai-marketbasketanalysis-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@marketbasketanalysis/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 Aug 26 +15
    • Malware scan: unverified → pass security
    • Known CVEs: partial → pass security
    • Dependency health: partial → 0.89 functional
  • 6 Aug 26 +29
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 functional
    • MCP protocol: unverified → pass functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
    • First check of Tool coverage: 100 functional
    • First check of Schema quality: fail functional
  • 5 Aug 26 15

    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 Aug 2026 · Analysed npm/@marketbasketanalysis/[email protected]

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm
Dependencies 126 packages
Packages resolved 126
Stale 31
Tree resolution Complete
MCP tools · 19 exposed · ~3,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.

Tool Tokens
analyze_basket ~126

Run market-basket analysis on a proposed basket / bundle to score its cohesion. Given 2+ products, returns a cohesion score 0..1 representing how strongly they bind together (their affinity) in the merchant's order data. Use this to vet a proposed bundle BEFORE recommending it, so agents can avoid suggesting bundles that look plausible but have no statistical signal. Also useful for 'is this a good bundle?', 'analyze this basket', or 'do these products go together?' questions.

NameTypeReqDescription
product_idsarrayyesThe products in the proposed basket (2-6).

No output schema declared.

No examples provided.

execute_weekly_plan_action ~110

Execute a specific action from the merchant's weekly plan (publish bundle, run mining job, archive rule, etc.). Idempotent by action_id, safe to retry. Use this AFTER the merchant has confirmed which action from get_weekly_plan they want to run; do not call preemptively.

NameTypeReqDescription
action_idstringyesThe id of the action to execute, from get_weekly_plan.
confirmbooleanyesMust be true to actually execute. Guard against accidental dispatch.

No output schema declared.

No examples provided.

explain_drift ~162

Explain ONE drift alert: return its prior and current confidence (plus support, lift, and order sample count when the rule is still live) and a short plain-language narrative of how the pair moved versus the prior mining run. Use this when a merchant asks 'why did this pair drift?', 'explain this alert', or 'what changed for these two products?' after seeing it in get_drift_alerts. Different from get_drift_alerts: that lists the feed, this drills into a single alert_id with the change spelled out in a sentence. Handles a disappeared pair gracefully (only the prior confidence is available). BigCommerce only today.

NameTypeReqDescription
alert_idstringyesThe id of the drift alert to explain, from get_drift_alerts.

No output schema declared.

No examples provided.

explain_opportunity ~158

Explain ONE mined opportunity: return its support, confidence, lift, and order sample count plus a short plain-language narrative of why the pair is a good cross-sell. Use this when a merchant asks 'why is this a good cross-sell?', 'explain this opportunity', or 'why should I bundle these?' after seeing it in get_opportunities. Different from get_opportunities: that lists the ranked set, this drills into a single opportunity_id with the stats spelled out in a sentence. Different from get_rationale: rationale is a generic pair 'why', this is the specific mined opportunity's own numbers. BigCommerce only today.

NameTypeReqDescription
opportunity_idstringyesThe id of the opportunity to explain, from get_opportunities.

No output schema declared.

No examples provided.

find_substitutes ~207

For a given product, recommend the top substitute items that could REPLACE it (not complement it). Substitutes are the inverse of cross-sell: this answers 'what to buy instead', not 'what to buy with'. Use this when the user asks 'what's a substitute for X?', 'X is out of stock, what's a good alternative?', 'recommend a replacement for Y', 'find an equivalent product', or when a procurement agent needs to swap an unavailable SKU. Returns a ranked list with a similarity score and a reason (context_similar / category_match / vendor_match). Works for Shopify, Magento, and WooCommerce merchants.

NameTypeReqDescription
limitintegerMaximum number of substitutes to return. Default 3, max 6.
product_idstringyesProduct id, either the numeric storefront id (e.g. '8472918765') or the platform-specific GID/SKU. The id of the product the user wants to REPLACE.

No output schema declared.

No examples provided.

forecast_bundle ~168

For an inventory, purchasing, or merchant-ops agent: forecast weekly sales and recommend a buy quantity for a specific bundle over a configurable horizon. Uses additive Holt-Winters on the bundle's stored historical sales (demand forecasting). Use this when the agent asks 'how many of bundle X should I order?', 'what should I stock for the next N weeks?', 'what's the demand outlook for bundle Y?', or 'forecast the next 8 weeks for the camera bundle'.

NameTypeReqDescription
bundle_idstringyesBundle identifier (the platform-specific bundle/kit id).
horizon_weeksintegerForecast horizon in WEEKS. Default 8, range 1..52. The server converts this to days for the backend, so pass the number of weeks, not days.

No output schema declared.

No examples provided.

get_bundle_for_cart ~160

Given a list of products already in the cart, recommend products that frequently bundle with the cart to complete a high-confidence bundle. This is multi-item basket analysis for cart completion. Use when the user describes a multi-item cart and asks 'what else do I need?', 'what completes this set?', 'what's missing from this bundle?', 'recommend add-ons for this cart', or similar. Different from get_recommendations: this takes MULTIPLE products and returns items that pair with the cart as a whole, not single-item pairings.

NameTypeReqDescription
limitintegerMax suggestions to return. Default 3, max 6.
product_idsarrayyesList of product ids currently in the cart (numeric or GID/SKU).

No output schema declared.

No examples provided.

get_drift_alerts ~119

For a merchant-ops or analytics agent: list active drift alerts, the recommendation rules whose confidence has materially changed (weakened, strengthened, disappeared, emerged) versus the prior mining job. Use this when a merchant asks 'what's changed?', 'is my model still accurate?', 'are any rules drifting?', or wants to investigate a SKU swap / seasonal shift.

NameTypeReqDescription
limitintegerMax alerts to return. Default 10, max 50.
severitystringFilter alerts by severity. Default 'all'.

No output schema declared.

No examples provided.

get_forecast_alerts ~142

For an inventory or merchant-ops agent: list forecast-based alerts, the bundles with stockout risk, demand drop, demand spike, or an unreliable forecast curve. Use this when a merchant asks 'what's at risk of stockout?', 'which bundles are losing demand?', 'do I need to reorder anything?', or 'what should I restock?'. Pair with forecast_bundle to drill into a specific bundle.

NameTypeReqDescription
kindstringFilter by alert kind. Default 'all'.
limitintegerMax alerts to return. Default 10, max 50.
severitystringFilter by severity. Default 'all'.

No output schema declared.

No examples provided.

get_opportunities ~123

List the merchant's ranked bundle / cross-sell opportunities mined from order history, with support / confidence / lift / revenue-weighted score. Use this when a merchant asks 'what are my top opportunities?', 'show me the best bundles I haven't published yet', or 'what should I prioritize?'. Pair with triage_opportunity to act on a specific one.

NameTypeReqDescription
limitintegerMax opportunities to return. Default 10, max 50.
statusstringFilter by opportunity status. Defaults to 'proposed' (untriaged).

No output schema declared.

No examples provided.

get_rationale ~127

Fetch the one-sentence rationale for why product B is recommended alongside product A. Returns a short merchandiser-grade explanation ('these are commonly bought together by customers buying X') suitable for surfacing in a recommendation tile or chat reply. Use this after get_recommendations / get_bundle_for_cart when the agent or user asks 'why are these recommended together?' or 'explain this pairing'.

NameTypeReqDescription
product_idstringyesThe base product id (the antecedent in the recommendation rule).
related_product_idstringyesThe recommended product id (the consequent in the rule).

No output schema declared.

No examples provided.

get_recommendations ~166

For a given product, recommend the top complementary, frequently-bought-together products customers also bought, based on mined order-history association rules. This is the single-product cross-sell tool. Use this when the user asks 'what goes with X?', 'what should I bundle with X?', 'what do customers also buy with X?', 'recommend products to cross-sell with X', or similar single-product co-purchase questions. Works for Shopify, Magento, and WooCommerce merchants.

NameTypeReqDescription
limitintegerMaximum number of recommendations to return. Default 3, max 6.
product_idstringyesProduct id, either the numeric storefront id (e.g. '8472918765') or the platform-specific GID/SKU. Both are accepted.

No output schema declared.

No examples provided.

get_weekly_plan ~90

Fetch the current weekly action plan for the merchant: a ranked list of typed actions (publish opportunity, retire stale bundle, reorder inventory, investigate drift, etc.) the merchant should take this week. Use this when a merchant asks 'what should I work on this week?', 'what's on my plate?', 'show me my weekly plan', or wants a summary of pending tasks before opening the admin.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

mine_hui_itemsets ~164

Run high-utility itemset (HUI) mining on a caller-supplied payload of orders + per-line unit_profit. Returns top-K itemsets ranked by aggregate utility (sum of profit across all occurrences). Use this when an agent needs to evaluate which item combinations drive the most profit (not just frequency) for a specific time window or product subset. Plus or Enterprise tier required on the merchant account.

NameTypeReqDescription
min_utilitynumberMinimum utility threshold; itemsets below this are dropped.
ordersarrayyesOrder payload: each order has order_id + items[]. Each item has sku, quantity, unit_profit.
top_kintegerHow many top-utility itemsets to return. Default 20, max 100.

No output schema declared.

No examples provided.

predict_reorder ~253

For a sales-rep or inventory / account-management agent: predict when a B2B customer / account is due to reorder. Returns predicted next-order dates for every SKU the customer has ordered >=2 times, with confidence based on the regularity of their cadence (reorder prediction / replenishment forecasting). Bucketed into 'overdue' / 'due_soon' / 'on_track' / 'not_predictable'. Use this when the agent asks 'what's Acme Corp due to reorder?', 'when will customer X need more of Y?', 'show me stockout risks for my B2B accounts', or for proactive replenishment workflows. Works on the Shopify, BigCommerce, WooCommerce, and Magento backends. Not available on OroCommerce.

NameTypeReqDescription
customer_idstringyesThe customer id on the store's own platform. Shopify accepts either the numeric storefront id (e.g. '7654321') or the full GID (gid://shopify/Customer/7654321). BigCommerce, WooCommerce, and Magento…
product_idstringOptional: filter to a single product. Useful for 'when will customer X reorder product Y?'.

No output schema declared.

No examples provided.

propose_subscription_bundle ~343

Propose a recurring subscription bundle for a customer based on their first-order items. Given 1-5 seed products the customer has bought, returns a recurring subscription bundle (3-6 items) of the seeds plus complementary products, with a predicted cadence (median days between reorders), a 0..1 confidence score, and a rough monthly_value when prices are known. Use this when a merchant agent asks 'what should they subscribe to?', 'build a monthly subscription bundle from this order', 'propose a subscription bundle', 'recommend a recurring replenishment bundle', or 'what's the right subscription frequency for this customer?'. If a customer_id is supplied the tool blends in the customer's per-SKU reorder cadence; without one it falls back to the seed catalog cohesion alone. Works for Shopify, Magento, and WooCommerce merchants.

NameTypeReqDescription
cadence_daysintegerOptional target subscription frequency in days (e.g. 30 for monthly, 14 for biweekly). When supplied, the tool snaps the predicted cadence toward this target and weights candidates whose individual c…
customer_idstringOptional customer id (numeric storefront id or GID). When supplied, the tool pulls the customer's reorder-prediction history to anchor the cadence and confidence. Without this, the proposal uses seed…
kit_sizeintegerTarget total items in the subscription bundle (seeds + complements). Default 4, clamped to [3, 6].
seed_product_idsarrayyesProducts the customer bought in their first order (1-5). The proposed subscription bundle will include these plus complementary items.

No output schema declared.

No examples provided.

score_cross_sell ~149

Score the cross-sell strength (product affinity) between two specific products. Returns the confidence the merchant's real co-purchase data supports for the pair, or a clear 'no signal' result when there's no qualifying rule. Use this to validate a proposed pair before recommending it, or to answer 'is X a good cross-sell for Y?', 'how strong is the affinity between X and Y?', or 'how often are X and Y bought together?'.

NameTypeReqDescription
product_astringyesThe 'antecedent' product (the one the customer already has).
product_bstringyesThe 'consequent' product (the one being evaluated as a cross-sell).

No output schema declared.

No examples provided.

score_return_risk ~242

Predict return risk for a candidate bundle of 2-6 products. Returns the composite bundle return rate (max of items, since one returned item typically returns the whole bundle), each item's historical return rate, and a low/medium/high risk recommendation. Use this when the user asks 'will this bundle get returned?', 'predict return risk for these items', 'fashion bundle risk', 'is this set risky to ship together?', or when an agent is composing a bundle and wants to verify it won't tank the merchant's return KPIs. Backed by return-aware mining over the merchant's real order + refund history.

NameTypeReqDescription
product_idsarrayyesProduct ids for the candidate bundle. 2-6 items. Each id is either the numeric storefront id (e.g. '8472918765') or the platform-specific GID/SKU.
thresholdnumberOptional override for the 'high risk' cutoff. Defaults to 0.15 (15%). Items above this contribute to a stronger warning in the recommendation text. The low/medium/high classification itself uses fixe…

No output schema declared.

No examples provided.

triage_opportunity ~121

Pause, activate, or archive a specific opportunity from get_opportunities. State-mutating; guarded by confirm=true. Use this after the merchant has explicitly picked an opportunity to act on. Pass action='activate' to publish a proposed rule, 'pause' to temporarily hide an active one, 'archive' to permanently retire it.

NameTypeReqDescription
actionstringyesWhat to do with this opportunity.
confirmbooleanyesMust be true to dispatch. Guard against accidental triage.
opportunity_idstringyesOpportunity id from get_opportunities.

No output schema declared.

No examples provided.