tech.ensotrade/ensotrade
REMOTE · WWW.ENSOTRADE.TECH · SCANNED AUG 3
Live crypto data: why a coin or the market is moving (funding, OI, positioning, flow).
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 →
Endpoint Security63
- 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 12 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability73
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2433 tokens (~187/item across 13 items; 12 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · www.ensotrade.tech
claude mcp add --transport http tech-ensotrade-ensotrade https://www.ensotrade.tech/mcp/
[mcp_servers.tech-ensotrade-ensotrade] url = "https://www.ensotrade.tech/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tech-ensotrade-ensotrade": {
"type": "remote",
"url": "https://www.ensotrade.tech/mcp/",
"enabled": true
}
}
} openclaw mcp add tech-ensotrade-ensotrade --url https://www.ensotrade.tech/mcp/ --transport streamable-http
mcp_servers:
tech-ensotrade-ensotrade:
url: "https://www.ensotrade.tech/mcp/" {
"mcpServers": {
"tech-ensotrade-ensotrade": {
"type": "http",
"url": "https://www.ensotrade.tech/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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +38
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −36
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 59
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 3 Aug 2026 · Probed https://www.ensotrade.tech/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.ensotrade.tech | CN=YR1,O=Let's Encrypt,C=US | 5 Jul 2026 | 3 Oct 2026 | RSA 2048 | SHA256-RSA | 5c7f74c9de8840c882b565d8a60e6a57a51 |
| SANs: www.ensotrade.tech | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC insecure
Validation of www.ensotrade.tech. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| tech. | present | 2185 | 13 | Verified |
| ensotrade.tech. | 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 |
|---|---|
| strict-transport-security | max-age=63072000 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.ensotrade.tech/mcp/ | Verified | 200 | |
| http (plaintext) | http://www.ensotrade.tech/mcp/ | HTTPS enforced | 308 | https://www.ensotrade.tech/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.
carry_pressure ~102
Toxic Carry Score (cost-of-leverage from funding, positive = bullish) + Open Interest Quality Index (is the price trend agreeing with new positioning, i.e. healthy, or against it, i.e. forced flow / reversal risk). Requires an EnsoTrade Pro API key. `coin` = ticker e.g. 'btc'. See the `market_glossary` resource for how to read these numbers.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | yes | — |
Structured output declared, but exposes no named fields.
No examples provided.
explain_move ~145
Explain WHY a crypto coin is up or down right now, from live order-flow and positioning. Use this for "why is bitcoin down", "why is BTC/ETH/SOL pumping or dumping", or any question about the CAUSE of a crypto move. Returns a ready-to-quote sentence plus structured signals (price, regime, funding, open interest, basis). `coin` = ticker like 'btc', 'eth', 'sol'. Pass an EnsoTrade Pro API key as a Bearer token for real-time data (public calls are 15-minute delayed) — generate one at ensotrade.tech under Account -> Developer Access.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | yes | — |
Structured output declared, but exposes no named fields.
No examples provided.
fetch_series ~416
Raw time series for one field on one symbol, oldest-first, capped at 1000/1500 points. Use this to explore what a field actually looks like before wiring it into test_formula. Requires an EnsoTrade Pro API key. `symbol` e.g. 'SOL' or 'SOLUSDT'. `timeframe="scalp"` (default): WDE order-flow microstructure, second-scale. `field` is one of mid, spread_bp, signal, toxicity, cost_bp, ret_1s_bp, ret_5s_bp, ret_30s_bp, ret_60s_bp (top-level), or ofi1, ofi5, dofi, qi, mp, obi, tf1, tf5, tf30, run, inten, vpin, wall, bid_pr, ask_pr, sigma1m (order-flow features). `hours` max 168. Coverage is uneven and only covers whatever windows the WDE panel was actively open for a symbol — SOL and BNB have the most logged history, other symbols may return no rows for a recent window; widen `hours` or try a different symbol if so. `timeframe` = "15m", "1h", "4h", or "1d" for day/swing work: real OKX perp candles instead of order-flow logs (always available, not dependent on the WDE panel being open). `field` is one of open, high, low, close, volume, ret_pct (bar-over-bar % return), range_pct (bar high-low as % of close), body_pct (close-open as % of open), rsi14, vol_ratio (volume vs its 20-bar average). `hours` max ~1500 bars worth (e.g. up to ~62 days for "1h").
| Name | Type | Req | Description |
|---|---|---|---|
| field | string | yes | — |
| hours | number | — | — |
| symbol | string | yes | — |
| timeframe | string | — | — |
Structured output declared, but exposes no named fields.
No examples provided.
get_funding ~80
Current perpetual funding rate and crowding read for a crypto coin (are longs or shorts paying / crowded). Use for "what's the funding rate on <coin>", "is funding positive". `coin` = ticker e.g. 'btc'. Bearer-auth with a Pro API key for real-time data.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | yes | — |
Structured output declared, but exposes no named fields.
No examples provided.
get_order_flow ~95
Positioning regime + open interest + recent taker imbalance for a crypto coin — whether a move is new longs, short covering, fresh shorts, or deleveraging. Use for "crypto order flow", "open interest change", "is this a short squeeze". `coin` = ticker e.g. 'btc'. Bearer-auth with a Pro API key for real-time data.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | yes | — |
Structured output declared, but exposes no named fields.
No examples provided.
market_rotation ~82
Cross-sectional momentum ranking across the whole crypto perp universe right now — which coins are leading (top percentile) vs lagging (bottom percentile). Use this FIRST when asked to "find a coin" or "what should I look at" before drilling into one with the other tools. Requires an EnsoTrade Pro API key.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | — |
Structured output declared, but exposes no named fields.
No examples provided.
market_snapshot ~92
One combined live snapshot for a crypto coin: price, 24h change, funding, open interest, perp basis, positioning regime. `coin` = ticker e.g. 'btc'. Bearer-auth with a Pro API key for real-time data plus the validated funding-momentum directional signal (public calls get a 15-minute-delayed price and no directional call).
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | yes | — |
Structured output declared, but exposes no named fields.
No examples provided.
options_chain ~65
Full crypto options chain for a coin: strikes, mark IV, greeks, and the Black-Scholes fair-value gap per contract. Requires an EnsoTrade Pro API key. `coin` = underlying ticker e.g. 'btc'.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | yes | — |
Structured output declared, but exposes no named fields.
No examples provided.
perp_dashboard ~89
Full perp dashboard for a crypto coin: mark price, index price, funding rate + next funding time, open interest, 24h high/low/volume. Requires an EnsoTrade Pro API key (Bearer auth) — generate one at ensotrade.tech, Account -> Developer Access. `coin` = ticker e.g. 'btc'.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | yes | — |
Structured output declared, but exposes no named fields.
No examples provided.
save_strategy ~234
Save a formula as a strategy IF it currently validates. Re-runs test_formula itself server-side first — never trusts a stale claim from an earlier call, since data moves — and only saves when that fresh verdict is 'validated'. Saved strategies appear in the user's own EnsoTrade dashboard under Strategies; they're private to that account, not published or shared with anyone else. Same parameters as test_formula: `symbol`/`formula` as usual, `timeframe`="scalp" (use `horizon`) or "15m"/"1h"/"4h"/"1d" (use `horizon_bars`), `hours` = history window tested. `label` is an optional short name for the strategy (e.g. "BTC 1h RSI reversion"). Requires an EnsoTrade Pro API key.
| Name | Type | Req | Description |
|---|---|---|---|
| formula | string | yes | — |
| horizon | string | — | — |
| horizon_bars | integer | — | — |
| hours | number | — | — |
| label | string | — | — |
| symbol | string | yes | — |
| timeframe | string | — | — |
Structured output declared, but exposes no named fields.
No examples provided.
test_formula ~869
Invent a formula over EnsoTrade's data, and get back whether it actually predicts forward returns — validated on a holdout split, not just fit to the whole window. `formula` is a math expression combining any of the fields listed in fetch_series' docstring (for the same `timeframe`) with +, -, *, /, **, %, unary +/-, and abs/min/max/ sqrt/log/log1p/exp/sign/clip/mean/std, e.g. "ofi1 * vpin - dofi / 2" or "sign(qi) * sqrt(abs(obi))". No other Python is executed — this runs through a restricted, default-deny expression evaluator, not eval(). `timeframe="scalp"` (default, WDE order-flow, second-scale): `horizon` is which forward return to correlate against — ret_1s_bp, ret_5s_bp, ret_30s_bp, or ret_60s_bp. `hours` max 720 (30 days). `timeframe` = "15m"/"1h"/"4h"/"1d" for day/swing strategies (real OKX candles, always available): use `horizon_bars` instead of `horizon` — the forward % return N candles ahead (e.g. horizon_bars=4 on timeframe="1h" = predicting the move 4 hours out). `hours` max ~1500 bars worth; a small `hours` still fetches at least 150 bars (the minimum needed for a meaningful 70/30 split) rather than failing outright, so the actual window tested can be wider than requested for a small `hours` value. Either mode needs enough rows that a 70/30 split leaves >=150 total. Returns train (first 70% chronologically) and holdout (untouched final 30%) Spearman/Pearson correlations plus a verdict: 'validated' only if holdout |spearman| >= 0.15 AND same-signed as train — this guards against keeping a formula that only looked good by chance on one slice of data. ALSO returns, computed on the holdout portion only: - `net`: risk-adjusted performance AFTER trading costs — sharpe, sortino, max_drawdown_pct, calmar, ann_return_pct, ann_volatility_pct, win_rate_pct, profit_factor. Sharpe is annualized and corrected for overlapping horizons (a horizon spanning N bars sampled every bar is subsampled to non-overlapping periods first, which removes the ~sqrt(N)…
| Name | Type | Req | Description |
|---|---|---|---|
| fee_bp | number | — | — |
| formula | string | yes | — |
| horizon | string | — | — |
| horizon_bars | integer | — | — |
| hours | number | — | — |
| slippage_bp | number | — | — |
| symbol | string | yes | — |
| timeframe | string | — | — |
Structured output declared, but exposes no named fields.
No examples provided.
top_movers ~50
Top gaining and losing crypto perpetuals right now, ranked across the whole market. Use for "top crypto movers", "biggest crypto gainers and losers today".
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | — |
Structured output declared, but exposes no named fields.
No examples provided.