Flashalpha

FlashAlpha MCP Server — Real-Time Options Analytics for AI Assistants

Connect Claude, ChatGPT, Cursor, Windsurf, or any MCP-compatible AI assistant to live options market data. 70+ tools covering gamma exposure (GEX), delta/vanna/charm exposure, max pain, key dealer-positioning levels, IV surfaces (SVI parameters), VRP analytics + history, expected move, volatility skew & term structure, spot-vol correlation, dispersion / index-vs-component vol arbitrage, liquidity scoring, VIX macro state, the tradeable universe, exposure sheet / term-structure / multi-symbol basket / open-interest diff, Black-Scholes greeks, Kelly sizing, real-time options & stock order flow (sweeps, blocks, dealer premium), 0DTE intraday flow (snapshot, time series, hedge flow, heatmap, strike flow), 10 actionable options-strategy signals (flow-anomaly, expiry-positioning, 0DTE, dealer-regime, vol-carry, yield-enhancement, surface-anomaly, skew, term-structure, tail-pricing), a full earnings analytics suite (calendar, expected move, history, IV crush, VRP, dealer positioning, strategies, screener), multi-leg structure P&L + greeks calculators, a multi-factor options screener with field taxonomy, plus minute-resolution historical replay back to April 2018 for backtesting.

---

What is this repo

Documentation, setup snippets, and server.json metadata for the FlashAlpha remote MCP server. The server itself runs at https://lab.flashalpha.com/mcp (and /mcp-oauth for OAuth-authenticated clients) — its source is not open. Use this repo as a reference for how to wire FlashAlpha into your AI client of choice.

---

Server URLs

Two endpoints, identical tool catalog, different authentication:

• Transport: Streamable HTTP
• Protocol version: MCP 2025-06-18
• OAuth discovery: https://lab.flashalpha.com/.well-known/oauth-protected-resource (RFC 9728)
• Authorization server: https://flashalpha.com/oauth

Persona-scoped endpoints

Each base endpoint also has nine persona variants that expose a curated subset of the catalog for a specific trading style. Same auth model — /mcp/ takes the apiKey parameter, /mcp-oauth/ uses OAuth. Point your client at a persona URL instead of the base URL to load just that toolset.

---

Quick Setup (self-hosted clients → /mcp + apiKey)

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{

"mcpServers": { "flashalpha": { "type": "http", "url": "https://lab.flashalpha.com/mcp" } } }

Claude Code CLI

claude mcp add flashalpha --transport http https://lab.flashalpha.com/mcp

claude mcp list

Cursor

Settings → MCP → Add server:

{

"flashalpha": { "transport": "http", "url": "https://lab.flashalpha.com/mcp" } }

VS Code (Copilot / Continue)

.vscode/mcp.json or user settings:

{

"servers": { "flashalpha": { "type": "http", "url": "https://lab.flashalpha.com/mcp" } } }

Windsurf

Cascade settings → MCP Servers:

{

"flashalpha": { "transport": "http", "url": "https://lab.flashalpha.com/mcp" } }

Perplexity (Pro/Max/Enterprise)

Settings → Connectors → + Custom connector → Remote

• URL: https://lab.flashalpha.com/mcp-oauth
• Auth: OAuth (walks the consent flow at flashalpha.com/oauth/login)

---

Authentication

/mcp (apiKey)

Every tool call takes apiKey as a string parameter. Get a free key at flashalpha.com.

apiKey: "fa_your_key_here"

Key passes per-call rather than in a header so it works uniformly across all MCP clients without transport-level configuration.

/mcp-oauth (Bearer)

OAuth 2.1 + PKCE + Dynamic Client Registration (RFC 7591). The client registers itself, walks the authorization-code + PKCE flow, and presents a Bearer JWT on each request. No `apiKey` parameter needed — the server resolves the user's account from the OAuth identity and forwards the API key internally for upstream /v1/* calls. Same per-user tier gating and rate limits apply as the apiKey flow.

Discovery + endpoints:

---

Data provenance: data_as_of

Every tool result carries the API's response envelope: data_as_of, reporting when each upstream feed last delivered to the node that answered, and endpoint_version identifying the deployment that produced it.

This matters more for an MCP client than for a normal SDK caller: a model reading a tool result has no other way to tell a current figure from a stale one, and will otherwise present both with equal confidence.

How to read it

• Check the feeds the tool depends on. A GEX call on an equity is answered from equity_feed, equity_options_feed and oi_feed. futures_feed being null in that result says nothing about the answer.
• Compare against the cadence, not the clock. oi_feed at the previous session's close is correct: settled open interest is published once per session, so on a Monday the newest figure that exists is Friday's. An options feed an hour behind during the regular session is not correct.
• `null` means "not seen on this node", not "broken". A node that has never been asked for a futures symbol has never opened that feed.
• Spot and options are separate on purpose. They arrive over different pipes and can fail independently, so an index chain can be current while the index level behind it is not.
• It evidences feed activity, not per-contract freshness. An illiquid strike may not have quoted for hours while its feed is healthy.
• `data_as_of` is not `as_of`. as_of is response-generation time or the newest contract in the payload, depending on the endpoint. data_as_of describes the feeds behind it.

Historical replay tools carry a second object, archive_as_of, in the same shape: the vintage of the archive rows actually replayed for the timestamp requested. Their every feed in data_as_of is null, because a replay node reads the archive and consumes no live feed.

Full reference: https://flashalpha.com/docs/lab-api-overview#response-envelope and the methodology whitepaper at https://flashalpha.com/methodology#freshness-reporting.

Tool Catalog (70+ tools)

Tool names below are the exact strings sent via `tools/call` — snake_case, not the PascalCase C# method names. Copy verbatim.

Live tools

Market Data (6)

Exposure Analytics (13)

Volatility & Pricing (19)

| get_expected_move | Straddle-implied expected move (1σ) by expir