ZBS Index What actually exists in applied AI, with the source next to it

mcp server

Boolsai Signals

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

Description as published by the maintainer. Source

  • version 1.0.0
  • slowing
  • retrieval

slowing — Most recent push to the repository was 2026-05-19. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.

What this server can do

12 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.

domain_timeline(limit, domain, contains, change_type)
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?' Required: domain.
event_dossier(event_id)
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. Required: event_id.
farm_domain(weeks, domain, max_snapshots)
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. Required: domain.
find_signals(min_n, top_k, group_by, horizon_days)
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.
recent_events(days, min_co_occurrence)
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_at_date(url, 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. Required: url, date.
signal_diff(signal_a, signal_b, horizon_days)
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. Required: signal_a, signal_b.
signal_landscape(min_n, since, source, horizon_days, top_k_per_dim)
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.
test_filter(since, until, ticker, detector, event_type, severity_min, co_occurrence_min)
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_history(limit, ticker)
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'). Required: ticker.
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_backtest(min_n, since, top_k, group_by, horizon_days, exclude_noise)
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.

Last successful function declaration observed on . Source: https://signals.boolsai.ai/mcp. We list what the server declared; we do not call any of these functions.

Endpoint status observed on . Source: https://signals.boolsai.ai/mcp.

Signals

These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.

Signal Value What it measures Window Observed Source
GitHub stars 1 Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. cumulative, all time GitHub
Last commit 2026-05-19 Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. point in time GitHub
Open issues 0 Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. as of fetch GitHub
Latest published version 1.0.0 Latest version string the maintainer published to the registry. as of fetch Model Context Protocol
Registry record last updated 2026-05-19 When the registry record was last updated by its maintainer. point in time Model Context Protocol
License MIT Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. as of fetch GitHub
First listed in the MCP Registry 2026-05-19 Date this server was first published to the official MCP Registry. Not a usage or quality measure. point in time Model Context Protocol
repository status active The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. as of fetch GitHub
mcp tools declared 12 tools Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. as of probe signals.boolsai.ai
mcp endpoint status ok The server listed 12 functions when asked. as of probe signals.boolsai.ai

Where to get it

Also from boolsai-ai

  • Boolsai Directory — last commit 2026-05-19
    Indexed ecommerce site directory — vendor lookups, brands by city/market/founder. 10 tools.
  • Boolsai Grep — last commit 2026-05-19
    Parallel regex across all Boolsai scans — discover new vendor patterns, niche signals. 4 tools.
  • Boolsai Scan — last commit 2026-05-19
    Live tech-stack scan of any public site — vendors, account IDs, scripts, JSON-LD. 2 tools.

This record as data

Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.

GET /api/v1/entries/mcp_server.json

Sources

  1. Boolsai-ai/mcp on GitHub — GitHub, observed , trust tier 3.
  2. Official MCP Registry — Model Context Protocol, observed , trust tier 1.
  3. Tools declared by the MCP server at https://signals.boolsai.ai/mcp — signals.boolsai.ai, observed , trust tier 1.