price_contract — flashalpha MCP Prompt
price_contract
is one of 41 prompts on the
flashalpha
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke price_contract from your client
- Claude Code flashalpha Prompt/price_contract run in your project directory
- Claude Desktop flashalpha Prompt/price_contract ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor flashalpha Prompt/price_contract ~/.cursor/mcp.json
- VS Code flashalpha Prompt/price_contract .vscode/mcp.json
- Zed flashalpha Prompt/price_contract ~/.config/zed/settings.json
- Windsurf flashalpha Prompt/price_contract ~/.codeium/windsurf/mcp_config.json
- Cline flashalpha Prompt/price_contract ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI flashalpha Prompt/price_contract ~/.gemini/settings.json
- Grok flashalpha Prompt/price_contract .mcp.json (in your project root)
- ChatGPT flashalpha Prompt/price_contract Settings → Connectors → Advanced → Developer mode
- Claude.ai flashalpha Prompt/price_contract Settings → Connectors → Add custom connector
- LangChain flashalpha Prompt/price_contract pip install langchain-mcp-adapters
Other prompts on this server
- earnings_play
- surface_read
- whats_changed
- dealer_positioning_deep
- pin_risk_check
- screen_watchlist
- flow_direction
- income_overlay
- premium_selling_check
- vrp_regime_check
- daily_brief
- dealer_regime_play
- size_the_trade
- directional_setup
- tail_hedge_check
- zero_dte_live
- skew_read
- dispersion_check
- market_regime
- earnings_screen
- end_of_day_recap
- ask_flashalpha
- iv_crush_estimate
- analyze_exposure
- whats_the_setup
- term_structure_read
- gamma_flip_watch
- basket_exposure
- vol_check
- expected_move
- unusual_flow
- zero_dte_brief
- compare_tickers
- historical_comparison
- explain_metric
- credit_spread_picker
- smart_money_scan
- analyze_structure
- intraday_hedging_map
- key_levels
flashalpha also offers 9 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.