compare_expiry_impact — flashalpha MCP Tool
compare_expiry_impact
(compare expiry impact) is one of 78 tools on the
flashalpha
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call compare_expiry_impact from your client
- Claude Code flashalpha compare_expiry_impact run in your project directory
- Claude Desktop flashalpha compare_expiry_impact ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor flashalpha compare_expiry_impact ~/.cursor/mcp.json
- VS Code flashalpha compare_expiry_impact .vscode/mcp.json
- Zed flashalpha compare_expiry_impact ~/.config/zed/settings.json
- Windsurf flashalpha compare_expiry_impact ~/.codeium/windsurf/mcp_config.json
- Cline flashalpha compare_expiry_impact ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI flashalpha compare_expiry_impact ~/.gemini/settings.json
- Grok flashalpha compare_expiry_impact .mcp.json (in your project root)
- ChatGPT flashalpha compare_expiry_impact Settings → Connectors → Advanced → Developer mode
- Claude.ai flashalpha compare_expiry_impact Settings → Connectors → Add custom connector
- LangChain flashalpha compare_expiry_impact pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http flashalpha https://lab.flashalpha.com/mcpOther tools on this server
- 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
- 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
- get_zero_dte
- get_historical_advanced_volatility
- get_skew_term
- get_historical_chex
- get_flow_summary
- get_vix_state
- get_expected_move
- get_historical_option_quote
- get_stock_summary
- get_chex
- get_historical_term_structure
- get_vex
- get_stock_quote
- get_dealer_premium
- get_stock_flow
- get_exposure_summary
- get_gex
- get_dex
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.