# Boolsai Directory (remote · directory.boolsai.ai)

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

- Trust score: 61/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `directory.boolsai.ai`: 61/100 (this document), [markdown](https://verifymcp.io/servers/ai-boolsai-directory/directory.md), [page](https://verifymcp.io/servers/ai-boolsai-directory/directory)

## Channel facts

- Endpoint: `https://directory.boolsai.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 19 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2992 tokens (~157/item across 19 items; 19 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 98% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-boolsai-directory": {
      "type": "remote",
      "url": "https://directory.boolsai.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-boolsai-directory --url https://directory.boolsai.ai/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-boolsai-directory:
    url: "https://directory.boolsai.ai/mcp"
```

### Other

```json
{
  "mcpServers": {
    "ai-boolsai-directory": {
      "type": "http",
      "url": "https://directory.boolsai.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 59, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 59, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 58)

First indexed and scored.

## MCP tools (19)

### `summary` (~46 tokens)

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.

### `site_dossier` (~129 tokens)

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.

Input parameters:

- `url` (string, required): Domain or URL, e.g. 'gymshark.com' or 'https://gymshark.com/'

### `sites_using_vendor` (~91 tokens)

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.

Input parameters:

- `vendor` (string, required): Vendor slug, e.g. 'klaviyo', 'shopify', 'webflow', 'onetrust'.

### `lookup_id` (~225 tokens)

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.

Input parameters:

- `signal_type` (string, required): e.g. 'gtm_container', 'klaviyo_company_id', 'sentry_dsn_org'
- `signal_value` (string, required): the actual ID/value, e.g. 'GTM-XYZABC', 'H2zzaR'

### `brands_in_city` (~55 tokens)

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

Input parameters:

- `city` (string, required): City name, e.g. 'Los Angeles', 'New York', 'Berlin'

### `brands_in_market` (~61 tokens)

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

Input parameters:

- `country` (string, required): 2-letter country code, e.g. 'us', 'gb', 'de', 'fr'

### `stack_archetype` (~79 tokens)

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.

Input parameters:

- `archetype` (string, required): Archetype slug

### `compare_sites` (~74 tokens)

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.

Input parameters:

- `urls` (array, required): 2-5 domain/URL strings

### `similar_sites` (~52 tokens)

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

Input parameters:

- `url` (string, required): Domain to find similar sites for

### `brands_by_founder` (~44 tokens)

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

Input parameters:

- `founder` (string, required): Founder name (case-insensitive)

### `bulk_export` (~246 tokens)

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.

Input parameters:

- `cursor` (string): Opaque cursor from previous page; pass to get next 1000 rows
- `format` (string): Output format. CSV is best for CRM import.
- `limit` (integer): Max rows per page (default 1000, max 5000)
- `market_country` (string): Optional ISO-2 country code (e.g. 'us', 'au') to intersect with hreflang market data
- `signal_type` (string, required): Required. e.g. 'vendor', 'klaviyo_company_id', 'shopify_shopid', 'market_country', 'org_country'. Use list_signal_types via Boolsai Grep to discover.
- `signal_value` (string): Optional exact value to filter. If omitted returns ANY value of this signal_type.

### `compare_scans` (~126 tokens)

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.

Input parameters:

- `t1` (string): Optional ISO timestamp of first scan (oldest if omitted)
- `t2` (string): Optional ISO timestamp of second scan (newest if omitted)
- `url` (string, required): Domain or full URL to compare

### `domain_intel` (~133 tokens)

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.

Input parameters:

- `domain` (string, required): Domain to enrich (apex or any subdomain)

### `find_similar_by_stack` (~134 tokens)

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.

Input parameters:

- `domain` (string, required): Reference domain
- `limit` (integer): max similar sites (1-100)
- `min_shared` (integer): Minimum shared distinctive vendors required to be considered (default 3)

### `bulk_export_url` (~125 tokens)

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.

Input parameters:

- `format` (string)
- `market_country` (string): Optional ISO-2 country
- `signal_type` (string, required): Required signal_type
- `signal_value` (string): Optional exact value

### `operator_cluster` (~288 tokens)

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.

Input parameters:

- `domain` (string): Alternative: pass a domain and we'll return every cluster this domain belongs to (all tenant IDs and their fellow domains).
- `id` (string): The tenant ID itself (e.g. 'pk_live_abc...', 'GTM-M8TQZPX', 'o307020' for Sentry, '12345678' for Shopify shop_id). signal_type is auto-detected.
- `limit` (integer): max sites per cluster (1-500)
- `signal_type` (string): Optional explicit signal_type if auto-detect could be ambiguous (e.g. 'stripe_pk_live', 'sentry_dsn_org').

### `subdomain_map` (~161 tokens)

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).

Input parameters:

- `limit` (integer): max subdomains returned (1-1000)
- `root` (string, required): Root domain (e.g. 'gymshark.com'). Pass just the apex; we'll find subdomains automatically.

### `prospect_brief` (~192 tokens)

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'.

Input parameters:

- `angle` (string): Optional agency pitch angle to tune the brief: 'cro', 'analytics', 'consent', 'sst' (server-side tagging), 'headless', 'consolidation'. If omitted, returns all angles found.
- `url` (string, required): Domain or URL of the prospect

### `directory_query` (~196 tokens)

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.

Input parameters:

- `archetype` (string): e.g. 'headless-shopify', 'woocommerce-stores'
- `city` (string): case-insensitive city name
- `domain` (string): exact domain match (e.g. 'gymshark.com')
- `founder` (string): case-insensitive substring
- `limit` (integer): max rows (1-500)
- `market_country` (string): ISO-2 (e.g. 'us')
- `signal_type` (string): e.g. 'vendor', 'shopify_shopid'
- `signal_value` (string): exact signal value

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-boolsai-directory/directory#diagnostics

## Score history

- 2026-08-03: 61
- 2026-08-02: 60
- 2026-08-01: 60
- 2026-07-31: 59
- 2026-07-30: 61
- 2026-07-29: 60
- 2026-07-28: 60
- 2026-07-27: 59
- 2026-07-26: 58

## Links

- Remote endpoint: https://directory.boolsai.ai/mcp
- Repository: https://github.com/Boolsai-ai/mcp
- Changelog RSS feed: https://verifymcp.io/servers/ai-boolsai-directory/directory/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-boolsai-directory/directory/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ai-boolsai-directory/directory