Remote MCP · Endpoint

Optionscanner MCP server

No. Optionscanner answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://optionscanner.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.optionscanner/optionscanner
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
148 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Free options calculators and the Optionscanner Learn library for any AI assistant. No account.
Listing
From the official MCP registry (active).
Recent checks of Optionscanner
CheckedResultHandshake
1 hour agoHandshake completed148 ms
1 day agoHandshake completed48 ms
2 days agoHandshake completed42 ms
3 days agoHandshake completed42 ms
4 days agoHandshake completed34 ms
5 days agoHandshake completed43 ms
6 days agoHandshake completed37 ms
9 days agoHandshake completed38 ms
11 days agoHandshake completed43 ms
14 days agoHandshake completed53 ms
16 days agoHandshake completed43 ms
18 days agoHandshake completed55 ms
20 days agoHandshake completed162 ms
22 days agoHandshake completed38 ms
24 days agoHandshake completed213 ms

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

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 Optionscanner and makes no claim about it beyond what these checks measured.