Boolsai Scan

ai.boolsai由 boolsai.ai 發布官方發布者v1.0.0更新於 Oct 25, 2026

Live tech-stack scan of any public site — vendors, account IDs, scripts, JSON-LD. 2 tools.

發布方自己的服務：Boolsai Directory

已驗證Streamable HTTP可網頁執行網頁搜尋與抓取開發者工具

服務詳細資訊

識別碼: ai.boolsai/scan
傳輸: Streamable HTTP
執行環境: Web executable
信任: Verified
發布於: Sep 16, 2026

安全提示

MCP 服務會接收對話中的工具呼叫請求，並可能執行外部操作。啟用前請先了解該服務能做什麼，並只授予它所需的權限。

註冊中心已驗證此服務的命名空間屬於 boolsai.ai，且該網域同時執行其端點。這可以確認發布者，但並不代表該服務的工具是安全的。

SourceWeft 的檢查只涵蓋條目是否完整、端點是否回應；不審查伺服器的程式碼，也不審查其工具的行為。

在 README 中新增徽章

向讀者展示該 MCP 服務已收錄於 SourceWeft，徽章連結到本頁。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/ai.boolsai%2Fscan.svg)](https://sourceweft.com/mcp/ai.boolsai%2Fscan?utm_source=readme&utm_medium=badge)

概覽

AI 產生的概覽

一個遠端 MCP 伺服器，可即時掃描任意公開網站並回傳其技術堆疊：供應商、帳號 ID、指令碼、路由與 JSON-LD。

可以做什麼: 掃描公開站點，一次回傳所有外部主機、內嵌指令碼特徵、路由、供應商、帳號 ID 與 JSON-LD 組織資訊區塊。掃描站點的指定路徑以檢視更深層頁面。結果來自隨選即時掃描，而非預先建立的目錄。
適用情境: 適用於競品情報、代理商潛在客戶研究、電商盡職調查，或臨時了解某站點使用了哪些工具與追蹤供應商。
執行需求: 遠端 Streamable HTTP 端點；未宣告需要身分驗證、API 金鑰或環境變數。用戶端需支援遠端 MCP 連接器，伺服器需能存取目標站點。

安裝前請注意

掃描會隨選對第三方公開站點發出請求，目標站點會看到該請求，結果會反映所有公開暴露的內容，包括帳號 ID 與內嵌指令碼。不要求提供憑證，但掃描特定站點前應先確認是否可接受。

安裝

在 SourceWeft 中

開啟儀表板中的 Boolsai Scan，將其新增到工作區。
為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/ai.boolsai%2Fscan/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

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

README

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

json

{  "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" }  }}

{  "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

bash

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

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)

                   ┌──────────────────────────┐                   │  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)