Boolsai Signals
ai.boolsaiPublished by boolsai.aiOfficial publisherv1.0.0Updated Oct 24, 2026
Quant-research MCP — tradeable signals from public-company website stack changes. 7 tools.
The publisher's own server: Boolsai Directory
Overview
Lets an assistant query quant-research signals derived from public-company website technology stack changes, benchmarked against SPY.
- What you can do
- Boolsai Signals is a remote MCP server for quant research on tradeable signals found in website stack changes across 316 public companies, covering 1,761 events. Its seven tools include universe_summary, find_signals, test_filter, recent_events, event_dossier, scan_at_date and ticker_history. It draws on a historical scan corpus with Wayback Machine integration, and its methodology is described in the initialize response.
- When to use it
- Use it when an assistant needs to explore whether changes in a public company's website technology stack line up with tradeable signals, review recent events, or inspect a specific company's history. It suits research and screening rather than live trading.
- Requirements
- A remote streamable HTTP endpoint at signals.boolsai.ai; no package install. The provider states no authentication, API key, environment variables or headers are required. Network access to the endpoint is needed.
Installation
In SourceWeft
- Open Boolsai Signals in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/ai.boolsai%2Fsignals/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"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
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
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
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
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: [email protected]
Source: README.md at commit 0f4359c
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Boolsai integrations
Boolsai Directory
ai.boolsaiOfficial publisher
Lets an assistant query a pre-indexed directory of ecommerce sites by vendor, account ID, city, market, founder, or stack archetype.
Boolsai Scan
ai.boolsaiOfficial publisher
A remote MCP server that scans any public website live and returns its tech stack: vendors, account IDs, scripts, routes and JSON-LD.
Boolsai Grep
ai.boolsaiOfficial publisher
Boolsai Grep is a remote, no-auth MCP server that runs parallel regex searches across Boolsai's archive of ecommerce site scans to surface vendor and tracking…