Boolsai Signals
REMOTE · SIGNALS.BOOLSAI.AI · SCANNED AUG 3
Quant-research MCP — tradeable signals from public-company website stack changes. 7 tools.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3108 tokens (~259/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 87% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · signals.boolsai.ai
claude mcp add --transport http ai-boolsai-signals https://signals.boolsai.ai/mcp
[mcp_servers.ai-boolsai-signals] url = "https://signals.boolsai.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-boolsai-signals": {
"type": "remote",
"url": "https://signals.boolsai.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-boolsai-signals --url https://signals.boolsai.ai/mcp --transport streamable-http
mcp_servers:
ai-boolsai-signals:
url: "https://signals.boolsai.ai/mcp" {
"mcpServers": {
"ai-boolsai-signals": {
"type": "http",
"url": "https://signals.boolsai.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 57
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://signals.boolsai.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=boolsai.ai | CN=WE1,O=Google Trust Services,C=US | 11 Jul 2026 | 9 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 14aca0047bc991e813321002c0e19ac3 |
| SANs: boolsai.ai, signals.boolsai.ai, *.signals.boolsai.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of signals.boolsai.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| boolsai.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://signals.boolsai.ai/mcp | Verified | 200 | |
| http (plaintext) | http://signals.boolsai.ai/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
domain_timeline ~115
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?'
| Name | Type | Req | Description |
|---|---|---|---|
| change_type | string | — | — |
| contains | string | — | Filter to events whose key_path or key_name contains this string (e.g. 'segment') |
| domain | string | yes | e.g. 'adobe.com' |
| limit | integer | — | — |
No output schema declared.
No examples provided.
event_dossier ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | integer | yes | change_event id |
No output schema declared.
No examples provided.
farm_domain ~186
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Bare domain, e.g. 'sweetgreen.com' |
| max_snapshots | integer | — | Hard cap on snapshots to fetch (default 50; max 200) |
| weeks | integer | — | How many weeks of history to farm (default 26 = ~6 months; max 100) |
No output schema declared.
No examples provided.
find_signals ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| group_by | string | — | What dimension to slice on |
| horizon_days | integer | — | Forward-return window (default 7) |
| min_n | integer | — | Minimum sample size (default 10) |
| top_k | integer | — | Top K combos to return (default 15) |
No output schema declared.
No examples provided.
recent_events ~98
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?'
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | — | Lookback in calendar days (max 30) |
| min_co_occurrence | integer | — | Only show events with this many same-day detectors (4 = high-conviction) |
No output schema declared.
No examples provided.
scan_at_date ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | YYYY-MM-DD — closest wayback snapshot on or before this date will be used |
| url | string | yes | Original URL (e.g. 'https://gymshark.com/') |
No output schema declared.
No examples provided.
signal_diff ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| horizon_days | integer | — | — |
| signal_a | object | yes | First filter (same shape as test_filter args) |
| signal_b | object | yes | Second filter |
No output schema declared.
No examples provided.
signal_landscape ~211
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.
| Name | Type | Req | Description |
|---|---|---|---|
| horizon_days | integer | — | Forward-return window (default 7) |
| min_n | integer | — | Sample-size floor per group |
| since | string | — | Optional YYYY-MM-DD lower bound on event date |
| source | string | — | Which event dataset to scan. 'live' = 1.7K recent. 'wayback' = 13K over 2 years. 'both' = run both and return side-by-side. |
| top_k_per_dim | integer | — | Top K results per dimension (default 8) |
No output schema declared.
No examples provided.
test_filter ~184
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.
| Name | Type | Req | Description |
|---|---|---|---|
| co_occurrence_min | integer | — | min same-day detector count (4 = 'real redesign') |
| detector | string | — | e.g. 'pricing_detector' |
| event_type | string | — | e.g. 'TIER_COUNT_CHANGED' (case-insensitive) |
| severity_min | integer | — | minimum severity (1-5) |
| since | string | — | YYYY-MM-DD lower bound |
| ticker | string | — | single ticker to filter to |
| until | string | — | YYYY-MM-DD upper bound |
No output schema declared.
No examples provided.
ticker_history ~62
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').
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | — |
| ticker | string | yes | e.g. 'NFLX' |
No output schema declared.
No examples provided.
universe_summary ~57
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
wayback_backtest ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| exclude_noise | boolean | — | Filter out is_meta_noise=1 events |
| group_by | string | — | Dimension to slice on |
| horizon_days | integer | — | Forward-return window |
| min_n | integer | — | Minimum sample size |
| since | string | — | YYYY-MM-DD lower bound on event date (default: when prices start) |
| top_k | integer | — | — |
No output schema declared.
No examples provided.