Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Boolsai Signals

REMOTE · SIGNALS.BOOLSAI.AI · SCANNED SEP 27

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

0 this week 71 Trust /100
Trust breakdown (7 categories)

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 → Why this is hard to score →

Endpoint Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

How do I install the Boolsai Signals MCP server?

Boolsai Signals is a hosted endpoint at https://signals.boolsai.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · signals.boolsai.ai

# add to Claude Code
claude mcp add --transport http ai-boolsai-signals 'https://signals.boolsai.ai/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "ai-boolsai-signals": {
      "url": "https://signals.boolsai.ai/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ai-boolsai-signals": {
      "type": "http",
      "url": "https://signals.boolsai.ai/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.ai-boolsai-signals]
url = "https://signals.boolsai.ai/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-boolsai-signals": {
      "type": "remote",
      "url": "https://signals.boolsai.ai/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-boolsai-signals --url 'https://signals.boolsai.ai/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ai-boolsai-signals:
    url: "https://signals.boolsai.ai/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ai-boolsai-signals": {
      "Transport": "http",
      "Url": "https://signals.boolsai.ai/mcp"
    }
  }
}
# add to Vellum
assistant mcp add ai-boolsai-signals -t streamable-http -u 'https://signals.boolsai.ai/mcp'
// mcp.json
{
  "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.

Changelog

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.

  • 27 Sept 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • DNSSEC: fail → unverified ▼ security
    • HSTS header: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • HTTPS: fail → pass ▲ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • 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 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 27 Sept 2026 · Probed https://signals.boolsai.ai/mcp

TLS unreached
DNSSEC inconclusive

Validation of signals.boolsai.ai. — Inconclusive

Zone DS Keys Algorithms Outcome
signals.boolsai.ai. Error no A/AAAA/CNAME RRset answered for the name
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://signals.boolsai.ai/mcp Unreachable
http (plaintext) http://signals.boolsai.ai/mcp HTTPS enforced
MCP tools · 12 exposed · ~1,483 tokens

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
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?'

NameTypeReqDescription
change_typestring––
containsstring–Filter to events whose key_path or key_name contains this string (e.g. 'segment')
domainstringyese.g. 'adobe.com'
limitinteger––

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.

NameTypeReqDescription
event_idintegeryeschange_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.

NameTypeReqDescription
domainstringyesBare domain, e.g. 'sweetgreen.com'
max_snapshotsinteger–Hard cap on snapshots to fetch (default 50; max 200)
weeksinteger–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.

NameTypeReqDescription
group_bystring–What dimension to slice on
horizon_daysinteger–Forward-return window (default 7)
min_ninteger–Minimum sample size (default 10)
top_kinteger–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?'

NameTypeReqDescription
daysinteger–Lookback in calendar days (max 30)
min_co_occurrenceinteger–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.

NameTypeReqDescription
datestringyesYYYY-MM-DD — closest wayback snapshot on or before this date will be used
urlstringyesOriginal 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.

NameTypeReqDescription
horizon_daysinteger––
signal_aobjectyesFirst filter (same shape as test_filter args)
signal_bobjectyesSecond 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.

NameTypeReqDescription
horizon_daysinteger–Forward-return window (default 7)
min_ninteger–Sample-size floor per group
sincestring–Optional YYYY-MM-DD lower bound on event date
sourcestring–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_diminteger–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.

NameTypeReqDescription
co_occurrence_mininteger–min same-day detector count (4 = 'real redesign')
detectorstring–e.g. 'pricing_detector'
event_typestring–e.g. 'TIER_COUNT_CHANGED' (case-insensitive)
severity_mininteger–minimum severity (1-5)
sincestring–YYYY-MM-DD lower bound
tickerstring–single ticker to filter to
untilstring–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').

NameTypeReqDescription
limitinteger––
tickerstringyese.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.

NameTypeReqDescription
exclude_noiseboolean–Filter out is_meta_noise=1 events
group_bystring–Dimension to slice on
horizon_daysinteger–Forward-return window
min_ninteger–Minimum sample size
sincestring–YYYY-MM-DD lower bound on event date (default: when prices start)
top_kinteger––

No output schema declared.

No examples provided.

Common questions

What is the Boolsai Signals MCP server?

Boolsai Signals is an MCP server listed in the public MCP registry as ai.boolsai/signals. Quant-research MCP, tradeable signals from public-company website stack changes. 7 tools. This page covers its hosted endpoint (https://signals.boolsai.ai/mcp).

Is the Boolsai Signals MCP server safe to use?

Boolsai Signals scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Boolsai Signals MCP server expose?

Boolsai Signals exposes 12 tools: universe_summary, find_signals, test_filter, recent_events, event_dossier, and 7 more. Their descriptions and schemas cost roughly 1,483 tokens of context every time the server is loaded.

Does the Boolsai Signals MCP server require authentication?

Its publisher declares no required credentials for Boolsai Signals. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Boolsai Signals MCP server still maintained?

Boolsai Signals is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.