# StoreTechScan — Ecommerce Tech Stack & ICP (remote · storetechscan.ytriple.dev)

Bulk ecommerce tech stack, Shopify prices, AI ICP fit, contacts. 25/day free; agents buy credits.

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `storetechscan.ytriple.dev`: 67/100 (this document), [markdown](https://verifymcp.io/servers/dev-ytriple-storetechscan-storetechscan/storetechscan.md), [page](https://verifymcp.io/servers/dev-ytriple-storetechscan-storetechscan/storetechscan)

## Channel facts

- Endpoint: `https://storetechscan.ytriple.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1343 tokens (~134/item across 10 items; 7 tools + 3 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 58% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the StoreTechScan — Ecommerce Tech Stack & ICP MCP server?

StoreTechScan — Ecommerce Tech Stack & ICP is a hosted endpoint at https://storetechscan.ytriple.dev/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.

### Claude

```bash
claude mcp add --transport http dev-ytriple-storetechscan-storetechscan 'https://storetechscan.ytriple.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-ytriple-storetechscan-storetechscan": {
      "url": "https://storetechscan.ytriple.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-ytriple-storetechscan-storetechscan": {
      "type": "http",
      "url": "https://storetechscan.ytriple.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-ytriple-storetechscan-storetechscan]
url = "https://storetechscan.ytriple.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-ytriple-storetechscan-storetechscan": {
      "type": "remote",
      "url": "https://storetechscan.ytriple.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-ytriple-storetechscan-storetechscan --url 'https://storetechscan.ytriple.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-ytriple-storetechscan-storetechscan:
    url: "https://storetechscan.ytriple.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-ytriple-storetechscan-storetechscan": {
      "Transport": "http",
      "Url": "https://storetechscan.ytriple.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-ytriple-storetechscan-storetechscan -t streamable-http -u 'https://storetechscan.ytriple.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-ytriple-storetechscan-storetechscan": {
      "type": "http",
      "url": "https://storetechscan.ytriple.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 67, +1)

- [functional regression] Schema quality: 121 → 134
- [functional improvement] Tool coverage: 47% → 58%
- [functional] Server version: 1.1.1 → 1.2.0
- [functional] New tool “inspect_product_url”
- [cosmetic] “inspect_domains” added an optional parameter “include_evidence”
- [cosmetic] “inspect_domains” added an optional parameter “profile”

### 2026-11-20 (score 66, 0)

- [functional] Server version: 1.1.0 → 1.1.1

### 2026-11-19 (score 66, +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.

### 2026-11-18 (score 65, 0)

- [security] Tool “check_credits” rewrote its description, which is the text the model reads
- [functional] Server version: 1.0.0 → 1.1.0

### 2026-11-17 (score 65, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-16 (score 64)

First indexed and scored.

## MCP tools (7)

### `inspect_domains` (~407 tokens)

Inspect Ecommerce & Company Domains

Live 4-stage enrichment for 1–25 unique domains per call: detects ecommerce platforms & marketing/support/pixel stack (Shopify, WooCommerce, Klaviyo, Gorgias, Recharge, Meta/TikTok Pixel, GA4), samples public Shopify /products.json catalog counts & native-currency min/median/max prices, scores 1.0–5.0 ICP prospect fit + active-merchant check + wholesale/B2B signal, and extracts public same-domain role emails (hello@, sales@) & social URLs. Pass multiple domains together in one array rather than calling 1 domain at a time. Paid mode (via HTTP header Authorization: Bearer zsk_live_... or X-API-Key) debits 1 credit per reachable billable domain ($0 for DNS/TLS/timeout/5xx/429/WAF failures), enables calibrated AI ICP scoring, and returns a durable job_id recoverable via get_inspection_results.

Input parameters:

- `b2b_wholesale_only` (boolean): Optional filter: return only domains with detected B2B, trade, or wholesale signals.
- `domains` (required)
- `include_evidence` (boolean): Optional: return auditable detection evidence[] entries even on the default ecommerce profile.
- `min_fit_score` (number): Optional filter: minimum 1.0–5.0 ICP prospect fit score (e.g. 3.5 or 4.0).
- `platform` (string): Optional filter: match primary platform or detected tech (e.g. "Shopify", "WooCommerce", "Klaviyo").
- `profile` (string): Optional inspection depth: ecommerce (default 4-stage ecommerce enrichment), tech_stack (fast 200+ Web/SaaS fingerprints + passive MX/TXT/CNAME/NS DNS + evidence[]), or full (both).
- `real_merchant_only` (boolean): Optional filter: return only verified active merchants/operators (excludes parked/empty stores).

### `inspect_product_url` (~180 tokens)

Inspect Live Ecommerce Product URL (Price, Variants & Availability)

Probe 1–10 public Shopify, WooCommerce, BigCommerce, or Schema.org DTC product URLs for live title, brand, native currency, price, compare-at price, variants, and explicit public available: true/false status. Unreachable, rate-limited, or WAF-blocked URLs return billable: false ($0). Paid mode (via HTTP header Authorization: Bearer zsk_live_... or X-API-Key) debits 1 credit per reachable billable domain ($0 for DNS/TLS/timeout/5xx/429/WAF failures), enables calibrated AI ICP scoring, and returns a durable job_id recoverable via get_inspection_results.

Input parameters:

- `url` (string): Single public product URL (use either url or urls).
- `urls` (array): Array of 1 to 10 public product URLs.

### `get_inspection_results` (~112 tokens)

Retrieve Saved Inspection Batch Results

Retrieve saved results for a previously submitted StoreTechScan job_id (from inspect_domains or web workspace) at 0 credit cost. Useful if a network connection dropped during an inspection.

Input parameters:

- `b2b_wholesale_only` (boolean)
- `job_id` (string, required): The job_id (e.g. "job_...") returned by inspect_domains or check_credits.
- `min_fit_score` (number)
- `platform` (string)
- `real_merchant_only` (boolean)

### `check_credits` (~61 tokens)

Check StoreTechScan Credits & Quota

Check your StoreTechScan credit balance and recent ledger transactions (when authenticated via Authorization: Bearer or X-API-Key HTTP header), or view the anonymous one-time 25-domain free trial policy and pay-as-you-go pack pricing. Costs 0 credits.

### `buy_credits` (~139 tokens)

Buy StoreTechScan Credits

Create a one-time credit pack checkout for a human to pay in their browser. Show only checkout_url to the human; keep session_id and claim_token with the agent and never put claim_token in a browser URL. After payment, poll claim_purchase every 10–15 seconds for up to 15 minutes. The API key appears only in the claim_purchase tool result, once with a 15-minute same-IP retry grace window. To top up an existing account, authenticate this MCP connection with its Bearer or X-API-Key header before calling.

Input parameters:

- `email` (string): Optional buyer email for checkout.
- `package_id` (string, required)

### `claim_purchase` (~117 tokens)

Claim Purchased StoreTechScan Credits

Poll a purchase created by buy_credits using the agent-held session_id and claim_token. While ready is false, wait retry_after_seconds before retrying (up to 15 minutes). Once the human has paid, returns the API key for the agent to store securely and use in the MCP connection or REST Authorization header. Keep the claim token out of the browser; key retrieval can be retried from the same IP for 15 minutes after the first successful claim.

Input parameters:

- `claim_token` (string, required)
- `session_id` (string, required)

### `get_ecommerce_benchmark_2026` (~113 tokens)

Get 2026 Ecommerce Tech & Rate-Limit Benchmark

Retrieve empirical benchmark findings across 235 deduplicated real storefronts comparing unpaced burst HTTP (29.4% reachability, 155 HTTP 429s) vs. paced inspection (92.8% reachability, 95.9% cohort consistency, 100% zero-drift native-currency price medians). Costs 0 credits.

Input parameters:

- `format` (string): Return structured JSON summary ("summary", default) or include raw CC BY 4.0 CSV ("csv").

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-ytriple-storetechscan-storetechscan/storetechscan#diagnostics

## Score history

- 2026-11-21: 67
- 2026-11-20: 66
- 2026-11-19: 66
- 2026-11-18: 65
- 2026-11-17: 65
- 2026-11-16: 64

## Common questions

### What is the StoreTechScan — Ecommerce Tech Stack & ICP MCP server?

StoreTechScan — Ecommerce Tech Stack & ICP is an MCP server listed in the public MCP registry as dev.ytriple.storetechscan/storetechscan. Bulk ecommerce tech stack, Shopify prices, AI ICP fit, contacts. 25/day free; agents buy credits. This page covers its hosted endpoint (https://storetechscan.ytriple.dev/mcp).

### Is the StoreTechScan — Ecommerce Tech Stack & ICP MCP server safe to use?

StoreTechScan — Ecommerce Tech Stack & ICP scores 67 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 StoreTechScan — Ecommerce Tech Stack & ICP MCP server expose?

StoreTechScan — Ecommerce Tech Stack & ICP exposes 7 tools: inspect_domains, inspect_product_url, get_inspection_results, check_credits, buy_credits, and 2 more. Their descriptions and schemas cost roughly 1,129 tokens of context every time the server is loaded.

### Does the StoreTechScan — Ecommerce Tech Stack & ICP MCP server require authentication?

No. We connected to StoreTechScan — Ecommerce Tech Stack & ICP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the StoreTechScan — Ecommerce Tech Stack & ICP MCP server still maintained?

StoreTechScan — Ecommerce Tech Stack & ICP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the StoreTechScan — Ecommerce Tech Stack & ICP MCP server?

VerifyMCP ran 12 checks on StoreTechScan — Ecommerce Tech Stack & ICP, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about StoreTechScan — Ecommerce Tech Stack & ICP: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://storetechscan.ytriple.dev/mcp
- Website: https://storetechscan.ytriple.dev/integrations/mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/dev-ytriple-storetechscan-storetechscan/storetechscan.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-ytriple-storetechscan-storetechscan/storetechscan/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-ytriple-storetechscan-storetechscan/storetechscan.json
- HTML version of this page: https://verifymcp.io/servers/dev-ytriple-storetechscan-storetechscan/storetechscan
