JW3 MCP Server
JW3.ai remote MCP server for market reads and confirm-gated trading execution
Reviews
No review yet. Used JW3 MCP Server? Be the first to help others choose.What it does
JW3 MCP Server is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 21h ago (live check)Hosted endpoint
https://nzhbfeahymmyqerzjgbt.supabase.co/functions/v1/mcp-serverstreamable-http
In Claude Code: claude mcp add --transport http jw3-mcp-server https://nzhbfeahymmyqerzjgbt.supabase.co/functions/v1/mcp-server
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"jw3-mcp-server": {
"url": "https://nzhbfeahymmyqerzjgbt.supabase.co/functions/v1/mcp-server"
}
}
}Live check
Electra Index connected to the hosted endpoint 21h agoONLINE JW3 MCP Server answered an MCP connection on 15 Nov 2026 and introduced itself as jw3-agent 1.0.0 (MCP protocol 2025-06-18).
25 tools offered to AI assistants
read_live_datum· 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 exanalyze_market· 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+sread_diary_day· 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 (ilist_connections· 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) — apropose_trade· 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).propose_diary_note· 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 tradpropose_trade_ideas· 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 executepropose_bracket· 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 fundspropose_predict_market· 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 trpropose_close_all_positions· 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 (PATread_onchain_balances· 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 cachread_venue_balances· 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 publ
Show 13 more
close_position· Close an open CEX futures position (or reduce it) with a reduce-only market order. Real money. Needs the trade:execute scope AND user YOLO eligibility; per-call kill-switch/autonomy check. NEVER touch positions the user marked manual unlessset_exits· Arm or replace venue-native SL and/or TP on an open CEX position (spot or futures across binance, bybit, okx, kucoin, gateio, mexc, bitget, bingx, coinbase, kraken). Clears existing stops on the pair and arms the new legs sized against thecancel_order· Cancel an open CEX order by order id. Needs trade:execute + YOLO eligibility; per-call kill-switch/autonomy check.list_open_orders· 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 exlist_fills· 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). Uniread_closed_pnl· 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; Binareconcile_realized_pnl· 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 eread_risk_limits· 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.daily_prep· 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:proposeexecute_trade· 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); caps enforced per order. Fee-aware: pass stop to refuse stops treserve_sweep· 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 venuread_news_brief· 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 accepget_insights· 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 shar
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Version | 0.1.1 | DECLARED | SRC-001 Official MCP Registry | 10h ago |
| Hosted endpoint | https://nzhbfeahymmyqerzjgbt.supabase.co/functions/v1/mcp-server | DECLARED | SRC-001 Official MCP Registry | 10h ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 10h ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 10h ago |
| Website | https://www.jw3.ai | DECLARED | SRC-001 Official MCP Registry | 10h ago |
| Repository | https://github.com/agnostic4321-ops/jw3-mcp-cli | DECLARED | SRC-001 Official MCP Registry | 10h ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 10h ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 10h ago |
Change history
- VERSION09 Nov 20260.1.0 → 0.1.1
- NEW09 Nov 2026first seen in the index
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is JW3 MCP Server still online?
Free alerts · no account▲ 0Do you run JW3 MCP Server? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about JW3 MCP Server
How do I connect JW3 MCP Server?
Use the hosted endpoint https://nzhbfeahymmyqerzjgbt.supabase.co/functions/v1/mcp-server in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does JW3 MCP Server offer?
When Electra Index connected on 15 Nov 2026, it listed 25 tools: read_live_datum, analyze_market, read_diary_day, list_connections, propose_trade, propose_diary_note, propose_trade_ideas, propose_bracket and more. The full list is in "Live check" above.
Is JW3 MCP Server online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 21h ago.