mcpbeat

Boolsai Scan MCP Server

ai.boolsai/scan
answering

Boolsai Scan is answering right now. Last checked 8 min ago. It exposes 2 tools. Last commit 19 May 2026.

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

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
2
Tools
read from the server
99 ms
Response time
average over 24h
1
Stars
last commit 19 May 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add scan --transport http https://boolsai.ai/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "scan": {
      "url": "https://boolsai.ai/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.scan]
url = "https://boolsai.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "scan": {
      "url": "https://boolsai.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "scan": {
      "url": "https://boolsai.ai/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

boolsai
boolsai_scan
Scan a public website. Returns its full tech stack — every external host the page talks to, every fetch/xhr/beacon endpoint, every inline-script signal, parsed JSON-LD, and the internal DOM/route trie — as structured JSON. Hostnames are returned raw; recognise vendors from them using your own knowledge.
boolsai_scan_paths
Scan multiple paths on the same site in parallel and merge the external-host lists. Returns per-path host lists, a unified merged set, and a homepage_missed list (hosts that appeared ONLY on non-home paths). Use when the homepage understates the stack — common on Shopify Plus and consent-gated sites where pixels lazy-load on PDP / cart / checkout. Recommended for ecom audits: paths = ["/", "/products/<any>", "/cart", "/checkout"]. Max 5 paths per call.

Endpoints

URLTransportStateLatencyChecked
https://boolsai.ai/mcp streamable-http answering 353 ms 8 min ago

Boolsai Scan — questions

Answers built from our own checks of this server.

What can Boolsai Scan do?
It exposes 2 tools, read directly from the server on our last check. Among them: boolsai_scan, boolsai_scan_paths. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Boolsai Scan working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 99 ms. The bar chart above shows every period we have measured.
How do I connect Boolsai Scan?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Boolsai Scan need an API key?
No. Boolsai Scan completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Boolsai Scan?
It answers our handshake in 99 ms on average, which is faster than 84% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Boolsai Scan open source?
Yes — it is published under the MIT licence and 1 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.