mcp-ecommerce-platform-profiler
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from https://console.apify.com/account/integrations |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| profile_ecommerce_platformA | 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. Read only; requires an APIFY_TOKEN and consumes Apify credits per call. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool in the server, there is no possibility of confusing it with another tool. profile_ecommerce_platform has a singular, clearly described responsibility.
The single tool name follows a clear verb_noun pattern (profile_ecommerce_platform), which is consistent with common MCP naming conventions. There are no other tools to contradict this convention, so consistency cannot be fully exercised.
The server is intentionally narrow, but one tool is on the thin side and feels minimal for a domain that covers many detection dimensions. It is usable, but leaves no room for complementary operations such as batch profiling or evidence inspection.
The tool covers the core profiling domain well: platform detection, payment providers, apps, catalogue size, currencies, and shipping destinations. It gracefully handles non-extractable storefronts, though a truly complete surface might also expose raw evidence or allow batch/multiple URL processing.