Boolsai Directory
REMOTE · DIRECTORY.BOOLSAI.AI · SCANNED AUG 3
Indexed ecommerce site directory — vendor lookups, brands by city/market/founder. 10 tools.
Available components
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 →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 98% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · directory.boolsai.ai
claude mcp add --transport http ai-boolsai-directory https://directory.boolsai.ai/mcp
[mcp_servers.ai-boolsai-directory] url = "https://directory.boolsai.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-boolsai-directory": {
"type": "remote",
"url": "https://directory.boolsai.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-boolsai-directory --url https://directory.boolsai.ai/mcp --transport streamable-http
mcp_servers:
ai-boolsai-directory:
url: "https://directory.boolsai.ai/mcp" {
"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.
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.
- 3 Aug 26 +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.
- 1 Aug 26 +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.
- 31 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +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.
- 28 Jul 26 +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.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 58
First indexed and scored.
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 3 Aug 2026 · Probed https://directory.boolsai.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=boolsai.ai | CN=WE1,O=Google Trust Services,C=US | 12 Jul 2026 | 10 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 6232702a03e77c6b1347664fe6cc918c |
| SANs: boolsai.ai, directory.boolsai.ai, *.directory.boolsai.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of directory.boolsai.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| boolsai.ai. | 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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://directory.boolsai.ai/mcp | Verified | 200 | |
| http (plaintext) | http://directory.boolsai.ai/mcp | Served over HTTP | 200 |
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.
brands_by_founder ~44
List brands attributed to a founder (from Schema.org Organization markup). Useful for tracking serial DTC founders.
| Name | Type | Req | Description |
|---|---|---|---|
| founder | string | yes | Founder name (case-insensitive) |
No output schema declared.
No examples provided.
brands_in_city ~55
List indexed brands that publish a physical address in a given city. Sourced from Schema.org Organization JSON-LD.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City name, e.g. 'Los Angeles', 'New York', 'Berlin' |
No output schema declared.
No examples provided.
brands_in_market ~61
List indexed brands explicitly serving a country market (via hreflang). Country is a 2-letter ISO code, lowercase.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | 2-letter country code, e.g. 'us', 'gb', 'de', 'fr' |
No output schema declared.
No examples provided.
bulk_export ~246
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
bulk_export_url ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | — | — |
| market_country | string | — | Optional ISO-2 country |
| signal_type | string | yes | Required signal_type |
| signal_value | string | — | Optional exact value |
No output schema declared.
No examples provided.
compare_scans ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| t1 | string | — | Optional ISO timestamp of first scan (oldest if omitted) |
| t2 | string | — | Optional ISO timestamp of second scan (newest if omitted) |
| url | string | yes | Domain or full URL to compare |
No output schema declared.
No examples provided.
compare_sites ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| urls | array | yes | 2-5 domain/URL strings |
No output schema declared.
No examples provided.
directory_query ~196
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
domain_intel ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to enrich (apex or any subdomain) |
No output schema declared.
No examples provided.
find_similar_by_stack ~134
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Reference domain |
| limit | integer | — | max similar sites (1-100) |
| min_shared | integer | — | Minimum shared distinctive vendors required to be considered (default 3) |
No output schema declared.
No examples provided.
lookup_id ~225
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.
| Name | Type | Req | Description |
|---|---|---|---|
| signal_type | string | yes | e.g. 'gtm_container', 'klaviyo_company_id', 'sentry_dsn_org' |
| signal_value | string | yes | the actual ID/value, e.g. 'GTM-XYZABC', 'H2zzaR' |
No output schema declared.
No examples provided.
operator_cluster ~288
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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'). |
No output schema declared.
No examples provided.
prospect_brief ~192
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'.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Domain or URL of the prospect |
No output schema declared.
No examples provided.
similar_sites ~52
Find brands with similar stack archetypes to the given domain. Returns 'sites running similar tech' — useful for benchmarking, prospecting, competitor lookups.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Domain to find similar sites for |
No output schema declared.
No examples provided.
site_dossier ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Domain or URL, e.g. 'gymshark.com' or 'https://gymshark.com/' |
No output schema declared.
No examples provided.
sites_using_vendor ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| vendor | string | yes | Vendor slug, e.g. 'klaviyo', 'shopify', 'webflow', 'onetrust'. |
No output schema declared.
No examples provided.
stack_archetype ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| archetype | string | yes | Archetype slug |
No output schema declared.
No examples provided.
subdomain_map ~161
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).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | max subdomains returned (1-1000) |
| root | string | yes | Root domain (e.g. 'gymshark.com'). Pass just the apex; we'll find subdomains automatically. |
No output schema declared.
No examples provided.
summary ~46
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.