Remote MCP · Endpoint

Trade Chart MCP server

No. Trade Chart answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://chart.openkrill.app/mcp

The last check completed an MCP handshake.

Registry name
app.openkrill/trade-chart
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
158 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
A candlestick chart for a public ticker, with volume, the indicators you name and a plain read.
Listing
From the official MCP registry (active).
Recent checks of Trade Chart
CheckedResultHandshake
1 hour agoHandshake completed158 ms
1 day agoHandshake completed164 ms
4 days agoHandshake completed4.21 s
6 days agoHandshake completed149 ms
9 days agoHandshake completed181 ms
11 days agoHandshake completed285 ms
13 days agoHandshake completed168 ms
15 days agoHandshake completed185 ms
17 days agoHandshake completed310 ms
19 days agoHandshake completed62 ms
21 days agoHandshake completed31 ms
22 days agoHandshake completed89 ms
24 days agoHandshake completed285 ms
25 days agoHandshake completed38 ms
27 days agoHandshake completed43 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 Trade Chart and makes no claim about it beyond what these checks measured.