Home / MCP registry index / io.github.tdobrowolski1/flashalpha
io.github.tdobrowolski1/flashalpha
io.github.tdobrowolski1/flashalpha in the official MCP registry.
Endpoint https://lab.flashalpha.com/mcp. Source: github.com/FlashAlpha-lab/flashalpha-mcp.
The registry describes it as: Real-time & historical options analytics: GEX, dealer positioning, vol, VRP, 0DTE, CME futures
We read its 78 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
get_flow_dealer_risk get_exposure_sheet get_historical_max_pain get_option_flow get_liquidity get_historical_volatility get_historical_zero_dte get_universe get_historical_coverage get_narrative get_earnings get_strike_expiry_dependency post_structure_greeks solve_iv get_historical_narrative get_flow_live get_spot_vol_correlation get_tickers get_historical_vrp get_symbols post_screener get_vrp_history get_historical_skew_series get_earnings_screener get_historical_dex get_expected_move_history get_historical_stock_summary post_structure_pnl get_zero_dte_flow get_flow_scan get_realized_vol get_levels get_option_chain get_strategy get_historical_surface get_dispersion compare_expiry_impact get_exposure_basket get_svi_params calculate_greeks get_advanced_volatility get_oi_diff get_account get_option_quote calculate_kelly get_historical_stock_quote get_flow_pin_risk get_term_structure get_max_pain get_vrp get_historical_levels get_historical_exposure_summary get_surface get_historical_vex get_flow_levels get_volatility_forecast get_volatility get_flow_signals get_historical_gex get_earnings_calendar and 18 more
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-tdobrowolski1-flashalpha)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.