Mcp Ecommerce Platform Profiler

com.mambabuilt由 mambabuilt.com 發布v1.2.1更新於 Nov 7, 2026

Detect the ecommerce platform, payment providers and catalogue size behind a storefront.

概覽

AI 產生的概覽

透過 Apify actor 讀取商店公開頁面,辨識電商平台、支付服務商與商品目錄規模。

可以做什麼
  • 依公司網域分析商店:辨識電商平台(Shopify、WooCommerce、Magento、BigCommerce、Salesforce Commerce、Squarespace、Wix、PrestaShop、commercetools),並附上信心程度與證據。
  • 偵測支付服務商、訂閱與市集應用程式,可選擇讀取公開購物車頁面。
  • 估算商品數量、貨幣與配送目的地。
  • 每家公司回傳一列 22 個欄位的扁平 JSON,並附上覆蓋率與抓取狀態。
適用情境
適合業務、GTM 或研究情境,需要在不人工檢視的情況下了解潛在客戶商店使用哪個平台與支付方案、目錄有多大。也適合需要每家公司一列扁平資料、可直接堆疊進試算表的流程。
執行需求
透過 npx 在本機執行,需要 Node.js 18 或更新版本。需要 Apify 帳號,並以環境變數 APIFY_TOKEN 提供 Apify API 權杖。所有偵測都在 Apify 上執行,因此需要能連線至 Apify 的網路。
安裝前請注意
必須提供 APIFY_TOKEN 密鑰,它可存取你的 Apify 帳號。執行依事件在 Apify 計費(actor 啟動、公司檢查、平台辨識、商品數量估算),每次查詢都會產生費用;可用 max_charge_usd 限制單次執行成本。送出的網域會傳給 Apify,並會抓取目標商店,包括可選的公開購物車頁面讀取,以及遇到 403/429 時的住宅代理重試。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Mcp Ecommerce Platform Profiler,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

Ecommerce Platform Profiler MCP Server

[Glama score] [MCP Registry] [npm version] [npm downloads] [license] [mcpservers.org]

[Ecommerce Platform Profiler MCP server]

An MCP server that detects the ecommerce platform, payment providers and catalog size behind a storefront. It wraps the Mamba Labs Ecommerce Platform Profiler actor on Apify and returns a Clay-ready flat JSON row to any MCP client.

What's Inside

What it does

Give it a company domain and it reads the storefront and returns which ecommerce platform it runs on, which payment providers it loads, whether it sells subscriptions, roughly how many products it lists, and which currencies and shipping destinations it takes. One flat row per company.

Detected platforms include Shopify, WooCommerce, Magento, BigCommerce, Salesforce Commerce, Squarespace, Wix, PrestaShop and commercetools. Reads are static: the homepage, the sitemap, and optionally the public cart page. No browser is used, so a storefront that reveals its platform only after JavaScript runs is reported as not_extractable rather than labeled with the nearest guess. Confidence follows the kind of evidence, so a vendor header is high and a substring in the HTML is low.

All of the detection runs on Apify. This package is a thin client that calls the actor and hands back the result unchanged.

Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config:

json
{  "mcpServers": {    "mamba-ecommerce-platform-profiler": {      "command": "npx",      "args": ["-y", "@mambalabsdev/mcp-ecommerce-platform-profiler"],      "env": {        "APIFY_TOKEN": "your-apify-token"      }    }  }}

Get your token at https://console.apify.com/account/integrations, paste it in, and restart Claude Desktop. The profile_ecommerce_platform tool will be available.

Prerequisites

  • Node.js 18 or newer
  • An Apify account with an API token

Example prompts

  • "What ecommerce platform does allbirds.com run on?"
  • "Profile gymshark.com and include the payment providers loaded on the cart page."
  • "Does this storefront sell subscriptions, and roughly how many products does it list?"
  • "Check the platform for this domain but fail fast if the site blocks us."

Inputs

  • company_domain (optional): bare company domain, for example allbirds.com. This is the storefront that gets read, and it is the join key against every other actor in the fleet.
  • company_name (optional but strongly recommended): what the identity gate checks a discovered record against, so supplying it is the cheapest way to reduce wrong matches.
  • includeProductCount (optional): when true (the default) the catalog size is estimated, from the Shopify products endpoint where the store is Shopify and from the sitemap otherwise. It costs one or two extra requests.
  • includePaymentProviders (optional): when true (the default) the payment provider scripts loaded on the storefront are detected. Providers that load only inside a real checkout are invisible from the homepage, which is why checkCheckout exists.
  • checkCheckout (optional): when true the public cart page is also read, because several payment and buy now pay later providers load there and not on the homepage. This never adds an item, never starts a checkout and never submits anything. It is a plain read of a public URL and costs one extra request.
  • escalateOnBlock (optional): when true (the default) a storefront that answers 403 or 429 is retried once from a residential exit, because a bot challenge on a first read is common. Set false to fail fast and cheap.
  • skipCache (optional): when false (the default) a successful lookup is cached for seven days and reused. Set true to force a fresh fetch.
  • max_charge_usd (optional): a cost cap in USD for this run. The actor stops before an item that could take its charges past this amount. Omit it to rely on the maximum cost per run set in Apify.

Output

The tool returns the actor's flat JSON row for the company, with 22 snake_case fields and no nested objects. platform_confidence and platform_evidence travel with the detection rather than a bare label, coverage shows how much of the row was filled, and fetch_status says whether the read succeeded. See the Apify Store page for the full output schema.

Example output

json
{  "degraded": false,  "degradation_reason": null,  "company_domain": "allbirds.com",  "company_name": "Allbirds",  "ecommerce_platform": "shopify",  "platform_confidence": "high",  "platform_evidence": "header",  "platforms_all": "shopify",  "payment_providers": "apple_pay",  "has_subscriptions": false,  "subscription_apps": null,  "has_marketplace": false,  "product_count_estimate": 250,  "product_count_source": "products_json",  "product_count_exact": false,  "currencies": null,  "ships_to": null,  "pages_read": 2,  "escalated": false,  "coverage": 0.71,  "fetch_status": "ok",  "run_date": "2026-08-22T19:23:53.897Z"}

Features

  • Identifies the ecommerce platform a storefront runs on
  • Payment providers, subscription apps and marketplace apps
  • Catalog size estimate, currencies and shipping destinations
  • Static homepage and sitemap reads only, no browser
  • Confidence and evidence recorded per detection, not a bare label
  • Coverage reported per row, so a thin read is visible
  • 22 flat snake_case fields, one row per company

Pricing

Price per event on the Apify FREE plan, from the live pricing record; paid Apify plans pay less per event.

EventPrice (USD)
Actor Start (apify-actor-start)0.00005
Company checked (company-checked)0.0035
Platform detected (platform-detected)0.003
Product count estimated (product-count-estimated)0.0025

Full actor documentation

This server is a thin client and holds no detection logic. For the complete input and output reference, pricing, and run history, see the Apify Store page:

https://apify.com/mambalabs/ecommerce-platform-profiler


Mamba Labs GTM Suite

This server is one of the Mamba Labs GTM Suite MCP servers. Every actor in the suite takes a domain or a company and returns one flat row, so they stack in the same Clay table without reshaping anything. The actor behind this server is the Ecommerce Platform Profiler, immutable Apify actor ID 5G2NeYjBbQTjaTn9L.

Built by Mamba Labs | npm | Apify Store

License

MIT

Built by Mamba Labs. https://apify.com/mambalabs

來源:README.md,提交 fae1028

工具

1

profile_ecommerce_platform

Profile Ecommerce Platform

Detect which ecommerce platform a storefront runs on (Shopify, WooCommerce, Magento, BigCommerce, Salesforce Commerce, Squarespace, Wix, PrestaShop or commercetools), plus its payment providers, subscription and marketplace apps, an estimated catalogue size, currencies and shipping destinations. Returns one flat Clay ready row. Static homepage and sitemap reads only, no browser, so a storefront that reveals its platform only after JavaScript runs is reported as not_extractable rather than labelled with the nearest guess. Confidence follows the KIND of evidence: a vendor header is high, a substring in the HTML is low. Use it to qualify ecommerce accounts by platform before outreach, or to segment a store list by catalogue size and payment stack. Pass company_name with the domain to cut wrong matches. Requires an APIFY_TOKEN and consumes Apify credits per call.

輸入參數skipCachecompany_namecheckCheckoutcompany_domainmax_charge_usdescalateOnBlockincludeProductCountincludePaymentProviders

版本歷史

5
  1. v1.2.1最新Nov 5, 2026
  2. v1.2.0Oct 16, 2026
  3. v1.1.1Oct 6, 2026
  4. v1.1.0Oct 6, 2026
  5. v1.0.0Sep 16, 2026

評分

已滿足適用檢查項的 90%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分
  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分