get_upcoming_reverse_splits

ai.signal8/mcp · Verify this server

Get reverse stock splits SCHEDULED to take effect within a day-offset window of the current US market day, for companies under a market-cap ceiling. Offsets are days from today on the US market calendar: fromOffset=1, toOffset=1 is tomorrow; fromOffset=1, toOffset=7 is the week ahead. Each row carries the ticker, company name, the exact vendor integers (splitFrom/splitTo), a pre-rendered ratio ("1-for-20"), the effective date, market cap, float in SHARES, and price. WHAT THIS IS: rows are splits scheduled AS OF NOW — not a guarantee that every split effective in the window is already known. The underlying stock_splits table has NO created_at column, so there is no way to measure when a row first appeared, and a split announced later will simply be missing. Describe results as "scheduled as of now", NEVER as "all of" or "every" reverse split. A scheduled split can also be postponed or cancelled after it is announced. 🔴 capUnknownCount IS A WITHHOLDING COUNT, NOT A ZERO. It counts rows that passed every other filter and were DELIBERATELY EXCLUDED because Signal8 has no measured market cap for them — typically real OTC microcaps. It does NOT mean those companies have no dilution, no split, or no cap; it means the cap was not measured, so they cannot be asserted to sit under the stated ceiling. If you publish a "under $Xm" framing and capUnknownCount is above zero, say that N further companies were withheld for unmeasured market cap — do not present the list as complete and do not describe the withheld rows at all. Funds, ETFs and sub-1.5x fractional ratio adjustments are already removed server-side; do not re-filter or re-derive the ratio. AN EMPTY splits ARRAY IS A NORMAL, COMMON RESULT — most single weekdays have no sub-cap reverse split scheduled at all. It is NOT an error, NOT a failure, and NOT evidence that reverse-split activity has stopped. Publish nothing rather than publishing an empty-list framing.