Storefront Check

Audit any storefront from outside: ad tags, dead-tag detection, AI crawler access, feed readiness.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
100%
Naming quality
95%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~529Tokens (tool definitions)
~625 BTypical response size
Minimal attention impact (0.41% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "storefront-check": {
      "url": "https://tools.profitpather.com/store/mcp"
    }
  }
}

Remote endpoints

https://tools.profitpather.com/store/mcpstreamable-http

What it can do

Tool inventory

Tools (4)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢detect_tracking_tags(url, verify_google_ids)

Reads a public storefront and reports every advertising, analytics and marketing tag visible in its HTML, with the actual measurement ids. It then verifies each Google id against Google Tag Manager, because an id Google does not recognise returns 404 and silently stops gtag from initialising, which means a campaign can spend for months while recording zero conversions. Use this to explain why conversion tracking is wrong, or to see what a store you have no access to is running.

Input Schema

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "The storefront URL, for example example.com or https://example.com."
    },
    "verify_google_ids": {
      "type": "boolean",
      "description": "Check each Google id against Google Tag Manager to catch dead ids. Default true."
    }
  },
  "required": [
    "url"
  ]
}
🟢check_agent_readiness(url)

Determines whether an AI agent can actually discover and parse a store: whether robots.txt permits each major AI crawler by name, whether a sitemap, llms.txt, product feed or MCP endpoint exists, and whether the catalogue is machine readable. Use this when asked why a store never appears in AI assistants or agent shopping results.

Input Schema

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "The store's domain, for example example.com."
    }
  },
  "required": [
    "url"
  ]
}
🟢check_structured_data(url)

Parses every JSON-LD block on a page and reports the schema.org types found, blocks that fail to parse, and whether the types a shopping agent looks for are present. Point it at a product page to check Product and Offer markup, or at a homepage to check Organization and WebSite.

Input Schema

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "The exact page URL to inspect. Use a product URL to check Product markup."
    }
  },
  "required": [
    "url"
  ]
}
⚪audit_product_feed(url, limit)

Reads a Shopify store's public products.json and reports what would break a Google Merchant Center or Meta catalogue feed: missing barcodes, absent weights, unpriced or unavailable variants, and thin descriptions. Shopify-only, because products.json is a Shopify endpoint.

Input Schema

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "The Shopify store domain, for example example.com."
    },
    "limit": {
      "type": "integer",
      "description": "How many products to sample, 1 to 250. Default 250."
    }
  },
  "required": [
    "url"
  ]
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded4 tools