$ trust-the.store mcp

Trust the Store in your AI assistant

One MCP server for everything: search verified shops, scan and compare any store, find stores by tech stack, connect your own shop, and manage your watchlist, from Claude, Cursor, VS Code or any MCP client.

Endpoint

https://trust-the.store/api/mcp

Without a token you get every public tool. To act on your account (your shops, connecting a store, your watchlist), create a token and send it as Authorization: Bearer tms_….

Create an API token

Add it to your client

Claude Code

Terminal

claude mcp add --transport http trust-the-store https://trust-the.store/api/mcp \
  --header "Authorization: Bearer tms_your_token"

Claude Desktop

Settings → Developer → Edit config (claude_desktop_config.json), then restart Claude

{
  "mcpServers": {
    "trust-the-store": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://trust-the.store/api/mcp",
        "--header",
        "Authorization: Bearer ${TMS_TOKEN}"
      ],
      "env": {
        "TMS_TOKEN": "tms_your_token"
      }
    }
  }
}

Needs Node.js. mcp-remote bridges Claude Desktop to the HTTP server and adds your token.

Cursor

~/.cursor/mcp.json (or .cursor/mcp.json in a project)

{
  "mcpServers": {
    "trust-the-store": {
      "url": "https://trust-the.store/api/mcp",
      "headers": {
        "Authorization": "Bearer tms_your_token"
      }
    }
  }
}

VS Code (Copilot agent mode)

.vscode/mcp.json

{
  "servers": {
    "trust-the-store": {
      "type": "http",
      "url": "https://trust-the.store/api/mcp",
      "headers": {
        "Authorization": "Bearer tms_your_token"
      }
    }
  }
}

Claude.ai (custom connector)

Settings → Connectors → Add custom connector

https://trust-the.store/api/mcp

Custom connectors can't send a token yet: you get every public tool (search, scan, compare, guides). Use one of the clients above for your account tools.

Any HTTP client

Streamable HTTP, stateless, JSON responses

curl -s https://trust-the.store/api/mcp \
  -H "Authorization: Bearer tms_your_token" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}}'

Try asking

“Help me connect my Shopify store to Trust the Store.”
“What are the 10 biggest Shopify stores using Klaviyo, and what else do they run?”
“Scan allbirds.com and tell me its estimated monthly revenue range.”
“Compare gymshark.com, alphalete.com and represent.com.”
“Watch my three biggest competitors and tell me what changed this week.”
“How did my shop's verified revenue evolve over the last 90 days?”

What it can do

Tools · 18

search_shops

public · read-only

Search shops whose revenue is verified at the source (read-only platform API). Revenue in USD.

get_shop

public · read-only

One verified shop's public profile: 30-day and all-time revenue (USD), orders, AOV, growth, founder, sync status.

get_shop_revenue

public · read-only

Daily verified net revenue (USD) and orders of one shop for the last N days, with totals.

top_stores

public · read-only

Scanned online stores ranked by estimated monthly revenue (or rank, trust score, reviews, products). Estimates from public pages, in each store's currency.

get_store_scan

public · read-only

The latest stored scan of a store: platform, estimated traffic/orders/revenue ranges, apps and pixels, ad networks, socials, trust signals. Never triggers a new scan.

scan_store

public

Scan any public online store now (cached 6 h, rate-limited). Reads public pages only, respects robots.txt.

store_trends

public · read-only

How a scanned store moved across its stored scans: each metric first → last, and apps/pixels added or removed.

compare_stores

public · read-only

Compare 2–4 scanned stores side by side: best value per metric, shared and unique tech stack.

search_by_stack

public · read-only

Scanned stores running every given tool (apps, pixels, platforms), e.g. ["Klaviyo", "Meta Pixel"]. Up to 5 tools. Without tools, lists the most used ones.

list_platforms

public · read-only

Every e-commerce platform Trust the Store can verify, the read-only access each one needs, and the credential fields connect_shop expects.

connection_guide

public · read-only

Step-by-step instructions to create the read-only key for one platform, the fields to send, and fixes for common errors. Use this to walk a merchant through connecting.

connect_shop

needs token

Connect a store to your account with a READ-ONLY key and publish its verified revenue profile. Get the fields from connection_guide. The key is encrypted at rest; never send a key with write access.

whoami

public · read-only

The Trust the Store account behind the API token, or how to get one when anonymous.

my_shops

needs token · read-only

Shops connected to your account: status, last sync, verified 30-day revenue (USD).

sync_shop

needs token

Re-read one of your shops from its platform now (normally hourly).

my_watchlist

needs token · read-only

Scanned stores you watch, with their latest numbers. You get an email when one moves.

watch_store

needs token

Follow a scanned store: it is rescanned daily and you get an email when its revenue estimate, rank, catalogue, trust or stack moves.

unwatch_store

needs token

Remove a store from your watchlist.

Safety

A token acts as you. Keep it out of shared configs and repos; revoke it any time from your account.
connect_shop only accepts read-only keys, the same as the website. Store keys are encrypted at rest (AES-256-GCM) and never returned.
Scanned-store numbers are estimates from public pages; verified numbers come from the platform API. The server tells your assistant which is which.
Limits: 60 calls per minute, 10 store connections per hour, the website's scan limits.