JW3 MCP Server
REMOTE · NZHBFEAHYMMYQERZJGBT.SUPABASE.CO
JW3.ai remote MCP server for market reads and confirm-gated trading execution.
Available components
Last scanned (14 hours ago)
Scores higher than 77% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 7195 tokens (~287/item across 25 items; 25 tools + 0 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 Management32
- Stability check failed: schema churn in the 12 days we've observed: 2 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 25 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 28 to 32.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 22 to 25.
- 18 Nov 26 0
- Tool “reserve_sweep” rewrote its description, which is the text the model reads security
- Tool “set_exits” rewrote its description, which is the text the model reads security
- 17 Nov 26 +1
- Tool “cancel_order” rewrote its description, which is the text the model reads security
- Tool “close_position” rewrote its description, which is the text the model reads security
- Tool “execute_trade” rewrote its description, which is the text the model reads security
- Tool “reserve_sweep” rewrote its description, which is the text the model reads security
- Tool “set_exits” rewrote its description, which is the text the model reads security
- “close_position” reworded the description of “size” cosmetic
- 15 Nov 26 −1
- Stability: 0.17 → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “build_defi_tx” was removed ▼ security
- Tool “read_defi” was removed ▼ security
- Tool “read_onchain_balances” rewrote its description, which is the text the model reads security
- Tool “daily_prep” no longer declares itself destructive security
- Tool “propose_diary_note” no longer declares itself destructive security
- Tool “reconcile_realized_pnl” no longer declares itself destructive security
- “execute_trade” added an optional parameter “agentId” cosmetic
- “read_live_datum” reworded the description of “exchange” cosmetic
- “read_live_datum” reworded the description of “kind” cosmetic
- “read_news_brief” reworded the description of “source” cosmetic
- “read_live_datum” dropped the optional parameter “max_age_seconds” cosmetic
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 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.
- 11 Nov 26 +1
- Tool “list_open_orders” rewrote its description, which is the text the model reads security
- Tool “read_onchain_balances” rewrote its description, which is the text the model reads security
- New tool “read_venue_balances” functional
- “list_open_orders” reworded the description of “connectionId” cosmetic
- “list_open_orders” reworded the description of “exchange” cosmetic
- “list_open_orders” made “exchange” optional cosmetic
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 21 Nov 2026 · Probed https://nzhbfeahymmyqerzjgbt.supabase.co/functions/v1/mcp-server
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=supabase.co | CN=WE1,O=Google Trust Services,C=US | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | d2b50611cd88e9c50e4e2231f4d3f059 |
| SANs: supabase.co, *.supabase.co | ||||||
| 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 nzhbfeahymmyqerzjgbt.supabase.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| co. | DS published | 7786 | 8 | Verified |
| supabase.co. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://nzhbfeahymmyqerzjgbt.supabase.co/functions/v1/mcp-server/.well-known/oauth-protected-resource", error="invalid_token"
Bearer resource_metadata="https://nzhbfeahymmyqerzjgbt.supabase.co/functions/v1/mcp-server/.well-known/oauth-protected-resource", error="invalid_token" | Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Protected resource metadata
| Document | https://nzhbfeahymmyqerzjgbt.supabase.co/functions/v1/mcp-server/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://nzhbfeahymmyqerzjgbt.supabase.co/functions/v1/mcp-server |
| Authorisation server | https://www.jw3.ai/mcp |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://nzhbfeahymmyqerzjgbt.supabase.co/functions/v1/mcp-server | Verified | 200 | |
| http (plaintext) | http://nzhbfeahymmyqerzjgbt.supabase.co/functions/v1/mcp-server | HTTPS enforced | 301 | https://nzhbfeahymmyqerzjgbt.supabase.co/functions/v1/mcp-server |
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 →
analyze_market JEV market verdict ~401
SERVER-EXECUTED, read-only: ask the JEV decision model for a typed verdict (verdict + agreement% + snapshot age). Pass family (cex | dex_perps | prediction) + venue + symbol. The server builds multi-timeframe candles itself for CEX (venue+symbol only); dex_perps needs snapshot.timeframes [{tf, candles:[{o,h,l,c,v?}]}]; prediction needs snapshot.brief ONLY — 2–6 research notes YOU assemble ({title, snippet, url, at} with real URLs you can vouch for): the server fetches the live book itself and grounds the call, so never paste prices as snapshot.market (a model-supplied market is ignored). Call this BEFORE any trade proposal and cite the verdict (agree/disagree + why) in the proposal thesis — uncertain/mixed verdicts mean no trade. NEVER narrate instead of calling it.
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | string | – | Alias of venue (chat compat). |
| family | string | yes | Market family matching the planned trade. |
| pair | string | – | Alias of symbol (chat compat). |
| snapshot | object | – | Optional override: { timeframes: [{tf, candles: [{o,h,l,c,v?}]}] } for cex/dex_perps, { market, brief: [{title, snippet, url, at}] } for prediction. Omit for CEX — the server builds candles itself; d… |
| symbol | string | – | Pair, ticker, or condition id (e.g. BTC/USDT). Required for cex unless the snapshot already carries timeframes; prediction takes the Polymarket conditionId/slug or Opinion market id. |
| venue | string | – | Venue slug (e.g. binance, kucoin, polymarket). Required for cex unless the snapshot already carries timeframes; prediction defaults to polymarket. |
No output schema declared.
No examples provided.
cancel_order Cancel CEX order ~146
Cancel an open CEX order by order id. Needs trade:execute. CANCELS ARE NEVER BLOCKED BY THE KILL SWITCH (D4): a cancel always passes, even with the switch on or autonomy=propose_only — the switch stops NEW positions only.
| Name | Type | Req | Description |
|---|---|---|---|
| connectionId | string | – | CEX connection id (see list_connections). Takes precedence over exchange. |
| exchange | string | yes | CEX slug, e.g. kucoin |
| market | string | – | Optional market scope. Omit to search both. |
| orderId | string | yes | Venue order id to cancel |
| pair | string | – | e.g. BTC/USDT (helps venue routing) |
No output schema declared.
No examples provided.
close_position Close CEX position ~252
Close an open CEX futures position (or reduce it) with a reduce-only market order. Real money. Needs the trade:execute scope. EXITS ARE NEVER BLOCKED BY THE KILL SWITCH (owner decision D4): a close, a reduce-only order and a cancel always pass, and the switch plus autonomy=propose_only stop only NEW positions. NEVER touch positions the user marked manual unless explicitly asked.
| Name | Type | Req | Description |
|---|---|---|---|
| connectionId | string | – | CEX connection id (see list_connections). Takes precedence over exchange. |
| exchange | string | yes | CEX slug, e.g. kucoin |
| pair | string | yes | e.g. BTC/USDT |
| side | string | yes | Side of the OPEN position |
| size | string | – | Size to close, in the unit the positions tool reported for this venue — contracts on OKX swaps, the contract's own size on Kraken, base units elsewhere. Omit to close the whole leg on the named side:… |
No output schema declared.
No examples provided.
daily_prep Daily pre-trading brief ~131
Build the morning brief (risk header, positions, 5-venue funding/OI, liquidation proxy, macro 24h, regime, JEV bias per name) and record it as the day's 'Daily analysis' in the diary. Reads need mcp:read; the diary write needs trade:propose (or pass write:false for a dry run). Sections carry [DATA]/[PROXY]/[UNAVAILABLE] tags — gaps are never synthesized.
| Name | Type | Req | Description |
|---|---|---|---|
| day | string | – | YYYY-MM-DD (default today UTC) |
| write | boolean | – | Record into diary_day_notes (default true) |
No output schema declared.
No examples provided.
execute_trade Execute live CEX order ~962
Execute a live CEX order immediately (real money) via stored exchange keys. Needs the trade:execute scope AND user YOLO eligibility (kill switch off, autonomy != propose_only) — entries are the one class the switch blocks; closes, cancels and exit legs always pass (D4). Caps enforced per order. Fee-aware: pass stop to refuse stops that cannot survive round-trip fees (min-move gate), or risk_usd to size from risk (needs stop, else an ATR stop from venue klines). Returns the fee estimate + min-move in the result. CEX spot/futures only — never on-chain.
| Name | Type | Req | Description |
|---|---|---|---|
| actor | string | – | WHO is placing the order. 'machine' for the trading machine; 'owner' for the account owner's own manual trading. The account is SHARED, so this is what tells the machine's trades from the owner's whe… |
| agentId | string | – | Optional agent id this session is bound to (max 64 chars). Forwarded to cex-proxy, which verifies it belongs to you and applies that agent's per-agent caps/kill switch; a foreign or forged id is refu… |
| amount | string | – | Base units, e.g. 0.05 (omit when risk_usd sizes the order) |
| clientOid | string | – | Optional caller-supplied identity tag for the order (max 36 chars, [A-Za-z0-9_-]). A later session uses it to attribute the order to its owner instead of classifying it as foreign/unknown-origin. Omi… |
| connectionId | string | – | CEX connection id (see list_connections). Takes precedence over exchange. |
| exchange | string | yes | CEX slug, e.g. kucoin |
| idempotency_key | string | – | Optional per-INTENT key. Two submits with the same key are the same intent: the second is deduped and never dispatched again. Use it when a submission may be retried (a timeout, a reconnect) so a ret… |
| leverage | number | – | Futures only; rides the order (KuCoin has no venue-level setting) |
| marginMode | string | – | Futures only; isolated bounds max loss to position margin (default cross) |
| market | string | – | Which market to trade (default spot) |
| pair | string | yes | e.g. BTC/USDT |
| price | string | – | Limit price. OMIT for a market order. When the order type is 'market' the price is only a reference for sizing and is NOT sent to the venue — a resting limit has no position to protect, so the exit l… |
| referencePrice | string | – | For a MARKET order only: the price the exit legs were derived from. The venue may fill the entry at a different price, and the server REBASES the stop and target onto the actual fill (each keeps its… |
| risk_usd | number | – | Max USD loss at the stop — sizes the order as risk_usd / stop distance (needs stop, else ATR stop from venue klines; capped by max_position_usd + lot step). |
| side | string | yes | Order side: buy|sell |
| stop | number | – | Protective stop price (> 0). Gated server-side: stops inside round-trip fees x factor are refused with the shortfall spelled out, and armed as a venue-native SL exit leg after the entry across all CE… |
| tp | number | – | Take-profit price (> 0) armed with the entry as a single 100%-share venue-native TP exit leg across all CEX venues. Must sit on the profit side of the entry (long: above, short: below). |
| tpLegs | array | – | Optional 1-3 split take-profit legs ({ price, share }, where share is 1..100 percent of entry size) armed as venue-native TP orders after the entry. |
| tpPrice | number | – | Deprecated alias of tp. |
| type | string | – | Order type. Defaults to 'limit' when a price is given, else 'market'. Use 'market' for a live entry: the exit legs are venue-native conditionals that attach to a POSITION, so a RESTING LIMIT has no p… |
No output schema declared.
No examples provided.
get_insights Insights summary ~238
READ-ONLY: one-shot summary of the user's Insights page — market regime (BTC/ETH price + 24h, total market cap, Fear & Greed, ETF 7d net flow, stablecoin supply), cross-venue funding extremes, the fee-aware carry board, DEX perp volume share, the caller's own fee drag from the Diary, headlines, and a deterministic brief. Values may be null/unknown; missing blocks are listed in `gaps` and are never synthesized. Cite as 'observed at <time>'. Optional args: days (1-90, default 30), notional_usd (default 10000), fee_bps (default 5). Never trades, never writes.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Lookback in days for the rollup, 1..90 (default 30). |
| fee_bps | number | – | Round-trip fee assumption in basis points, 0..100 (default 5). |
| notional_usd | number | – | Notional in USD used to price the carry board and the fee drag, > 0 (default 10000). |
No output schema declared.
No examples provided.
list_connections List CEX connections ~114
READ-ONLY: list the user's connected CEX venues (id, exchange slug, label, status, markets) so follow-up reads can target a connectionId. `markets` is spot|futures|both as verified at save (Kraken dual keys; KuCoin/Bitget futures scope) — a row with markets=both covers perpetuals, so prefer it for positions reads. Returns metadata only, never keys or secrets. Call this first when the user asks about positions, balances, or anything per-exchange.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_fills List CEX execution fills ~209
READ-ONLY: list recent execution fills on a CEX connection (individual order executions with price/qty/fee, spot + futures). Never moves funds, never writes Diary rows — fills are Activity history (see read_closed_pnl for realized PnL). Unimplemented venues return an empty list; a venue walk that exceeds its time budget fails loud, never truncated-as-empty.
| Name | Type | Req | Description |
|---|---|---|---|
| connectionId | string | – | CEX connection id (see list_connections). Takes precedence over exchange. |
| days | number | – | Lookback in days, 1..90 (default 30) |
| exchange | string | – | CEX slug, e.g. kucoin (resolved to an active connection; connectionId wins when both are given) |
| limit | number | – | Max rows, newest-first, 1..500 (default 100) |
| market | string | – | Which fills to read (default all) |
| pair | string | – | Optional filter, e.g. BTC/USDT |
No output schema declared.
No examples provided.
list_open_orders List open CEX orders ~188
READ-ONLY: resting open orders across the user's CEX connections (spot + futures) — the same per-venue envelope as agent-chat kind=open_orders ({kind, observedAt, venues:[{connectionId, exchange, label, ok, orders, count}]}). Narrow with exchange and/or connectionId, filter one market with pair; omit all three to fan out across every active connection. An empty book reads as no resting orders, never as a flat position.
| Name | Type | Req | Description |
|---|---|---|---|
| connectionId | string | – | CEX connection id (see list_connections). Takes precedence over exchange. Omit to read every active connection. |
| exchange | string | – | CEX slug, e.g. kucoin (resolved to active connection(s); connectionId wins when both are given). Omit to read every active connection. |
| pair | string | – | Optional filter, e.g. BTC/USDT |
No output schema declared.
No examples provided.
propose_bracket Propose bracket order ~290
APPROVAL CARD ONLY — NEVER auto-executed: propose one atomic bracket (entry + protective stop + 1–3 OCO take-profits) for in-app approval. Recorded as a proposed setup row (Diary → setups → Send to ticket). Never executes, never moves funds. Needs the trade:propose scope (PAT).
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Base amount, e.g. 0.05. Must be > 0. |
| entry_price | number | – | Required when entry_type=limit. Must be > 0. |
| entry_type | string | yes | market = fill now; limit = resting entry at entry_price |
| exchange | string | yes | CEX slug, e.g. kucoin |
| fee_usd | number | – | All-in fee in USD. Omit or null if unknown — never 0-substituted. |
| pair | string | yes | e.g. BTC/USDT |
| rationale | string | yes | One-sentence why-now |
| side | string | yes | buy = long, sell = short |
| stop_price | number | yes | Protective stop. Long: below entry; short: above. Must be > 0. |
| take_profits | array | yes | 1–3 take-profit legs {price > 0, weight (or fraction) 0..1 of position}. Weights should sum to ~1. |
No output schema declared.
No examples provided.
propose_close_all_positions Propose close-all ~152
APPROVAL CARD ONLY — NEVER auto-executed: propose flattening EVERY open position at once (or one venue/pair scope) for in-app approval. Records the proposal only — no order is placed, nothing is cancelled. Needs the trade:propose scope (PAT).
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | string | – | Optional CEX slug to flatten one venue only. Omit for every connected venue. |
| limit_price | string | – | Required for order_type=limit. |
| order_type | string | – | Default market. |
| pair | string | – | Optional pair filter (e.g. BTC/USDT) — flatten only this market. Omit for everything. |
| rationale | string | yes | Why flatten now |
No output schema declared.
No examples provided.
propose_diary_note Propose diary note ~127
Append (default) or replace a markdown note on one diary day (diary_day_notes upsert — the same append/replace write the agent-chat approval path and daily_prep perform). Diary-only: never executes a trade, never moves funds. Needs the trade:propose scope (PAT).
| Name | Type | Req | Description |
|---|---|---|---|
| body_md | string | yes | Markdown note content, 1..4000 chars (longer bodies are cut) |
| day | string | – | Day in YYYY-MM-DD format (default today UTC) |
| mode | string | – | append (default) or replace the day's note |
No output schema declared.
No examples provided.
propose_predict_market Propose prediction trade ~221
APPROVAL CARD ONLY — NEVER auto-executed: propose a prediction-market trade for in-app approval. JEV-gated: pass the consult_jev family=prediction verdict (run analyze_market first) — a call without one is refused. Recorded as a proposal trail row. Never executes, never moves funds. Needs the trade:propose scope (PAT).
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | Optional pUSD amount to spend (must be > 0 when provided) |
| confidence | number | – | Optional agreement-weighted conviction 0–1 |
| jev_verdict | string | yes | The consult_jev family=prediction verdict (run analyze_market first) — required |
| market_id | string | yes | Polymarket conditionId or slug, or Opinion market id |
| question | string | – | Optional human-readable question, for UI display |
| rationale | string | yes | Why this market and side now |
| side | string | yes | Outcome to buy |
| venue | string | – | Default polymarket (executable). opinion is proposal-only. |
No output schema declared.
No examples provided.
propose_trade Propose trade setup ~306
APPROVAL CARD ONLY — NEVER auto-executed: propose a trade setup for the user to approve in-app (Diary → setups → Send to ticket). Never executes, never moves funds. Needs the trade:propose scope (PAT).
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | Base symbol, e.g. BTC |
| entry | number | yes | Entry price, must be > 0 |
| invalidation | string | – | Optional invalidation note captured alongside the proposal |
| jev_verdict | string | – | Optional caller-supplied JEV verdict captured alongside the proposal |
| kronos_captured_at | string | – | Optional ISO timestamp of the Kronos vote |
| kronos_direction | string | – | Optional Kronos oracle vote direction |
| kronos_expected_move_pct | number | – | Optional Kronos expected move in percent |
| kronos_horizon | number | – | Optional Kronos horizon (positive integer) |
| pair | string | yes | e.g. BTC/USDT |
| side | string | yes | Side to propose: buy|sell (long|short accepted as aliases, normalized to buy|sell) |
| size_usd | number | – | Suggested size in USD, must be > 0 |
| stop | number | yes | Stop-loss price, must be > 0 |
| thesis | string | – | One-paragraph rationale |
| timeframe | string | – | e.g. 4h |
| venue | string | – | CEX slug or perps venue |
No output schema declared.
No examples provided.
propose_trade_ideas Propose trade ideas ~212
APPROVAL CARD ONLY — NEVER auto-executed: propose 1–3 personalized trade opportunities (best-first) for in-app approval. Each idea is recorded as a proposed setup row (Diary → setups → Send to ticket) plus one batch trail row. Never executes, never moves funds. Needs the trade:propose scope (PAT).
| Name | Type | Req | Description |
|---|---|---|---|
| ideas | array | yes | 1–3 trade ideas, best-first. Each: pair (e.g. BTC/USDT), side buy|sell (long|short accepted as aliases), entry > 0, stop > 0 (long: stop<entry, short: stop>entry), targets 1–3x {price>0, weight (or f… |
| jev_verdict | string | – | Optional caller-supplied JEV verdict captured alongside the batch (run analyze_market first for a fresh one) |
| rationale | string | yes | One-sentence why-now for the batch |
No output schema declared.
No examples provided.
read_closed_pnl Read closed CEX PnL ~206
READ-ONLY: realized/closed-PnL history on a CEX connection (one row per closed position carrying net pnl + fees, for diary sync). Never moves funds. Rows whose venue reports no side stay null — side is never inferred from the PnL sign; Binance rows carry entryPrice 0 = unknown (the income feed has no entry price) and exitPrice is the paired closing fill when one was found.
| Name | Type | Req | Description |
|---|---|---|---|
| connectionId | string | – | CEX connection id (see list_connections). Takes precedence over exchange. |
| days | number | – | Lookback in days, 1..90 (default 30) |
| exchange | string | – | CEX slug, e.g. kucoin (resolved to an active connection; connectionId wins when both are given) |
| limit | number | – | Max rows, newest-first, 1..500 (default 100) |
| pair | string | – | Optional filter, e.g. BTC/USDT |
No output schema declared.
No examples provided.
read_diary_day Read diary day ~200
READ-ONLY: read one diary day (trades, setups, analyses, actions) or an explicit day RANGE. Never writes — saving a note stays a propose_diary_note approval card. Pass an explicit day (YYYY-MM-DD) or an explicit start_day + end_day range (inclusive, max 31 days) — there is no today default, so ask the user when no day is given. Returns the most recent rows first with totals; quote it as observed diary state, not a live venue read.
| Name | Type | Req | Description |
|---|---|---|---|
| day | string | – | One day in YYYY-MM-DD format (required when no range is given; no default — ask the user). |
| end_day | string | – | Range end in YYYY-MM-DD format, inclusive. Requires start_day; the range caps at 31 days. |
| start_day | string | – | Range start in YYYY-MM-DD format, inclusive. Requires end_day; the range caps at 31 days. |
No output schema declared.
No examples provided.
read_live_datum Read live CEX datum ~1,132
READ-ONLY: fetch ONE specific live datum on demand (open positions, account balances, or a market quote) instead of waiting for the context snapshot. Never moves funds, never places an order, never widens the context on its own — ask for exactly the datum you need. Returns numbers WITH the venue and a fetch timestamp; report them as 'observed at <time> on <venue>'. If the result has no fetched number, say the value is unavailable — NEVER invent a placeholder. Present positions/balances/order reads as an inline markdown table in your reply text (never 'shown above'); when empty, say 'No open positions' explicitly. Not for writing anything; use a propose_* tool when the user wants an action.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional market scope for kind=order|open_orders: spot|linear. Omit to search both on perp venues. |
| chains | string | – | Optional comma list to filter kind=onchain, e.g. ethereum,solana. |
| connectionId | string | – | CEX connection id for positions|balances|open_orders (see list_connections). Omit to read every active connection. REQUIRED for kind=order (an order id is connection-scoped). |
| exchange | string | – | Venue slug for kind=market and kind=screener (e.g. binance). For positions|balances|open_orders, narrows to one venue; omit to read every connection. |
| kind | string | yes | Which datum to read. positions = open derivatives positions with mark/liq/leverage (rows also carry their resting venue-native exit legs as exits[] with TP/SL triggers across all CEX venues, or exits… |
| market_id | string | – | Prediction market selector for kind=predictions scope=orders|quote (and to narrow positions): Polymarket conditionId (0x…), slug, or numeric id; Opinion market id. |
| orderId | string | – | Venue order id for kind=order (e.g. the orderId a placeOrder/YOLO fill returned). |
| scope | string | – | Prediction read scope for kind=predictions (default markets). markets = liquid open markets scan; positions = the user's open prediction positions (wallet-scoped, needs connected creds or wallets=);… |
| status | string | – | Optional position-status filter for kind=predictions scope=positions: OPEN|REDEEMABLE|REDEEMABLE_LOST|CLOSED|MERGEABLE (default OPEN, Polymarket; Opinion returns its open positions). |
| symbol | string | – | Required for kind=market (e.g. BTC/USDT). Optional pair filter for kind=open_orders (e.g. BTC/USDT narrows the resting book). |
| tag | string | – | Optional tag pill to filter kind=predictions scope=markets: politics|crypto|sports|economy|ai|tech (Polymarket tag_slug; Opinion matches its category labels best-effort). Omit for the most liquid ope… |
| token_id | string | – | Outcome token id for kind=predictions scope=quote: Polymarket CTF clobTokenId (orderbook + tick-size + taker-delay) or Opinion token id (latest price). |
| venue | string | – | Prediction venue for kind=predictions: polymarket|opinion|all. Scan (scope=markets) defaults to polymarket; positions|orders read both venues unless narrowed; quote defaults to polymarket unless the… |
| wallets | string | – | Optional csv of 0x wallet addresses for kind=predictions scope=positions (merged with the stored Polymarket funder; capped at 10). Omit to read the connected wallets only. |
| withExits | boolean | – | Accepted for backward compatibility (older CLI versions send it): positions reads always carry their resting venue-native exit legs as exits[] with TP/SL triggers across all CEX venues, or exitsUnkno… |
No output schema declared.
No examples provided.
read_news_brief Read crypto news brief ~243
READ-ONLY: fetch the latest crypto headlines as keyword-matched news clusters for fundamentals analysis (ETF flows, unlocks, macro, hacks — read the headlines here, act through a propose_* tool). Optional pair (BTC, ETH, or SOL — also accepts BTC/USDT or BTC-USD forms) narrows to that asset's keywords; omit it for all three. Returns the top clusters newest-first with per-item source links and recency (publishedAt + ageHrs) plus a fetch timestamp; quote them as 'observed at <time> from <source>'. If no headlines match, say so — NEVER invent a headline.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max items kept per asset cluster, 1..12 (default 6). |
| pair | string | – | Optional asset filter: BTC, ETH, or SOL (BTC/USDT and BTC-USD forms accepted). Omit for all three. |
| source | string | – | optional publisher filter, free text (e.g. CoinDesk); omit for every publisher |
| window_hrs | number | – | Harvest window in hours, 1..168 (default 48). |
No output schema declared.
No examples provided.
read_onchain_balances Read onchain balances ~294
DEPRECATED — use read_live_datum kind=onchain: this alias runs the exact same reader and returns the same shape, and it stays only for older CLI versions. Read-only onchain wallet balances across EVM/Solana/TON/Tron/BTC via the balance cache + public RPCs. Server resolves the user's wallet addresses itself (addresses only, never keys). The chains filter uses canonical slugs and matches non-EVM chains exactly — `sol` never matches `solana`, `bitcoin` reads as `btc`; one linked EVM address is readable on any requested EVM chain. TON matches by chain slug, not address form — raw (0:…), bounceable (EQ…) and non-bounceable (UQ…) versions of one wallet resolve to the same balance. Every linked wallet and every requested chain gets an explicit row in `reads` (ok | empty | invalid-address | no-wallet): lowercased Solana/Tron rows surface as invalid-address with a re-link hint instead of vanishing.
| Name | Type | Req | Description |
|---|---|---|---|
| chains | string | – | Optional comma list of canonical chain slugs, e.g. ethereum,solana. Non-EVM slugs (solana, ton, tron, btc) match exactly — no aliases or substrings; ton covers every TON address version. EVM slugs ex… |
No output schema declared.
No examples provided.
read_risk_limits Read risk limits ~45
READ-ONLY: read the user's risk posture (kill switch, autonomy level, caps, daily usage). Never edits limits — the agent must check this before proposing live size.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
read_venue_balances Read venue-held balances ~198
READ-ONLY: venue-held funds per linked wallet address — Hyperliquid (mode-aware total), Aster (keyless per-asset), dYdX (subaccount equity), Pacifica (account by Solana address), Polymarket (spendable pUSD + positions value). Reads are public and keyless against the EXPLICIT owner address (never an agent address); each row names the address it read. A failed venue nulls its leg — never a coerced 0. Omit venue to read every linked venue; totalUsd sums the legs that answered and partial:true names every leg that did not.
| Name | Type | Req | Description |
|---|---|---|---|
| venue | string | – | Venue to read: dydx|hyperliquid|polymarket|aster|pacifica, or all (default). `hl` is accepted as an alias of hyperliquid. One row per venue per linked address; totalUsd sums the legs that answered. |
No output schema declared.
No examples provided.
reconcile_realized_pnl Reconcile realized PnL against the daily loss cap ~177
Counts the venue's realized LOSSES against the daily risk counters. A trade closed by the VENUE's own stop never goes through the close path, so without this the daily loss cap can never fire on it. Idempotent: each venue trade is counted exactly once, tracked in the realized-PnL ledger. Never moves funds, never places an order. Returns how many trades were counted, the loss recorded, and what was skipped and why.
| Name | Type | Req | Description |
|---|---|---|---|
| connectionId | string | – | CEX connection id (see list_connections). Takes precedence over exchange. |
| days | number | – | How far back to reconcile, in days, 1..30 (default 2) |
| exchange | string | – | CEX slug, e.g. kucoin (resolved to an active connection; connectionId wins when both are given) |
No output schema declared.
No examples provided.
reserve_sweep Sweep KuCoin futures reserve to trade ~288
KuCoin reserve sweep (real money on live fire): keeps `keep` units of `currency` in the futures wallet and moves the excess futures -> main -> trade in two legs carrying the same amount. Dry-run by default (plan only, zero bytes to the venue, no YOLO gate). Live fire (dryRun:false) needs the trade:execute scope AND user YOLO eligibility (kill switch off, autonomy != propose_only) — a sweep moves funds, so it mirrors transferReserve and stays gated while exits and cancels never are. A 2xx is not a completed sweep: each leg's answer is read, leg 1 failing stops before leg 2, a partial sweep says where the funds are, and nothing is ever retried. KuCoin only.
| Name | Type | Req | Description |
|---|---|---|---|
| connectionId | string | – | CEX connection id (see list_connections). Takes precedence over exchange. |
| currency | string | – | Settlement asset to sweep: USDT, USDC, BTC or ETH (XBT accepted as BTC; default USDT) |
| dryRun | boolean | – | Plan only, moves nothing (default true). Pass false to fire both transfer legs. |
| exchange | string | yes | CEX slug — kucoin only (resolved to an active connection; connectionId wins when both are given) |
| keep | number | – | Units of currency to leave in futures (default 10) |
No output schema declared.
No examples provided.
set_exits Arm position exits ~463
Arm or replace venue-native SL and/or TP on an open CEX position. Spot legs work on every venue; a LINEAR (futures) leg only on binance, bybit, okx, kucoin, gateio, bitget, bingx and kraken — mexc and coinbase have no linear exit path and refuse one. Clears existing stops on the pair and arms the new legs sized against the live position. EXITS ARE NEVER BLOCKED BY THE KILL SWITCH (owner decision D4): arming or replacing a stop or target always lands, including while the switch is on or autonomy is propose_only. Needs the trade:execute scope. The server reads the live position's mode and sends each venue its documented CLOSE form (hedge: Bitget tradeSide=close, BingX positionSide, OKX posSide; one-way: reduce-only), and refuses with nothing cancelled and no leg sent when the mode cannot be read.
| Name | Type | Req | Description |
|---|---|---|---|
| connectionId | string | – | CEX connection id (see list_connections). Takes precedence over exchange. |
| exchange | string | yes | CEX slug, e.g. binance, bybit, okx, kucoin, gateio, mexc, bitget, bingx, coinbase, kraken |
| market | string | – | Which market the open position is on (default futures). Spot needs quantity. |
| pair | string | yes | e.g. BTC/USDT |
| quantity | number | – | Spot only: position size in base units (the venue reports no spot position to size against) |
| referencePrice | number | – | The price the stop and take-profit were DERIVED FROM. The server rebases both legs onto the position's ACTUAL entry price, keeping their distances, so a fill that came in better than the reference ca… |
| slPrice | number | – | Stop-loss trigger. Must sit on the loss side of the entry (long: below, short: above). |
| tpPrice | number | – | Take-profit trigger. Must sit on the profit side of the entry (long: above, short: below). |
No output schema declared.
No examples provided.
How do I install the JW3 MCP Server server?
JW3 MCP Server is a hosted endpoint at https://nzhbfeahymmyqerzjgbt.supabase.co/functions/v1/mcp-server, 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 · nzhbfeahymmyqerzjgbt.supabase.co
claude mcp add --transport http agnostic4321-ops-jw3-mcp-cli 'https://nzhbfeahymmyqerzjgbt.supabase.co/functions/v1/mcp-server'
What is the JW3 MCP Server server?
JW3 MCP Server is listed in the public MCP registry as io.github.agnostic4321-ops/jw3-mcp-cli. JW3.ai remote MCP server for market reads and confirm-gated trading execution. This page covers its hosted endpoint (https://nzhbfeahymmyqerzjgbt.supabase.co/functions/v1/mcp-server).
Is the JW3 MCP Server server safe to use?
JW3 MCP Server scores 80 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 JW3 MCP Server server expose?
JW3 MCP Server exposes 25 tools: read_live_datum, analyze_market, read_diary_day, list_connections, propose_trade, and 20 more. Their descriptions and schemas cost roughly 7,195 tokens of context every time the server is loaded.
Does the JW3 MCP Server server require authentication?
Yes. JW3 MCP Server asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the JW3 MCP Server server still maintained?
JW3 MCP Server is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the JW3 MCP Server server?
VerifyMCP ran 13 checks on JW3 MCP Server, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.