Boolsai Signals

Name: Boolsai Signals
Author: ai.boolsai

MCP serverMCP

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

Listed on its own since 2026-09-26. Until then it was part of boolsai-directory, where its earlier checks remain.

by ai.boolsairepository ↗v1.0.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"boolsai-signals","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability4/9 checks ok

30 days agotoday

when	check	result	http	latency	detail
5 d ago	mcp initialize	failed	—	—	unsafe: DNS resolution failed
9 d ago	mcp initialize	failed	—	—	unsafe: DNS resolution failed
11 d ago	mcp initialize	failed	—	—	unsafe: DNS resolution failed
12 d ago	mcp initialize	failed	—	—	unsafe: DNS resolution failed
13 d ago	mcp initialize	failed	—	—	unsafe: DNS resolution failed
13 d ago	mcp initialize	ok	200	13 ms	server boolsai-signals 1.0.0 · protocol 2025-06-18 · 12 tools
13 d ago	mcp initialize	ok	200	13 ms	server boolsai-signals 1.0.0 · protocol 2025-06-18 · 12 tools
13 d ago	mcp initialize	ok	200	24 ms	server boolsai-signals 1.0.0 · protocol 2025-06-18 · 12 tools
14 d ago	mcp initialize	ok	200	26 ms	server boolsai-signals 1.0.0 · protocol 2025-06-18 · 12 tools

Tools observed via MCP handshake

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 researc
find_signals — Automated pattern discovery — scans event_type × detector × diff_field × severity combinations and returns those with the strongest forward-return characteristi
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
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. U
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 t
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 Bo
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').
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).
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
signal_landscape — ONE-SHOT cross-signal sweep. Computes α-vs-SPY stats simultaneously across event_type, detector, diff_field, severity, AND co_occurrence dimensions — returns th
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 s
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_ba

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryai.boolsai/signals

first seen 1 mo ago · fetched 28 h agoopen ↗

Field history (6 recent events)

14 d ago · declared · summary → "Quant-research MCP — tradeable signals from public-company website stack changes. 7 tools."
14 d ago · declared · description → "Quant-research MCP — tradeable signals from public-company website stack changes. 7 tools."
14 d ago · declared · publisherName → "ai.boolsai"
14 d ago · declared · repoUrl → "https://github.com/Boolsai-ai/mcp"
14 d ago · declared · version → "1.0.0"
14 d ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from