Boolsai Directory
SAFEgrade B · trust 89/100None
Overview
From the repository's own README, as read at the audited commit.
# 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
Details
- Source
- Boolsai-ai/mcp
- Transports
- streamable-http
- Tools
- Registered at runtime; the list could not be read from source.
- License
- MIT
- Stars
- 1 · pushed 116d ago
Trust audit
Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | NA |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | WARN |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (2)
streamable-http
Gates applied: no_behavioural_pass.
Audited 2026-09-13 · audit v0.4.0 · source sha 0576e7361b1c · full audit: observations/trust-audit/mcp-server/boolsai-ai__directory.json · Report an issue or request a re-scan
Audit history
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-09-13 | 0576e7361b1c | SAFE | B | 89 | source changed, verdict held |
Also audited
Servers with a similar trust profile.
Questions
What is the Boolsai Directory MCP server?
None
Is Boolsai Directory safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does Boolsai Directory need?
No credential environment variables were found in its source, so it appears to need none.
How does Boolsai Directory run?
It speaks streamable-http, so it runs as a service you connect to over the network.
How current is this page?
The grade is for one exact copy of the source (0576e7361b1c), read on 2026-09-13. The repository is watched and re-audited when it changes.
Provenance: OBSERVED · read 2026-09-13 · job trust-audit-2026-09-13