Remote MCP · Endpoint

Chaos — OKX Perpetual Signals MCP server

No. Chaos — OKX Perpetual Signals answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.okx.tw/mcp

The last check completed an MCP handshake.

Registry name
tw.okx/chaos
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
157 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Trend and order-flow signals for OKX USDT perpetual swaps, over MCP. Pay per call.
Listing
From the official MCP registry (active).
Recent checks of Chaos — OKX Perpetual Signals
CheckedResultHandshake
1 hour agoHandshake completed157 ms
13 hours agoHandshake completed157 ms
2 days agoHandshake completed508 ms
4 days agoHandshake completed440 ms
6 days agoHandshake completed420 ms
9 days agoHandshake completed456 ms
11 days agoHandshake completed604 ms
13 days agoHandshake completed427 ms
15 days agoHandshake completed416 ms
17 days agoHandshake completed421 ms
19 days agoHandshake completed477 ms
21 days agoHandshake completed411 ms
23 days agoHandshake completed415 ms
24 days agoHandshake completed461 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 Chaos — OKX Perpetual Signals and makes no claim about it beyond what these checks measured.