Remote MCP · Endpoint

OwlChart MCP server

No. OwlChart answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://owlchart.com/mcp

The last check completed an MCP handshake.

Registry name
com.owlchart/owlchart
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
441 ms
Tools exposed
46 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Live market data for AI: open interest on 13 exchanges, liquidity magnets, ETF flows, alerts
Listing
From the official MCP registry (active).
Recent checks of OwlChart
CheckedResultHandshake
1 hour agoHandshake completed441 ms
2 days agoHandshake completed468 ms
4 days agoHandshake completed468 ms
6 days agoHandshake completed593 ms
8 days agoHandshake completed607 ms
10 days agoHandshake completed593 ms
12 days agoHandshake completed415 ms
14 days agoHandshake completed161 ms
16 days agoHandshake completed162 ms
17 days agoHandshake completed637 ms
18 days agoHandshake completed410 ms
21 days agoHandshake completed626 ms
22 days agoHandshake completed171 ms
24 days agoHandshake completed462 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 OwlChart and makes no claim about it beyond what these checks measured.