Boolsai Scan
Live tech-stack scan of any public site — vendors, account IDs, scripts, JSON-LD. 2 tools.
Open source Repository Open in the app JSON README (API)
About
Live tech-stack scan of any public site — vendors, account IDs, scripts, JSON-LD. 2 tools.
Details
- Kind
- MCP servers
- Topic
- No topic detected
- Publisher
- ai.boolsai
- Origin
- official
- Category
- ferramentas
- Transport
- http
- Version
- 1.0.0
- Stars
- 1
- Last push
- 2026-05-19T13:30:20Z
- Repository state
- ativo
- License
- MIT
- Added
- 2026-08-29 02:00:51
- Updated
- 2026-08-29 03:00:09
- Origin id
ai.boolsai/scan
README
# Boolsai — MCP server suite
[](https://modelcontextprotocol.io)
[](LICENSE)
[](https://boolsai.ai)
**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](./boolsai-scan/server.json)** | `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](./boolsai-directory/server.json)** | `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](./boolsai-grep/server.json)** | `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](./boolsai-signals/server.json)** | `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" }
}
}
```
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 .
```
---
## 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](./PUBLISHING.md)** for the one-time DNS verification + per-server publish commands.
---
## License
MIT — see [LICENSE](LICENSE).
Built by [Boolsai](https://boolsai.ai) · Contact: [founder@boolsai.ai](mailto:founder@boolsai.ai)