Boolsai Signals

ai.boolsai由 boolsai.ai 发布官方发布者v1.0.0更新于 Nov 10, 2026

Quant-research MCP — tradeable signals from public-company website stack changes. 7 tools.

发布方自己的服务：Boolsai Directory

已验证Streamable HTTP可网页运行网页搜索与抓取金融数据与分析

服务详情

标识符: ai.boolsai/signals
传输: Streamable HTTP
运行时: Web executable
信任: Verified
发布于: Sep 16, 2026

安全提示

MCP 服务会接收对话中的工具调用请求，并可能执行外部操作。启用前请先了解该服务能做什么，并只授予它所需的权限。

注册中心已验证此服务的命名空间属于 boolsai.ai，且该域名同时运行其端点。这可以确认发布者，但并不代表该服务的工具是安全的。

SourceWeft 的检查只涵盖条目是否完整、端点是否响应；不审查服务器的代码，也不审查其工具的行为。

在 README 中添加徽章

向读者展示该 MCP 服务已收录于 SourceWeft，徽章链接到本页。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/ai.boolsai%2Fsignals.svg)](https://sourceweft.com/mcp/ai.boolsai%2Fsignals?utm_source=readme&utm_medium=badge)

概览

AI 生成的概览

让助手查询基于上市公司网站技术栈变化生成的量化研究信号，并以 SPY 为基准。

可以做什么: Boolsai Signals 是一个远程 MCP 服务器，用于对 316 家上市公司网站技术栈变化中发现的可用信号进行量化研究，覆盖 1,761 个事件。其七个工具包括 universe_summary、find_signals、test_filter、recent_events、event_dossier、scan_at_date 和 ticker_history。它基于历史扫描语料库，并集成 Wayback Machine，方法论写在 initialize 响应中。
适用场景: 当助手需要研究某家上市公司网站技术栈的变化是否与可用信号相关、查看近期事件，或查看某家公司的历史记录时，可以使用它。它适合研究与筛选，而非实时交易。
运行要求: 远程 streamable HTTP 端点 signals.boolsai.ai，无需安装软件包。提供方声明不需要身份验证、API 密钥、环境变量或请求头。需要能访问该端点的网络。

安装前请注意

该服务器自称无需认证且只读，因此不索取凭据。信号属于研究输出，并非投资建议，提供方自述的基准与方法论在此未经验证。用于决策前请确认数据的新鲜度与授权情况。

安装

在 SourceWeft 中

打开控制台中的 Boolsai Signals，将其添加到工作区。
为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/ai.boolsai%2Fsignals/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "boolsai-signals": {
      "type": "http",
      "url": "https://signals.boolsai.ai/mcp"
    }
  }
}

README

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

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" }  }}

{  "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 .

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)

                   ┌──────────────────────────┐                   │  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)