Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
Boolsai-ai avatar

Boolsai Directory

  • 1 repo stars
  • Updated May 19, 2026
  • Boolsai-ai/mcp

Boolsai Directory is a MCP server that exposes 10 tools to search an indexed ecommerce directory by vendor, city, market, founder, and site similarity.

About

Boolsai Directory MCP exposes a quant-style ecommerce site index to AI agents through ten Streamable HTTP tools at directory.boolsai.ai/mcp. developers validating a DTC idea, freelancers prospecting merchants, or founders scoping a vertical use it in Idea and Validate to see who runs which platforms, payment vendors, and markets without manual store-by-store research. Tools span summary and site_dossier for one brand, sites_using_vendor for competitive sets, and compare_sites or similar_sites for positioning work. The suite emphasizes public, no-auth access aligned with the broader Boolsai stack-intelligence story. It is directory and stack intelligence—not order processing or cart APIs—so it pairs well with the separate Boolsai Scan MCP when you need a live crawl of a URL the directory has not yet indexed.

  • 10 public MCP tools on directory.boolsai.ai/mcp with no-auth access
  • Pre-indexed directory of tens of thousands of ecommerce sites with stack and vendor metadata
  • Vendor-centric queries: sites_using_vendor, stack_archetype, compare_sites, similar_sites
  • Geographic and market filters: brands_in_city, brands_in_market, brands_by_founder
  • Deep single-site views via summary, site_dossier, and lookup_id for due diligence

Boolsai Directory by the numbers

  • Data as of Jul 7, 2026 (Skillselion catalog sync)
terminal
claude mcp add --transport http directory https://directory.boolsai.ai/mcp

Add your badge

Show developers this MCP server is listed on Skillselion. Paste this into your README.

Listed on Skillselion
repo stars1
TransportHTTP
AuthNone
Last updatedMay 19, 2026
RepositoryBoolsai-ai/mcp

What it does

Query a pre-indexed global ecommerce directory for vendor stacks, market presence, and founder-linked brands while researching niches or prospects.

Who is it for?

Best when you're doing ecommerce niche research, lead lists, or due diligence on public storefronts.

Skip if: Non-commerce products, private storefronts behind login, or developers who only need a one-off live tech scan without directory context.

What you get

Your agent can dossier brands, list sites on a vendor, compare stacks, and find similar merchants from a indexed directory in one MCP session.

  • Site dossiers and summaries from the indexed commerce corpus
  • Vendor- and geography-filtered brand lists plus compare_sites and similar_sites results

By the numbers

  • 10 MCP tools on Boolsai Directory server
  • Pre-indexed corpus described as tens of thousands of ecommerce sites
  • Connect URL: https://directory.boolsai.ai/mcp (public no-auth)
README.md

Boolsai — MCP server suite

MCP License: MIT No-auth

Stack-intelligence MCPs for AI agents. Live, no-auth, public access to every commerce site's tech stack — every vendor, every account ID, every inline script signature, plus a quant-research signal layer on top.

Built for AI agents doing competitive intel, agency prospect research, ecommerce due diligence, and ad-hoc commerce-data discovery.

This repo contains the Anthropic MCP Registry manifests for the four-server Boolsai suite. The actual servers live at *.boolsai.ai.


The four servers

Server Connect URL Tools What it does
Boolsai Scan https://boolsai.ai/mcp boolsai_scan, boolsai_scan_paths Live tech-stack scan of any public site. Returns every external host, inline script signature, route, vendor, account ID, and JSON-LD organisation block in one response.
Boolsai Directory https://directory.boolsai.ai/mcp summary, site_dossier, sites_using_vendor, lookup_id, brands_in_city, brands_in_market, stack_archetype, compare_sites, similar_sites, brands_by_founder Pre-indexed directory of tens of thousands of ecommerce sites by vendor, account ID, country, founder, city, archetype.
Boolsai Grep https://grep.boolsai.ai/mcp grep_pattern, count_pattern, sites_with_signal, list_signal_types Parallel regex search across the R2 corpus of every scan we've ever taken. Use when a signal isn't pre-indexed — discover new vendor patterns, leaked account IDs, niche tracking pixels.
Boolsai Signals https://signals.boolsai.ai/mcp universe_summary, find_signals, test_filter, recent_events, event_dossier, scan_at_date, ticker_history Quant-research MCP. Hunts for tradeable signals in 316 public-company website stack changes (1,761 events), SPY-benchmarked. Wayback Machine integration. Methodology baked into the initialize response.

Each server is independently published to the Anthropic MCP Registry under the ai.boolsai/* namespace (DNS-verified via boolsai.ai).


Why Boolsai

  • No auth, no key, no rate limit gymnastics. Paste a URL into Claude.ai → Settings → Connectors. Done.
  • First-party data. Every scan runs live on demand. No third-party feeds, no stale catalogue.
  • Built for AI consumption. Each server's initialize response includes a detailed instructions block — vendor recognition tips, output schemas, methodology. Agents don't have to guess.
  • Suite, not silo. Cross-discovery: each server's instructions reference the other three so agents can chain queries (scan → look up in directory → grep historical → test as signal).

Install

Claude Desktop / Claude Code / Cursor

{
  "mcpServers": {
    "boolsai-scan":      { "url": "https://boolsai.ai/mcp" },
    "boolsai-directory": { "url": "https://directory.boolsai.ai/mcp" },
    "boolsai-grep":      { "url": "https://grep.boolsai.ai/mcp" },
    "boolsai-signals":   { "url": "https://signals.boolsai.ai/mcp" }
  }
}

Restart the client. All four servers show up with their tools.

ChatGPT / Claude.ai Custom Connectors

Settings → Connectors → Add custom connector → paste any of the four URLs above. Add all four for the full suite.

One-liner test from a terminal

curl -sS https://boolsai.ai/mcp \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | jq .

Example agent prompts

"What's the full tech stack of gymshark.com?" → boolsai_scan({ url: "https://gymshark.com" })

"List ten stores using Klaviyo with their company IDs." → boolsai-directory.sites_using_vendor({ vendor: "klaviyo" })

"Show me sites with window._fs_org (FullStory) in their inline scripts." → boolsai-grep.sites_with_signal({ pattern: "window._fs_org" })

"Find the highest-α tradeable signal in the last 30 days with n ≥ 20." → boolsai-signals.find_signals({ horizon_days: 30, min_n: 20 })


Architecture

                   ┌──────────────────────────┐
                   │  AI agent (Claude / etc) │
                   └────────────┬─────────────┘
                                │ JSON-RPC 2.0 (Streamable HTTP)
            ┌───────────────────┼─────────────────────┐
            ▼                   ▼                     ▼
   boolsai.ai/mcp     directory.boolsai.ai/mcp   grep.boolsai.ai/mcp
   (live scanner)     (indexed corpus query)     (raw R2 search)
            │                   │                     │
            │                   │                     │
            ▼                   ▼                     ▼
     ┌──────────────────────────────────────────────────────┐
     │  R2 corpus (hundreds of thousands of historical scans) │
     └──────────────────────────────────────────────────────┘
                                ▲
                                │ derived
                signals.boolsai.ai/mcp  (quant signals from stack changes)

All four servers run on Cloudflare Workers with R2 for the historical corpus.


Publishing to the MCP Registry

See PUBLISHING.md for the one-time DNS verification + per-server publish commands.


License

MIT — see LICENSE.

Built by Boolsai · Contact: founder@boolsai.ai

Recommended MCP Servers

How it compares

Indexed ecommerce directory MCP with 10 lookup tools—not a payment MCP or a generic web scraper skill.

FAQ

Who is Boolsai Directory MCP for?

AI-assisted researchers and developers who need structured ecommerce competitive data—vendors, markets, founders, and site comparisons—inside their agent.

When should I use Boolsai Directory MCP?

Use it in Idea or Validate when choosing a niche, sizing competitors, or building prospect lists before you implement a store or outreach campaign.

How do I add Boolsai Directory to my agent?

Point your MCP client at https://directory.boolsai.ai/mcp (Streamable HTTP, public no-auth per Boolsai docs) and invoke the ten directory tools from the registry manifest.

Data Analyticsecommercepricing

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.