Server data from the Official MCP Registry
Shopify store intelligence: apps, tech stack, CDN, and market data over a 19K-store corpus.
Shopify store intelligence: apps, tech stack, CDN, and market data over a 19K-store corpus.
A well-structured MCP server that wraps the StoreSignal API with proper authentication and reasonable permission scoping. The code demonstrates good security practices: API keys are handled via environment variables and per-request context variables (no hardcoding), network access is appropriate for the use case, and input validation is present on tools. Minor code quality observations around broad exception handling do not materially impact the security posture. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.
6 files analyzed · 8 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: STORESIGNAL_API_KEY
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-anthesiallc-storesignal": {
"env": {
"STORESIGNAL_API_KEY": "your-storesignal-api-key-here"
},
"args": [
"storesignal-mcp"
],
"command": "uvx"
}
}
}From the project's GitHub README.
mcp-name: io.github.anthesiallc/storesignal
A Model Context Protocol server that exposes the StoreSignal API as tools, so any MCP client (Claude Desktop, Cursor, ChatGPT connectors, or an agent framework) can analyze Shopify stores and run market intelligence queries conversationally.
It's a thin wrapper: each tool maps to one StoreSignal REST endpoint. All the data work happens in the API.
| Tool | What it does |
|---|---|
analyze_store | Full structured profile for a Shopify store URL (apps, CDN, security headers, schema.org, classification, revenue estimate) |
compare_stores | Side-by-side comparison of 2-5 stores (shared apps, exclusive apps, tier) |
find_stores_using_app | Paginated list of every analyzed store running a specific app |
list_apps | All 278 apps in the catalog, optionally filtered by category |
app_adoption | Top apps by adoption % across the corpus, optionally filtered by category |
app_vs_app | Head-to-head: install counts, overlap, co-install rate, bidirectional cross-adoption |
industry_overview | Per-vertical stats: store count, median price, top countries, top apps, tier mix |
store_census | Whole-corpus stats (19,647 stores, 20 industries, app/tier/type breakdowns) |
get_usage | Current billing period usage and plan limit |
Free tier is 250 calls/month, no credit card:
curl -X POST https://storesignal.anthesia.io/api/v1/signup \
-H 'Content-Type: application/json' \
-d '{"email":"you@example.com"}'
The key comes back in the api_key field of the response.
The easiest way is with uv (no manual venv needed):
# stdio transport (default — for Claude Desktop, Cursor, most local clients)
STORESIGNAL_API_KEY=ss_your_key uvx storesignal-mcp
# streamable-HTTP transport (for remote / web clients)
STORESIGNAL_API_KEY=ss_your_key uvx storesignal-mcp --http
Or install with pip into its own environment:
pip install storesignal-mcp
STORESIGNAL_API_KEY=ss_your_key storesignal-mcp
Note: install into a dedicated environment. The
mcpSDK requires a newerstarlettethan the StoreSignal API app pins, so the two will conflict if installed together.
Environment variables:
STORESIGNAL_API_KEY (required) — your StoreSignal API key.STORESIGNAL_BASE_URL (optional) — defaults to https://storesignal.anthesia.io.STORESIGNAL_TIMEOUT (optional) — request timeout in seconds, default 60.Add to claude_desktop_config.json (Settings → Developer → Edit Config):
{
"mcpServers": {
"storesignal": {
"command": "uvx",
"args": ["storesignal-mcp"],
"env": { "STORESIGNAL_API_KEY": "ss_your_key" }
}
}
}
Add the same block to ~/.cursor/mcp.json (or the project .cursor/mcp.json).
The server is hosted on Smithery, so MCP clients that support Smithery can connect without installing anything. You provide your StoreSignal API key in the Smithery config and it routes to the server.
Any LangChain or LangGraph agent can use these tools through
langchain-mcp-adapters:
# pip install langchain-mcp-adapters langgraph "langchain[anthropic]"
from langchain_mcp_adapters.client import MultiServerMCPClient
client = MultiServerMCPClient(
{
"storesignal": {
"transport": "stdio",
"command": "uvx",
"args": ["storesignal-mcp"],
"env": {"STORESIGNAL_API_KEY": "ss_your_key"},
}
}
)
tools = await client.get_tools()
# hand `tools` to a LangGraph/LangChain agent, e.g.
# from langgraph.prebuilt import create_react_agent
# agent = create_react_agent("anthropic:claude-opus-4-8", tools)
LlamaIndex works the same way via its MCP tool spec.
"What apps does Allbirds use?" →
analyze_store("https://www.allbirds.com")
"Compare the tech stacks of Brooklinen and Bombas." →
compare_stores(["https://brooklinen.com", "https://bombas.com"])
"Which Shopify stores are running Judge.me?" →
find_stores_using_app("judge-me")
"What are the top email-marketing apps on Shopify?" →
app_adoption(category="Email Marketing")
"Compare Klaviyo to Omnisend." →
app_vs_app("klaviyo", "omnisend")
"Tell me about the Beauty vertical." →
industry_overview("Beauty")
git clone https://github.com/anthesiallc/storesignal-mcp && cd storesignal-mcp
python -m venv .venv
.venv/Scripts/python -m pip install -e ".[http]" # Windows; [http] adds uvicorn for --http
# .venv/bin/pip install -e ".[http]" # macOS/Linux
STORESIGNAL_API_KEY=ss_your_key .venv/Scripts/python -m storesignal_mcp.server
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.