Chaos — OKX Perpetual Signals
REMOTE · MCP.OKX.TW · SCANNED OCT 8
Trend and order-flow signals for OKX USDT perpetual swaps, over MCP. Pay per call.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 302 tokens (~50/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Chaos — OKX Perpetual Signals MCP server?
Chaos — OKX Perpetual Signals is a hosted endpoint at https://mcp.okx.tw/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.okx.tw
claude mcp add --transport http tw-okx-chaos 'https://mcp.okx.tw/mcp'
{
"mcpServers": {
"tw-okx-chaos": {
"url": "https://mcp.okx.tw/mcp"
}
}
} {
"servers": {
"tw-okx-chaos": {
"type": "http",
"url": "https://mcp.okx.tw/mcp"
}
}
} [mcp_servers.tw-okx-chaos] url = "https://mcp.okx.tw/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tw-okx-chaos": {
"type": "remote",
"url": "https://mcp.okx.tw/mcp",
"enabled": true
}
}
} openclaw mcp add tw-okx-chaos --url 'https://mcp.okx.tw/mcp' --transport streamable-http
mcp_servers:
tw-okx-chaos:
url: "https://mcp.okx.tw/mcp" {
"McpServers": {
"tw-okx-chaos": {
"Transport": "http",
"Url": "https://mcp.okx.tw/mcp"
}
}
} assistant mcp add tw-okx-chaos -t streamable-http -u 'https://mcp.okx.tw/mcp'
{
"mcpServers": {
"tw-okx-chaos": {
"type": "http",
"url": "https://mcp.okx.tw/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 8 Oct 26 60
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 8 Oct 2026 · Probed https://mcp.okx.tw/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=okx.tw | CN=WE1,O=Google Trust Services,C=US | 10 Sept 2026 | 9 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 93af4d481c43c7440e3217919d45ada1 |
| SANs: okx.tw, *.okx.tw | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.okx.tw. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| tw. | present | 46902 | 13 | Verified |
| okx.tw. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.okx.tw/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.okx.tw/mcp | HTTPS enforced | 301 | https://mcp.okx.tw/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
backtest_signal Backtest signal ~57
Replay the position state machine over history for one symbol and return trade count, win rate, cumulative PnL and max drawdown.
| Name | Type | Req | Description |
|---|---|---|---|
| interval | string | yes | – |
| pages | integer | – | – |
| symbol | string | yes | – |
No output schema declared.
No examples provided.
get_indicators Get indicator series ~60
Full indicator series for one symbol — trend line, CVD, MACD histogram, RSI zone and compression flags. For callers building their own model.
| Name | Type | Req | Description |
|---|---|---|---|
| bars | integer | – | – |
| interval | string | yes | – |
| symbol | string | yes | – |
No output schema declared.
No examples provided.
get_kline Get kline ~60
Raw OHLCV candle series for one OKX USDT perpetual swap. The cheapest call; use it when you want to compute your own indicators.
| Name | Type | Req | Description |
|---|---|---|---|
| interval | string | yes | – |
| limit | integer | – | – |
| symbol | string | yes | – |
No output schema declared.
No examples provided.
get_signal Get single signal ~48
Current signal snapshot for one symbol: trend-channel direction, CVD cross, price cross, position state and the most recent action.
| Name | Type | Req | Description |
|---|---|---|---|
| interval | string | yes | – |
| symbol | string | yes | – |
No output schema declared.
No examples provided.
get_signals Get all signals ~47
The full market table — every supported symbol at one interval, one row each. Use this to scan, filter or rank the market in a single call.
| Name | Type | Req | Description |
|---|---|---|---|
| interval | string | yes | – |
No output schema declared.
No examples provided.
list_markets List markets ~30
List the supported symbols, intervals and data source. Free — call this first to discover what is available.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Chaos — OKX Perpetual Signals MCP server?
Chaos — OKX Perpetual Signals is an MCP server listed in the public MCP registry as tw.okx/chaos. Trend and order-flow signals for OKX USDT perpetual swaps, over MCP. Pay per call. This page covers its hosted endpoint (https://mcp.okx.tw/mcp).
Is the Chaos — OKX Perpetual Signals MCP server safe to use?
Chaos — OKX Perpetual Signals scores 60 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Chaos — OKX Perpetual Signals MCP server expose?
Chaos — OKX Perpetual Signals exposes 6 tools: list_markets, get_kline, get_signal, get_signals, get_indicators, backtest_signal. Their descriptions and schemas cost roughly 302 tokens of context every time the server is loaded.
Does the Chaos — OKX Perpetual Signals MCP server require authentication?
No. We connected to Chaos — OKX Perpetual Signals without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Chaos — OKX Perpetual Signals MCP server still maintained?
Chaos — OKX Perpetual Signals is still listed as active in the MCP registry. We last reached this channel on 8 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.