Home / MCP registry index / com.onrender.shopify-launch-watch/shopify-launch-watch
Shopify launch watch for e-commerce agents (x402)
com.onrender.shopify-launch-watch/shopify-launch-watch in the official MCP registry.
Endpoint https://shopify-launch-watch.onrender.com/mcp.
The registry describes it as: See what Shopify competitors launched this week, from products.json. $0.01/store via x402.
We could not reach this server's endpoint on 2026-10-27. Nothing was checked.
Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.
Run this server? Show the check in your README
The badge reflects the latest read: 
[](https://lazaretto.dev/mcp-registry/com-onrender-shopify-launch-watch-shopify-launch-watch)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.
Related
E-commerce MCP servers · Crypto and Web3 MCP servers
| Replo io.github.replohq/replo | 84 tools, nothing matched 2026-10-27 |
| Ask AI com.ask-ai-data-connector/ask-ai | 67 tools, nothing matched 2026-10-26 |
| zobrx com.zobrx/zobrx | 58 tools, nothing matched 2026-10-28 |
| Traject Ecommerce io.github.pipeworx-io/traject-ecommerce | 50 tools, nothing matched 2026-10-30 |
| Shopify io.github.pipeworx-io/shopify | 49 tools, nothing matched 2026-10-30 |
| Woocommerce io.github.pipeworx-io/woocommerce | 49 tools, nothing matched 2026-10-30 |