Boolsai Directory MCP Server

by boolsai Your server? Claim it

not responding

Boolsai Directory is listed as active in the registry but did not answer our last check. It exposes 19 tools. Last commit 19 May 2026.

Indexed ecommerce site directory — vendor lookups, brands by city/market/founder. 10 tools.

Uptime history 91 days of history · worst day 0%

91 days agonow

0.0%

Uptime 24h

0 of 91 checks

Tools

read from the server

47 ms

Response time

average over 24h

Stars

last commit 19 May 2026

Boolsai Directory does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add directory --transport http https://directory.boolsai.ai/mcp

Settings → Connectors → Add custom connector, then paste this address

https://directory.boolsai.ai/mcp

~/.codex/config.toml

[mcp_servers.directory]
url = "https://directory.boolsai.ai/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "directory": {
      "url": "https://directory.boolsai.ai/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "directory": {
      "type": "http",
      "url": "https://directory.boolsai.ai/mcp"
    }
  }
}

Available tools 19

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

brands

brands_by_founder

List brands attributed to a founder (from Schema.org Organization markup). Useful for tracking serial DTC founders.

brands_in_city

List indexed brands that publish a physical address in a given city. Sourced from Schema.org Organization JSON-LD.

brands_in_market

List indexed brands explicitly serving a country market (via hreflang). Country is a 2-letter ISO code, lowercase.

bulk

bulk_export

Paginated bulk export of indexed sites matching a filter. Returns up to 1000 rows per page in CSV or JSONL format with a cursor for continued pages. Use this when an agency needs an outbound prospect list (e.g. all sites using Klaviyo in the US) for CRM import. The full row count is also returned so you can size the export.

bulk_export_url

Returns a streaming-export URL for the same filter as bulk_export. Useful when the agency wants to pull 50K rows in one shot via curl/HTTP pipe instead of paginating the MCP. The URL is public, no auth, returns NDJSON or CSV with HTTP chunked-transfer streaming. Use bulk_export when N<1000; use this for bigger exports.

compare

compare_scans

Compare two historical scans of the same URL to surface stack changes. Returns added/removed/changed vendors, account IDs, and inline-script signals between scan A and scan B. Use this for competitor watch — 'what did patagonia.com just deploy?'. If t1/t2 are omitted, compares oldest vs newest available scan.

compare_sites

Side-by-side stack comparison of 2-5 domains. Returns each site's vendors, account IDs, brand info, markets — and which signals are shared / unique per site. Good for 'compare X.com vs Y.com' or competitive teardowns.

similar

find_similar_by_stack

Find sites with the most-similar vendor stack to a given domain using Jaccard similarity over the full vendor set (not just archetype labels). Returns the top N matches with similarity scores. Use this when stack_archetype labels are too coarse and you want 'show me 20 brands running an almost-identical stack to liquiddeath.com'. More accurate than similar_sites for niche stacks.

similar_sites

Find brands with similar stack archetypes to the given domain. Returns 'sites running similar tech' — useful for benchmarking, prospecting, competitor lookups.

directory

directory_query

Unified query against the Boolsai Directory. One tool to rule the other lookups. Pass any combination of: signal_type+signal_value, domain, market_country, archetype, founder, city. Returns matching sites + their key signals. Prefer this over the granular tools when you have multiple filter conditions to AND together.

domain

domain_intel

Free DNS/WHOIS enrichment for a single domain. Returns: email host (Google Workspace / Microsoft 365 / etc. — derived from MX records), DNS provider (Cloudflare / Route 53 / GoDaddy / etc.), CDN provider, registrar, domain age (registered/expires). High-signal outbound data — 'they use Google Workspace + Cloudflare DNS + registered with GoDaddy' tells you a lot about org size + sophistication. Results cached 24h. Free — uses Cloudflare DoH + public RDAP.

lookup

lookup_id

Cross-reference any tenant-unique account ID across the index. Useful for 'who else shares this GTM container / Klaviyo company / Sentry org / Meta pixel ID?'. Signal types: gtm_container, ga4_measurement, ga_ua, klaviyo_company_id, meta_pixel_id, shopify_shopid, myshopify_slug, hotjar_id, intercom_app_id, hubspot_portal, klaviyo_subscriber, tiktok_pixel, stripe_pk_live, sentry_dsn_org, tealium_tenant, optimizely_project, mparticle_workspace, segment_writekey, abtasty_account, fullstory_org, pendo_account, intellimize_acct, webflow_site_id, dynamic_yield, wunderkind_site, elevar_id.

operator

operator_cluster

Find every domain sharing a tenant-unique ID — the most powerful single signal in Boolsai. Given a Stripe pk_live key, Sentry DSN org, Klaviyo company_id, mParticle workspace, GTM container, GA4 measurement, Shopify shop_id, or other tenant ID, returns every domain we've seen using the SAME ID. This surfaces multi-brand operators, holding-company portfolios, sister brands sharing infrastructure, agency-managed clusters. No competitor (BuiltWith, Wappalyzer, etc.) can do this — they only see external hostnames, not the tenant-unique IDs leaked client-side. Use this when you want to discover the actual operator behind a brand, or expand a single brand into its full portfolio.

prospect

prospect_brief

ONE-CALL PROSPECT BRIEF for agency outbound — runs four sub-queries against the live indexed data: (1) full dossier of the prospect's stack, (2) sister brands sharing tenant IDs (operator cluster), (3) 3-5 similar-stack competitors, (4) structured 'pitch angles' calling out concrete gaps an agency could pitch on (missing consent, no SST, outdated vendors, broken Schema.org, multiple GTM installs). Saves a strategist 20 min of manual cross-referencing per prospect. Use this whenever the user asks 'tell me about prospect.com'.

site

site_dossier

Full intel dossier for a single domain: detected vendors grouped by category, account IDs (GTM, GA4, Klaviyo company_id, Shopify shop_id, Meta pixel, Sentry org, Tealium tenant, Stripe pk_live, etc.), brand identity (name, founder, city, employees, social handles), international markets, external host list, and likely operator-cluster siblings. Use for any 'what's running on X.com?' query.

sites

sites_using_vendor

List indexed sites detected using a specific vendor (e.g. 'klaviyo', 'yotpo', 'elevar', 'gorgias', 'rebuy'). Vendor slug is lowercase, underscore-separated. Returns domain list with brand names where known.

stack

stack_archetype

List brands matching a stack archetype. Valid slugs: headless-shopify, classic-shopify-dtc, server-side-tagged, personalisation-heavy, pixel-stacked, multi-region, woocommerce-stores, magento-stores, bnpl-enabled, headless-cms.

subdomain

subdomain_map

Every subdomain of a given root domain we've ever scanned. Reveals storefront topology — where the checkout actually lives, regional storefronts, B2B portals, internal admin domains, asset CDNs. Output groups subdomains by their primary vendor where known. Use this to (a) find the right path to scan for an audit (sometimes the checkout is on us.checkout.brand.com not brand.com), (b) spot enterprise topology (multi-region Plus stores), (c) discover sister surfaces (community, ambassador, careers, etc).

summary

summary

Global stats for the Boolsai directory: how many sites are indexed, signal types covered, top vendors, most-changed companies. Use at the start of a session to ground what's available.

Endpoints

URL	Transport	State	Latency	Checked
https://directory.boolsai.ai/mcp	streamable-http	answering	47 ms	8 min ago

Alternatives to Boolsai Directory

same job, measured the same way

Blue Dot Brdg (BLDT)

by bldt

India market entry, ecommerce and fulfilment for consumer brands (Blue Dot Brdg, BLDT).

3 tools answering

ProjectThunder

by projectthunder

ERP and B2B ecommerce rollout research: ERP fit, migration plans, site scans, ERP partner directory.

11 tools answering

Lantern

by lantern

Lantern is an AI visibility platform for ecommerce brands.

answering

Signal by StackEnhance

by stackenhance

How often 750+ e-commerce brands send marketing emails: counts, send dates, recent subject lines.

4 tools answering

Polaris

by polaris-app

Marketing and ecommerce data for LATAM brands: Meta, Google, TikTok, VTEX, Tiendanube, MercadoLibre

answering

Marketbasketanalysis MCP

by 48x-ai

Co-purchase intelligence and merchant ops tools for AI shopping, ecommerce, and B2B agents

45 installs/wk 19 tools answering

UnClick

by malamutemayhem

AI agent tool marketplace. 60+ tools for social, e-commerce, accounting, and messaging.

local only

InstantClips

by instantclips

Create branded vertical video ads from ecommerce product URLs or product photos.

554 installs/wk 15 tools answering

Boolsai Directory — questions

Answers built from our own checks of this server.

What can Boolsai Directory do?

It exposes 19 tools, read directly from the server on our last check. Among them: brands_by_founder, brands_in_city, brands_in_market, bulk_export, bulk_export_url, compare_scans and 13 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Boolsai Directory mostly used for?

Its tools cluster around brands, bulk and compare. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Boolsai Directory working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 47 ms. The bar chart above shows every period we have measured.

The registry lists Boolsai Directory as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Boolsai Directory?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Boolsai Directory need an API key?

No. Boolsai Directory completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 19 of them are readable on this page. This is what we observed, not what the docs claim.

Is Boolsai Directory open source?

The code is open source: it is published under the MIT licence, 1 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at directory.boolsai.ai, which runs on its operator's own terms.