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

Boolsai Scan

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

mcp:ai.

About

mcp:ai.boolsai/scan skill documents Each server is independently published to the Anthropic MCP Registry under the `ai.boolsai/` namespace (DNS-verified via `boolsai.ai`). {.

  • Workflow guidance for mcp:ai.boolsai/scan.
  • Platform-specific setup patterns for mcp:ai.boolsai/scan.
  • Evidence-backed steps from upstream SKILL.md.
  • When-to-use criteria for mcp:ai.boolsai/scan versus alternatives.

Boolsai Scan by the numbers

  • Exposes 2 verified tools (MCP introspection)
  • Data as of Jul 9, 2026 (Skillselion catalog sync)
terminal
claude mcp add --transport http scan https://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
Tools2
Last updatedMay 19, 2026
RepositoryBoolsai-ai/mcp

How do I use mcp:ai.boolsai/scan correctly?

Apply mcp:ai.boolsai/scan workflows from SKILL.md guidance.

Who is it for?

Teams implementing mcp:ai.boolsai/scan workflows from the catalog.

Skip if: Skip when requirements clearly match a different specialized stack.

What you get

Working mcp:ai.boolsai/scan setup with validated configuration and next steps.

  • Live stack report: hosts, scripts, routes, vendors, and account IDs for a URL
  • JSON-LD organization block extraction for entity verification
  • Path-scoped scan output via boolsai_scan_paths when you need narrower coverage

By the numbers

  • 2 MCP tools: boolsai_scan and boolsai_scan_paths
  • Connect URL https://boolsai.ai/mcp
  • One of 4 servers in the Boolsai MCP suite (MIT registry manifests)
At a glance

Boolsai Scan capabilities & compatibility

Capabilities
mcp:ai.boolsai/scan quick start · mcp:ai.boolsai/scan when to use guidance · mcp:ai.boolsai/scan integration patterns
Use cases
orchestration
From the docs

What Boolsai Scan says it does

[![MCP](https://img.shields.io/badge/MCP-streamable--http-blue)](https://modelcontextprotocol.io)
SKILL.md
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
SKILL.md

Tools 2

Public tool metadata - what this server can do for an agent.

boolsai_scan1 param

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.

  • urlstringrequiredURL or bare domain, e.g. "gymshark.com" or "https://allbirds.com/products/legacy-tee".
boolsai_scan_paths2 params

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.

  • urlstringrequiredBase URL or bare domain (e.g. "gymshark.com").
  • pathsarrayPath strings to scan, relative to the base (e.g. ["/", "/products/legacy-tee", "/cart"]). Max 5. If omitted, scans just "/".
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

Live per-URL stack scanner MCP, not a workflow skill or hosted codebase analyzer.

FAQ

What does mcp:ai.boolsai/scan do?

mcp:ai.

When should I use mcp:ai.boolsai/scan?

User asks about mcp:ai.boolsai/scan, or related workflow.

Is this skill safe to install?

Review the Security Audits panel on this page before installing in production.

Developer Toolsintegrations

This week in AI coding

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

unsubscribe anytime.