Remote MCP · Endpoint

OptionWhales MCP server

No. OptionWhales answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.optionwhales.io/mcp/connect

The last check completed an MCP handshake.

Registry name
io.optionwhales/options-flow
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
139 ms
Tools exposed
34 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
US options flow & stock data: unusual activity, gamma levels, IV, earnings. OAuth sign-in or keys.
Listing
From the official MCP registry (active).
Recent checks of OptionWhales
CheckedResultHandshake
1 hour agoHandshake completed139 ms
2 days agoHandshake completed120 ms
5 days agoHandshake completed118 ms
7 days agoHandshake completed116 ms
9 days agoHandshake completed124 ms
11 days agoHandshake completed116 ms
13 days agoHandshake completed120 ms
15 days agoHandshake completed110 ms
18 days agoHandshake completed130 ms
19 days agoHandshake completed153 ms
21 days agoHandshake completed132 ms
21 days agoHandshake completed146 ms
23 days agoHandshake completed127 ms
25 days agoHandshake completed182 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with OptionWhales and makes no claim about it beyond what these checks measured.