New Shopify Stores Radar

io.github.yzf75011-uiPublished by GitHub account yzf75011-uiv1.0.0Updated Oct 11, 2026

New and pre-launch Shopify stores from public CT logs: RDAP date, niche, country. No PII.

Overview

AI-generated overview

Gives an assistant a live feed of new and pre-launch Shopify stores from public certificate transparency logs, plus a Shopify checker for domain lists.

What you can do
Returns one flat JSON object per store with fields such as store_domain, store_name, status (live or pre-launch), niche, country, region, currency, products, collections, ships_to, product_types, sample_titles, domain_registered from RDAP, first_detected and dated status checks. A feed mode lists stores since a given number of days or from a cursor, and an enrich mode checks which domains run on Shopify and when they were registered. Results can be capped with maxItems, and sample n8n workflows push new stores to webhooks, Google Sheets or Slack with optional lead scoring.
When to use it
Use it for market research, trend analysis and competitive intelligence on newly registered Shopify stores, including ones still behind a password page. It suits prospecting or monitoring pipelines that need new store leads delivered to a CRM, spreadsheet or chat tool. It is not a general web search or scraping tool.
Requirements
Remote streamable HTTP endpoint at served by the official Apify MCP server; no packages, environment variables or headers are declared in the manifest. The recommended remote setup signs in with Apify in the browser; a local stdio option requires an Apify API token. The n8n workflow needs a Header Auth credential named Authorization with a Bearer Apify API token, and optionally a webhook URL, Google Sheets and Slack.
Before you install
Results are billed per store, so use maxItems and the free cursor value "latest" to bound spend; a paid snapshot and CSV membership are also offered. The n8n integration asks for a Header Auth credential named Authorization with a Bearer Apify API token, and the local stdio option needs an Apify API token. The feed carries business-level public data only; any contact enrichment added downstream is the user's own processing and compliance responsibility. The provider disclaims affiliation with…

Installation

In SourceWeft

  1. Open New Shopify Stores Radar in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.yzf75011-ui%2Fprelaunch-radar-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "new-shopify-stores-radar": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=prelaunch-radar/new-shopify-stores-pre-launch-radar"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 26, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.