Boolsai Scan MCP Server

by boolsai Your server? Claim it

answering

Boolsai Scan is answering right now. Last checked 7 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 91 days of history · worst day 91%

91 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

350 ms

Response time

average over 24h

Stars

last commit 19 May 2026

Boolsai Scan missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add scan --transport http https://boolsai.ai/mcp

Settings → Connectors → Add custom connector, then paste this address

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

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

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

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

URL	Transport	State	Latency	Checked
https://boolsai.ai/mcp	streamable-http	needs auth	380 ms	7 min ago

Alternatives to Boolsai Scan

same job, measured the same way

Huntertech

by huntertech

Vendor incidents, public pricing, and plan-gated account tools. OAuth at /mcp/auth.

4 tools answering

Cite Files

by citefiles

Check whether AI assistants can reach, read and cite a public website. No account for 4 of 5 tools.

5 tools answering

deed.page

by deed

Publish permanent static sites via MCP/REST. 28 tools. No account or claim link.

28 tools answering

Website

by cuvo

Cuvo Health published site content and live discovery-call booking tools for AI agents.

46 installs/wk 9 tools answering

Reeling

by yomariano

Social publishing, scheduling and delivery-status tools for Reeling accounts.

20 tools answering

Sitepeel

by sitepeel

DESIGN.md, clone prompts, HTML, screenshots, assets, fonts, colors and tech stack of any website.

answering

Canopy account

by canopy-io

Every Canopy public API operation as a tool, run as you after a browser sign-in or on an API key.

answering

AI Model Pricing

by dataleadspro

Live pricing data for AI models across vendors: input/output prices per 1k tokens as JSON.

1 tools answering

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 92 of 92 checks got a reply (100.0%), average response time 350 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 in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.

Does Boolsai Scan need an API key?

Yes. Every time we knock, Boolsai Scan answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is Boolsai Scan?

It answers our handshake in 350 ms on average, which is faster than 38% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Boolsai Scan open source?

The code is open source: it is published under the MIT licence, 1 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at boolsai.ai, which runs on its operator's own terms.