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 分