Mcp Ecommerce Platform Profiler

com.mambabuiltPublished by mambabuilt.comv1.2.1Updated Nov 7, 2026

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

Overview

AI-generated overview

Profiles a storefront's ecommerce platform, payment providers and catalogue size by reading its public pages through an Apify actor.

What you can do
  • Profile a company domain's storefront: detect the ecommerce platform (Shopify, WooCommerce, Magento, BigCommerce, Salesforce Commerce, Squarespace, Wix, PrestaShop, commercetools) with confidence and evidence.
  • Inspect payment providers, subscription and marketplace apps, optionally reading the public cart page.
  • Estimate catalogue size, currencies and shipping destinations.
  • Return one flat 22-field JSON row per company, with coverage and fetch status.
When to use it
Useful for sales, GTM or research work that needs to know what platform and payment stack a prospect's store runs on, or how large its catalogue is, without manual inspection. It fits pipelines that want one flat row per company, for example stacked in a Clay table.
Requirements
Runs locally via npx, so Node.js 18 or newer is needed. Requires an Apify account and an Apify API token supplied in the APIFY_TOKEN environment variable. All detection runs on Apify, so network access to Apify is required.
Before you install
The APIFY_TOKEN secret is required and grants access to your Apify account. Runs are billed per event on Apify (actor start, company checked, platform detected, product count estimated), so costs accrue per lookup; max_charge_usd caps a run. The domain you submit is sent to Apify and the target storefront is fetched, including an optional public cart page read and a residential retry on 403/429.

Installation

In SourceWeft

  1. Open Mcp Ecommerce Platform Profiler in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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

Source: README.md at commit fae1028

Tools

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.

ParametersskipCachecompany_namecheckCheckoutcompany_domainmax_charge_usdescalateOnBlockincludeProductCountincludePaymentProviders

Version history

5
  1. v1.2.1LatestNov 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

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts