Storefront Check
REMOTE · TOOLS.PROFITPATHER.COM
Audit any storefront from outside: ad tags, dead-tag detection, AI crawler access, feed readiness.
Available components
Last scanned (3 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 686 tokens (~171/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 15 Oct 26 59
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Probed https://tools.profitpather.com/store/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=profitpather.com | CN=WE1,O=Google Trust Services,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 415b597bd09397e50eddc696ddd42c15 |
| SANs: profitpather.com, tools.profitpather.com, *.tools.profitpather.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of tools.profitpather.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| profitpather.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tools.profitpather.com/store/mcp | Verified | 200 | |
| http (plaintext) | http://tools.profitpather.com/store/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_product_feed Audit a Shopify catalogue for feed readiness ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many products to sample, 1 to 250. Default 250. |
| url | string | yes | The Shopify store domain, for example example.com. |
No output schema declared.
No examples provided.
check_agent_readiness Check whether AI shopping agents can find and read a store ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The store's domain, for example example.com. |
No output schema declared.
No examples provided.
check_structured_data Check a page's structured data ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The exact page URL to inspect. Use a product URL to check Product markup. |
No output schema declared.
No examples provided.
detect_tracking_tags Find the advertising and analytics tags on a storefront ~144
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The storefront URL, for example example.com or https://example.com. |
| verify_google_ids | boolean | – | Check each Google id against Google Tag Manager to catch dead ids. Default true. |
No output schema declared.
No examples provided.
How do I install the Storefront Check MCP server?
Storefront Check is a hosted endpoint at https://tools.profitpather.com/store/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · tools.profitpather.com
claude mcp add --transport http com-profitpather-tools-storefront-check 'https://tools.profitpather.com/store/mcp'
What is the Storefront Check MCP server?
Storefront Check is an MCP server listed in the public MCP registry as com.profitpather.tools/storefront-check. Audit any storefront from outside: ad tags, dead-tag detection, AI crawler access, feed readiness. This page covers its hosted endpoint (https://tools.profitpather.com/store/mcp).
Is the Storefront Check MCP server safe to use?
Storefront Check scores 61 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Storefront Check MCP server expose?
Storefront Check exposes 4 tools: detect_tracking_tags, check_agent_readiness, check_structured_data, audit_product_feed. Their descriptions and schemas cost roughly 422 tokens of context every time the server is loaded.
Does the Storefront Check MCP server require authentication?
No. We connected to Storefront Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Storefront Check MCP server still maintained?
Storefront Check is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.