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.

Brandloupe Index

REMOTE · API.BRANDLOUPE.COM

Weekly data on 600k+ Shopify stores: launches, best sellers, prices, apps and similar stores.

63 Trust /100

Last scanned (1 hour ago)

Scores higher than 46% of remote servers

Reachable. Last reached 18 Oct 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
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 766 tokens (~191/item across 4 items; 4 tools + 0 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 Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 83% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
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.

  • 17 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 16 Oct 26 62

    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 18 Oct 2026 · Probed https://api.brandloupe.com/api/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=brandloupe.com CN=YE2,O=Let's Encrypt,C=US 5 Oct 2026 3 Jan 2027 ECDSA 256 ECDSA-SHA384 65a8537f8192e98b0b782ce8864e2f0d5dc
SANs: *.brandloupe.com, brandloupe.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.brandloupe.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
brandloupe.com. absent 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
Header Value
x-content-type-options nosniff
referrer-policy same-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.brandloupe.com/api/mcp/ Verified 200
http (plaintext) http://api.brandloupe.com/api/mcp/ Inconclusive 405
MCP tools · 4 exposed · ~684 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
find_stores ~440

Up to 10 live Shopify stores matching filters (category, country, apps they run or lack, pixels, theme), sorted by popularity, estimated US visits, recent launches or catalog size.

NameTypeReqDescription
appstring–Comma-separated app keys the store runs (all of them, max 5). Keys by category: Email & SMS marketing: klaviyo, attentive, postscript, omnisend, privy; Pop-ups & conversion: justuno; Product reviews:…
categorystring–Store category key, e.g. fashion, beauty, home, health, food-drink, pets
countrystring–Two-letter country code of the store's business address, e.g. US
no_appstring–Comma-separated app keys the store runs none of (max 10), e.g. all of a category's keys for 'no reviews app'
no_pixelstring–Comma-separated pixel keys the store runs none of
pixelstring–Comma-separated pixel keys the store runs: meta, tiktok, google_ads, google_analytics, pinterest, snapchat, microsoft_ads, reddit, northbeam, rakuten
sortstring––
themestring–Theme name, e.g. Dawn

No output schema declared.

No examples provided.

lookup_store ~62

One Shopify store's profile from the latest crawl: newest products, best sellers, price range, catalog, apps, theme, pixels, estimated US traffic and similar stores (competitors).

NameTypeReqDescription
domainstringyesStore domain, e.g. gymshark.com

No output schema declared.

No examples provided.

technology_usage ~78

How many live Shopify stores run an app, theme or pixel, its share of its category, top countries, apps used with it and the most visited stores running it. Slugs: app key with hyphens (judge-me), theme name + '-theme' (dawn-theme), pixel key (meta).

NameTypeReqDescription
slugstringyes–

No output schema declared.

No examples provided.

weekly_changes ~104

Totals and examples from the latest weekly crawl compared with the previous one: product launches, price drops of 10% or more, new discounts, best-seller climbs and apps stores added. Optionally for one category or country.

NameTypeReqDescription
categorystring–Store category key, e.g. fashion, beauty, home, health, food-drink, pets
countrystring–Two-letter country code of the store's business address, e.g. US

No output schema declared.

No examples provided.

Install

How do I install the Brandloupe Index MCP server?

Brandloupe Index is a hosted endpoint at https://api.brandloupe.com/api/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 · api.brandloupe.com

# add to Claude Code
claude mcp add --transport http com-brandloupe-brandloupe 'https://api.brandloupe.com/api/mcp/'
Common questions

What is the Brandloupe Index MCP server?

Brandloupe Index is an MCP server listed in the public MCP registry as com.brandloupe/brandloupe. Weekly data on 600k+ Shopify stores: launches, best sellers, prices, apps and similar stores. This page covers its hosted endpoint (https://api.brandloupe.com/api/mcp/).

Is the Brandloupe Index MCP server safe to use?

Brandloupe Index scores 63 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 Brandloupe Index MCP server expose?

Brandloupe Index exposes 4 tools: lookup_store, weekly_changes, find_stores, technology_usage. Their descriptions and schemas cost roughly 684 tokens of context every time the server is loaded.

Does the Brandloupe Index MCP server require authentication?

No. We connected to Brandloupe Index without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Brandloupe Index MCP server still maintained?

Brandloupe Index is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.