Boolsai Signals is listed as active in the registry but did not answer our last check. It exposes 12 tools. Last commit 19 May 2026.
Quant-research MCP — tradeable signals from public-company website stack changes. 7 tools.
Uptime history
91 days of history · worst day 0%
91 days agonow
0.0%
Uptime 24h
0 of 91 checks
12
Tools
read from the server
56 ms
Response time
average over 24h
1
Stars
last commit 19 May 2026
Boolsai Signals does not always answer
Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.
run in your terminal
claude mcp add signals --transport http https://signals.boolsai.ai/mcpSettings → Connectors → Add custom connector, then paste this address
https://signals.boolsai.ai/mcp~/.codex/config.toml
[mcp_servers.signals]
url = "https://signals.boolsai.ai/mcp".cursor/mcp.json
{
"mcpServers": {
"signals": {
"url": "https://signals.boolsai.ai/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"signals": {
"type": "http",
"url": "https://signals.boolsai.ai/mcp"
}
}
}Available tools 12
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
signal
signal_diff
Compare two signal patterns side-by-side. e.g. 'how does PRICING_TIERS_ADDED compare to VENDORS_DETECTED_CHANGED on the live dataset?' Returns α, %pos, sample size, worst/best trades for each, plus delta. Pure D1, fast.
signal_landscape
ONE-SHOT cross-signal sweep. Computes α-vs-SPY stats simultaneously across event_type, detector, diff_field, severity, AND co_occurrence dimensions — returns the full landscape in a single response. Use this FIRST when you want to see where signal lives without having to call find_signals N times. Stateless, pure D1, no rate-limit risk, ~1s response. Cached per arg set for sub-100ms repeated queries.
domain
domain_timeline
Week-by-week wayback diff timeline for one domain. Returns every detected stack change (additions / removals) with week date. Use this to see when a vendor was added/removed historically, e.g. 'when did adobe.com add Segment?'
event
event_dossier
Deep dive on a single event: full diff (added/removed values), surrounding price action (-3D to +14D), predicted vs actual α, links to wayback comparison. Use this to investigate a specific event flagged by find_signals or recent_events.
farm
farm_domain
Bulk-farm a domain's historical wayback snapshots into our index. Use this when you need backtest history on a domain we haven't already farmed (i.e. wayback_backtest / domain_timeline return no data for it). Hits CDX → samples weekly → parallel-scans up to 50 snapshots via intel.boolsai.ai → inserts into wayback_intel_profiles. After farming completes you can call wayback_backtest or domain_timeline on the domain immediately. Cost: ~30-60s wall time, ~50 intel scans.
recent
recent_events
Live signal feed: events fired in the last N days (default 7). Returns each event with the predicted α range based on its event type's historical performance. Use this to surface 'what should I be looking at right now?'
scan
scan_at_date
Scan a URL as it appeared on a historical date via the Wayback Machine. Uses intel.boolsai.ai against the wayback-wrapped URL. Returns the same JSON shape as Boolsai Scan but for a historical snapshot. Use when investigating WHEN a vendor was added/removed.
signals
find_signals
Automated pattern discovery — scans event_type × detector × diff_field × severity combinations and returns those with the strongest forward-return characteristics (α vs SPY, % positive, n). Use this when you don't have a specific hypothesis yet. Returns sorted by α at +7D descending. Filter by min_n to set a sample-size floor.
test
test_filter
Compute α stats for an arbitrary filter expression. Use this to test a specific hypothesis (e.g. 'tier_count_changed on enterprise-SaaS tickers' or 'severity 5 events that happened on Mondays'). Returns n, mean/median raw and α returns at +1/+3/+7d, % positive, and the worst-loss trade.
ticker
ticker_history
All events fired on a single ticker, plus price action timeline. Use this to investigate one company's pattern (e.g. 'show me everything we caught on NFLX').
universe
universe_summary
Orient the agent: total events, tickers, date range, top event types, top detectors, price coverage, SPY benchmark status. Call this FIRST when starting research. Returns counts that let the agent reason about sample sizes before drilling in.
wayback
wayback_backtest
Run an SPY-benchmarked backtest on the WAYBACK historical event dataset (2+ years, 13K events) instead of the recent live event dataset (2 months, 1.7K events). Much bigger samples for statistical confidence. Group by change_type / key_path / domain.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://signals.boolsai.ai/mcp | streamable-http | answering | 56 ms | 8 min ago |
Alternatives to Boolsai Signals
same job, measured the same wayCompany Research
by kiskecske24
Website tech stack (7,600+ technologies) and screenshots for any company site, via Apify.
Sitelas
by sitelas
Build a real website from a chat — then run it: read messages, check traffic, publish changes.
Black Label Bots Website MCP
by blacklabelbots
Search and read public Black Label Bots pages with source URLs.
BlackLabel Tech Website MCP
by blacklabeltec
Search and read public BlackLabel Tech pages with source URLs.
Black Label Real Estate Website MCP
by blbestate
Search and read public Black Label Real Estate pages with source URLs.
Stacktree
by stacktr
Publish HTML to private, unguessable, replace-in-place URLs from any MCP-compatible AI agent.
Ace Website MCP
by ace-bl
Search and read public Ace pages with source URLs.
Stackduke Radar
by stackduke
Read-only answers about tool changes in the public MCP servers on Stackduke's tracker. No sign-in.
Boolsai Signals — questions
Answers built from our own checks of this server.
What can Boolsai Signals do?
It exposes 12 tools, read directly from the server on our last check. Among them: domain_timeline, event_dossier, farm_domain, find_signals, recent_events, scan_at_date and 6 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is Boolsai Signals working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 56 ms. The bar chart above shows every period we have measured.
The registry lists Boolsai Signals as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Boolsai Signals?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Boolsai Signals need an API key?
No. Boolsai Signals completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.
Is Boolsai Signals open source?
The code is open source: it is published under the MIT licence, 1 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at signals.boolsai.ai, which runs on its operator's own terms.