Boolsai Scan MCP Server

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

Local serverstdio

What is the Boolsai Scan MCP server?

Boolsai Scan MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Live tech-stack scan of any public site — vendors, account IDs, scripts, JSON-LD. 2 tools.

What you get

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

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

What the assistant can call

Once Boolsai Scan is connected, these are the calls the assistant has available:

  • First — party data.** Every scan runs live on demand. No third-party feeds, no stale catalogue
  • Server — Connect URL

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Choosing this one

Among the file and storage access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Boolsai Scan's toolset — First, Server — is a fair guide to whether it matches your workflow. It is maintained by ai.boolsai; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the boolsai scan mcp server does with a few real requests.

Available tools

ToolWhat it does
Firstparty data.** Every scan runs live on demand. No third-party feeds, no stale catalogue.
ServerConnect URL

How to install the Boolsai Scan MCP server

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

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use Boolsai Scan to First.
  • Use Boolsai Scan to Server.

Frequently asked questions

It connects Boolsai Scan to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (First, Server) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Boolsai Scan directly.