Boolsai Directory
REMOTE · DIRECTORY.BOOLSAI.AI
Indexed ecommerce site directory — vendor lookups, brands by city/market/founder. 10 tools.
Available components
Last scanned (32 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 27 Sep 2026.
Category E-commerce
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 4 Oct 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 3 Oct 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 2 Oct 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 1 Oct 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 30 Sept 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 29 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 4 Oct 2026 · Probed https://directory.boolsai.ai/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of directory.boolsai.ai. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| directory.boolsai.ai. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://directory.boolsai.ai/mcp | Unreachable | ||
| http (plaintext) | http://directory.boolsai.ai/mcp | HTTPS enforced |
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 →
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.
How do I install the Boolsai Directory MCP server?
Boolsai Directory is a hosted endpoint at https://directory.boolsai.ai/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 · directory.boolsai.ai
claude mcp add --transport http ai-boolsai-directory 'https://directory.boolsai.ai/mcp'
What is the Boolsai Directory MCP server?
Boolsai Directory is an MCP server listed in the public MCP registry as ai.boolsai/directory. Indexed ecommerce site directory, vendor lookups, brands by city/market/founder. 10 tools. This page covers its hosted endpoint (https://directory.boolsai.ai/mcp).
Is the Boolsai Directory MCP server safe to use?
Boolsai Directory scores 0 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 Boolsai Directory MCP server expose?
Boolsai Directory exposes 19 tools: summary, site_dossier, sites_using_vendor, lookup_id, brands_in_city, and 14 more. Their descriptions and schemas cost roughly 2,457 tokens of context every time the server is loaded.
Does the Boolsai Directory MCP server require authentication?
Its publisher declares no required credentials for Boolsai Directory. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Boolsai Directory MCP server still maintained?
Boolsai Directory has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.