streamable-httpMITupdated 3mo ago
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.
What can you do with Boolsai Directory?
Boolsai โ MCP server suite
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
initializeresponse includes a detailedinstructionsblock โ 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
Install
Add Boolsai Directory to your client. Pick the one you use.
claude mcp add --transport http boolsai-directory https://directory.boolsai.ai/mcpcodex mcp add boolsai-directory --url https://directory.boolsai.ai/mcp{
"mcpServers": {
"boolsai-directory": {
"url": "https://directory.boolsai.ai/mcp"
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
{
"servers": {
"boolsai-directory": {
"type": "http",
"url": "https://directory.boolsai.ai/mcp"
}
}
}Add to `.vscode/mcp.json` in your workspace.
{
"mcpServers": {
"boolsai-directory": {
"url": "https://directory.boolsai.ai/mcp"
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"boolsai-directory": {
"serverUrl": "https://directory.boolsai.ai/mcp"
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
Score
39 / 100
Incomplete
- Documentation25/25
- Maintenance13/25
- Trust16/20
- Capability0/15
- Install experience12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 104 days ago
- Has a release history
- Repository is not archived
- Licensed MIT
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 0 tool(s) documented
- Provides prompt templates
- Provides resources
- 6 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint โ no local install
Version history
| Versions | Published |
|---|---|
| 1.0.0Latest | May 19, 2026 |