Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

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.

67 Trust /100

Last scanned (17 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

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 Security63
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, 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
Schema Quality & AI Usability78
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 58% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +1
    • Schema quality: 121 → 134 ▼ functional
    • Tool coverage: 47% → 58% ▲ functional
    • Server version: 1.1.1 → 1.2.0 functional
    • New tool “inspect_product_url” functional
    • “inspect_domains” added an optional parameter “include_evidence” cosmetic
    • “inspect_domains” added an optional parameter “profile” cosmetic
  • 20 Nov 26 0
    • Server version: 1.1.0 → 1.1.1 functional
  • 19 Nov 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.

  • 18 Nov 26 0
    • Tool “check_credits” rewrote its description, which is the text the model reads security
    • Server version: 1.0.0 → 1.1.0 functional
  • 17 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 16 Nov 26 64

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://storetechscan.ytriple.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=ytriple.dev CN=WE1,O=Google Trust Services,C=US 15 Nov 2026 13 Feb 2027 ECDSA 256 ECDSA-SHA256 b3b15b048201799013c2b64c3415346b
SANs: ytriple.dev, storetechscan.ytriple.dev, *.storetechscan.ytriple.dev
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 storetechscan.ytriple.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
ytriple.dev. No DS 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://storetechscan.ytriple.dev/mcp Verified 200
http (plaintext) http://storetechscan.ytriple.dev/mcp Inconclusive 404
MCP tools · 7 exposed · ~1,129 tokens

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 →

Tool Tokens
buy_credits ~139

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.

NameTypeReqDescription
emailstring–Optional buyer email for checkout.
package_idstringyes–

No output schema declared.

No examples provided.

check_credits ~61

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

claim_purchase ~117

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.

NameTypeReqDescription
claim_tokenstringyes–
session_idstringyes–

No output schema declared.

No examples provided.

get_ecommerce_benchmark_2026 ~113

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.

NameTypeReqDescription
formatstring–Return structured JSON summary ("summary", default) or include raw CC BY 4.0 CSV ("csv").

No output schema declared.

No examples provided.

get_inspection_results ~112

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.

NameTypeReqDescription
b2b_wholesale_onlyboolean––
job_idstringyesThe job_id (e.g. "job_...") returned by inspect_domains or check_credits.
min_fit_scorenumber––
platformstring––
real_merchant_onlyboolean––

No output schema declared.

No examples provided.

inspect_domains ~407

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.

NameTypeReqDescription
b2b_wholesale_onlyboolean–Optional filter: return only domains with detected B2B, trade, or wholesale signals.
domains–yes–
include_evidenceboolean–Optional: return auditable detection evidence[] entries even on the default ecommerce profile.
min_fit_scorenumber–Optional filter: minimum 1.0–5.0 ICP prospect fit score (e.g. 3.5 or 4.0).
platformstring–Optional filter: match primary platform or detected tech (e.g. "Shopify", "WooCommerce", "Klaviyo").
profilestring–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_onlyboolean–Optional filter: return only verified active merchants/operators (excludes parked/empty stores).

No output schema declared.

No examples provided.

inspect_product_url ~180

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.

NameTypeReqDescription
urlstring–Single public product URL (use either url or urls).
urlsarray–Array of 1 to 10 public product URLs.

No output schema declared.

No examples provided.

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.

remote · storetechscan.ytriple.dev

# add to Claude Code
claude mcp add --transport http dev-ytriple-storetechscan-storetechscan 'https://storetechscan.ytriple.dev/mcp'
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.