JW3 MCP Server
io.github.agnostic4321-ops/jw3-mcp-cliagnostic4321-opsstreamable-httpv0.1.1Scanned
JW3.ai remote MCP server for market reads and confirm-gated trading execution.
26 tools: 8 can delete or cancel things, 5 change things and 13 only read.
- Reads private data · 0
- Reads text others write · 17
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
8 tools here can delete or cancel things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the JW3 MCP Server can do
The JW3 MCP Server is published by the GitHub account agnostic4321-ops. It has 26 tools. It can delete or cancel things (8 tools: propose_diary_note, close_position, set_exits, cancel_order and 4 more) and create or change data (5 tools: propose_trade, propose_trade_ideas, propose_bracket, propose_predict_market and 1 more). 13 tools only read.
17 tools bring in text other people can write (read_live_datum, analyze_market, read_onchain_balances and 14 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 9, 2026, version 0.1.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
26 tools
Deletes or cancels 8Claude Code: deny
cancel_orderCancel an open CEX order by order id.Reads text others writeNo findings
Why it is in this group
- The name "cancel_order" says "cancel": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Cancel an open CEX order by order id. Needs trade:execute + YOLO eligibility; per-call kill-switch/autonomy check.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
close_positionClose an open CEX futures position (or reduce it) with a reduce-only market order.Reads text others writeNo findings
Why it is in this group
- The name "close_position" says "close": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 unless explicitly asked.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
daily_prepBuild 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 dia…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- openWorldHint: true
execute_tradeExecute a live CEX order immediately (real money) via stored exchange keys.Reads text others writeNo findings
Why it is in this group
- The name "execute_trade" says "execute": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
propose_diary_noteAppend (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).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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).
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
reconcile_realized_pnlCounts the venue's realized LOSSES against the daily risk counters.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "count": a word for reading.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- openWorldHint: true
reserve_sweepKuCoin 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 a…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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). KuCoin only.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
set_exitsArm 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).Reads text others writeNo findings
Why it is in this group
- The name "set_exits" says "set": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 the live position. Needs trade:execute + YOLO eligibility.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
Changes things 5Claude Code: ask
propose_bracketAPPROVAL CARD ONLY — NEVER auto-executed: propose one atomic bracket (entry + protective stop + 1–3 OCO take-profits) for in-app approval.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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).
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
propose_close_all_positionsAPPROVAL CARD ONLY — NEVER auto-executed: propose flattening EVERY open position at once (or one venue/pair scope) for in-app approval.No findings
Why it is in this group
- The name "propose_close_all_positions" says "close": a word for a change.
Description, as the server wrote it 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).
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
propose_predict_marketAPPROVAL CARD ONLY — NEVER auto-executed: propose a prediction-market trade for in-app approval.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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).
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
propose_tradeAPPROVAL CARD ONLY — NEVER auto-executed: propose a trade setup for the user to approve in-app (Diary → setups → Send to ticket).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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).
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
propose_trade_ideasAPPROVAL CARD ONLY — NEVER auto-executed: propose 1–3 personalized trade opportunities (best-first) for in-app approval.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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).
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 13Show 13 read-only tools
analyze_marketSERVER-EXECUTED, read-only: ask the JEV decision model for a typed verdict (verdict + agreement% + snapshot age).Reads text others writeNo findings
Why it is in this group
- The name "analyze_market" says "analyze": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
build_defi_txREAD-ONLY / UNSIGNED: build an unsigned DeFi transaction payload (supply, redeem, borrow, repay, claim) or quote LP amounts (quote_lp) via the official Binance Web3 DeFi API.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "read": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it READ-ONLY / UNSIGNED: build an unsigned DeFi transaction payload (supply, redeem, borrow, repay, claim) or quote LP amounts (quote_lp) via the official Binance Web3 DeFi API. Never signs, never broadcasts, never touches private keys — returns unsigned contract calldata (and optional simulation result) for wallet signing or CLI inspection.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
get_insightsREAD-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 fundi…Reads text others writeNo findings
Why it is in this group
- The name "get_insights" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
list_connectionsREAD-ONLY: list the user's connected CEX venues (id, exchange slug, label, status, markets) so follow-up reads can target a connectionId.No findings
Why it is in this group
- The name "list_connections" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
list_fillsREAD-ONLY: list recent execution fills on a CEX connection (individual order executions with price/qty/fee, spot + futures).Reads text others writeNo findings
Why it is in this group
- The name "list_fills" says "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
list_open_ordersList open orders on a CEX connection (spot + futures).Reads text others writeNo findings
Why it is in this group
- The name "list_open_orders" says "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it List open orders on a CEX connection (spot + futures). Read-only.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
read_closed_pnlREAD-ONLY: realized/closed-PnL history on a CEX connection (one row per closed position carrying net pnl + fees, for diary sync).Reads text others writeNo findings
Why it is in this group
- The name "read_closed_pnl" says "read": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
read_defiREAD-ONLY: query DeFi protocols, yield/lending/liquid-staking/LP/RWA markets, or wallet positions across all 10 Binance Web3 DeFi chains (BNB 56, Ethereum 1, Base 8453, Arbitrum 42…Reads text others writeNo findings
Why it is in this group
- The name "read_defi" says "read": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it READ-ONLY: query DeFi protocols, yield/lending/liquid-staking/LP/RWA markets, or wallet positions across all 10 Binance Web3 DeFi chains (BNB 56, Ethereum 1, Base 8453, Arbitrum 42161, Arc 5042, Polygon 137, Optimism 10, Avalanche 43114, Robinhood 4663, Katana 747474). Returns APY, base/reward APY breakdown, TVL, redeemDelayDays, yieldAnalytics, and investmentId with a fetch timestamp. Use propose_defi when the user wants an action card.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
read_diary_dayREAD-ONLY: read one diary day (trades, setups, analyses, actions) or an explicit day RANGE.No findings
Why it is in this group
- The name "read_diary_day" says "read": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
read_live_datumREAD-ONLY: fetch ONE specific live datum on demand (open positions, account balances, or a market quote) instead of waiting for the context snapshot.Reads text others writeNo findings
Why it is in this group
- The name "read_live_datum" says "read": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
read_news_briefREAD-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 p…Reads text others writeNo findings
Why it is in this group
- The name "read_news_brief" says "read": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
read_onchain_balancesRead-only onchain wallet balances across EVM/Solana/TON/Tron/BTC via the balance cache + public RPCs.Reads text others writeNo findings
Why it is in this group
- The name "read_onchain_balances" says "read": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
read_risk_limitsREAD-ONLY: read the user's risk posture (kill switch, autonomy level, caps, daily usage).No findings
Why it is in this group
- The name "read_risk_limits" says "read": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write17
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 17, 2026, 15:21 UTC, unchanged since Nov 10, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 13
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 13 tools that change things (5 destructive, 8 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://nzhbfeahymmyqerzjgbt.supabase.co/functions/v1/mcp-server: tools/list returned 25 tools to an anonymous client, including close_position (destructive), set_exits (destructive), cancel_order (destructive), execute_trade (destructive), reserve_sweep (destructive) and 8 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http jw3-cli https://nzhbfeahymmyqerzjgbt.supabase.co/functions/v1/mcp-serverclaude mcp add --transport http jw3-cli https://nzhbfeahymmyqerzjgbt.supabase.co/functions/v1/mcp-serverRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__jw3-cli__read_live_datum",
"mcp__jw3-cli__analyze_market",
"mcp__jw3-cli__read_diary_day",
"mcp__jw3-cli__list_connections",
"mcp__jw3-cli__read_onchain_balances",
"mcp__jw3-cli__list_open_orders",
"mcp__jw3-cli__list_fills",
"mcp__jw3-cli__read_closed_pnl",
"mcp__jw3-cli__read_risk_limits",
"mcp__jw3-cli__read_defi",
"mcp__jw3-cli__read_news_brief",
"mcp__jw3-cli__get_insights",
"mcp__jw3-cli__build_defi_tx"
],
"ask": [
"mcp__jw3-cli__propose_trade",
"mcp__jw3-cli__propose_trade_ideas",
"mcp__jw3-cli__propose_bracket",
"mcp__jw3-cli__propose_predict_market",
"mcp__jw3-cli__propose_close_all_positions"
],
"deny": [
"mcp__jw3-cli__propose_diary_note",
"mcp__jw3-cli__close_position",
"mcp__jw3-cli__set_exits",
"mcp__jw3-cli__cancel_order",
"mcp__jw3-cli__reconcile_realized_pnl",
"mcp__jw3-cli__daily_prep",
"mcp__jw3-cli__execute_trade",
"mcp__jw3-cli__reserve_sweep"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as jw3-cli. Review it before you use it.
Capability tags behind 17 rules
- mcp__jw3-cli__read_live_datum untrusted-input
- mcp__jw3-cli__analyze_market untrusted-input
- mcp__jw3-cli__read_onchain_balances untrusted-input
- mcp__jw3-cli__close_position untrusted-input
- mcp__jw3-cli__set_exits untrusted-input
- mcp__jw3-cli__cancel_order untrusted-input
- mcp__jw3-cli__list_open_orders untrusted-input
- mcp__jw3-cli__list_fills untrusted-input
- mcp__jw3-cli__read_closed_pnl untrusted-input
- mcp__jw3-cli__reconcile_realized_pnl untrusted-input
- mcp__jw3-cli__daily_prep untrusted-input
- mcp__jw3-cli__execute_trade untrusted-input
- mcp__jw3-cli__reserve_sweep untrusted-input
- mcp__jw3-cli__read_defi untrusted-input
- mcp__jw3-cli__read_news_brief untrusted-input
- mcp__jw3-cli__get_insights untrusted-input
- mcp__jw3-cli__build_defi_tx untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.agnostic4321-ops/jw3-mcp-cli/verify?hash=3f87ed7b4f3a9c029e3ded6bc65b60e87e0db5018721cd83334e5f0adbcd1112" | jq -e '.changed == false'Pinned hash 3f87ed7b4f3a, from Nov 9, 2026, 15:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.agnostic4321-ops/jw3-mcp-cli/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.agnostic4321-ops/jw3-mcp-cli)Source: MCP Registry · repository. Synced Nov 9, 2026, 15:17 UTC.
JW3 MCP Server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the JW3 MCP Server safe?
- No scan can promise that. What its definitions show: 26 tools, 13 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the JW3 MCP Server delete data?
- Yes. 8 tools can delete, cancel or revoke something: propose_diary_note, close_position, set_exits, cancel_order, reconcile_realized_pnl, daily_prep and 2 more.
Can the JW3 MCP Server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the JW3 MCP Server have?
- 26 tools: 8 destructive, 5 write, 13 read. propose_diary_note, close_position, set_exits, cancel_order, reconcile_realized_pnl, daily_prep, execute_trade, reserve_sweep and 18 more.
Does the JW3 MCP Server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the JW3 MCP Server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the JW3 MCP Server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 9, 2026.