MCP Server

Bring your own AI

The VYX MCP server gives your own AI — Claude Desktop, Claude Code, claude.ai, ChatGPT, Codex, Cursor, or any client that speaks the Model Context Protocol — the sight of the desk's own analyst and hands on your positions. It reads your board scored live — the analyst's whole board if you ask — previews candidates before saving, composes signals and regimes, stands up and steers the desk's analyst, files reads and setup cards on your desk, and trades with you: you analyze together, agree on a setup, and it places and manages the position from the conversation. Your practice books are open to it on every plan, Free included, so the two of you can work real setups on play money from the first message; the live wallet needs a trading plan and the live switch on. The in-app chat is the zero-setup way to do all this on us; the MCP server is the same copilot running on your own AI subscription, so your usage scales with the plan you already pay your AI provider for. On connect it briefs your client with built-in instructions — what VYX is, what each metric means, the workflow, and the guardrails — so a fresh session uses it well from the first message. It is non-custodial: the key it trades with can place and close but never withdraw, live trading is off until you (or your AI, on your word) turn it on, and it cannot connect a wallet, change your guardrails, clear your kill switch, or enable or arm a desk trader.

Connect it (one URL, no install)

Add the connector URL below in your AI client and sign in to VYX when it asks — that is the whole setup. There is nothing to install, it speaks Streamable HTTP, it works on mobile, and it auto-updates. Signing in this way grants your AI full access to compose on your account — signals, regimes, desks, watchlists, and trader strategies — so it can get you set up rather than only look around. You approve that on a consent screen that lists exactly what it can touch, and you can revoke it anytime under Settings → API & integrations. No account yet, or signed out? Create one or sign in right on that screen — the connection carries on to the approve step without leaving the tab. Connecting is free on every plan.

https://api.vyx.app/mcp

Client-by-client

The same URL works everywhere. Where a client asks for an API key instead of a sign-in, mint one under Settings → API & integrations and send it as a Bearer token. Every AI you have signed in this way is listed there too, under Connected apps — what it can reach, when you authorized it, and when it last acted — and Disconnect severs it on the spot: the app loses access now, not at its next token renewal.

• ChatGPT — on the ChatGPT website (its phone app can’t add one), open Plugins, press + and choose Add custom MCP server. Name it VYX, paste the connector URL, choose OAuth for the sign-in, accept the warning and create it, then sign in to VYX when prompted. No Add custom MCP server in the + menu? Turn on Developer mode under Settings → Security and login, then try again.
• Claude (claude.ai, Desktop, Code) — add it as a custom connector and authorize with your VYX account.
• Codex, Cursor, and other MCP clients — add the same URL as a remote MCP server.
• Anything that wants a token instead of a sign-in — Authorization: Bearer vyx_sk_live_…

Authorization: Bearer vyx_sk_live_…

After a VYX update: reconnect once

We add options to the tools as VYX grows. Most AI clients remember the tool list from the moment you connected and check every call against it before sending, so right after an update your AI may say an option "was unexpected" — that call never reached VYX. Reconnect once and it reads the new list. The reading tools accept options they do not recognize, so an option added to them later reaches a client that connected after this change without any reconnect. Tools that change your account or place orders keep a strict list on purpose: a client that checks stops an order carrying an option VYX does not know, rather than letting it through half-understood.

• ChatGPT — open Plugins, open VYX and refresh it; if there is no refresh, remove it and add it again with the same URL.
• Claude — Settings → Connectors, disconnect VYX and connect it again, then start a new chat.
• Any other client — remove the server and add the same URL back.

Let your AI set you up

The fastest way to a working desk is to ask for one. Once connected, your AI can read the live market, compose the signals that catch what you care about, stand up a desk around them, and explain what it built — the setup work you would otherwise do by hand in the app. It can trade with you too: practice books need no setup at all, and the live wallet opens the moment the live switch is on — a switch your AI flips when you tell it to trade live. Wallets, guardrails, the kill switch and any desk trader's enable/arm stay with you in the app.

• "Connect to VYX, look at what the market is doing, and build me a desk for catching liquidity sweeps on the majors."
• "Set up VYX for someone who trades funding-rate extremes — compose the signals, preview them first, and light the ones that discriminate."
• "Read my board and tell me what it is set up to catch, in plain English."
• "Catch me up on my markets since last night." — one vyx_catch_up call (the morning_read prompt) instead of a scan and a read per market.
• "Work my Mean reversion desk for A+ setups, top-down, and show me each read in the vyx feed as you go." — the hunt_setups prompt walks this: the desk's mandate first, then the field and regimes, the higher timeframe, the tape, and only then a call.
• "Analyze the premarket rally on META end to end." — the read_the_move prompt pages back to where the move actually began, reads what flow did through each third of it, and only then looks at the current bar.

Tools: see the market

The read tools are the in-app chat's sight, served fresh on every call — live scoring for every plan, not cached engine runs. Every number comes with its unit and the bar it covers, a value that cannot be known on a bar (the forming bar's volume, a window deeper than the history read) reads n/a rather than 0, the newest bar of a candle history says it is still forming, and a table states its own counts so your AI copies them instead of counting.

• vyx_catch_up — what you missed, in one call: since a time you choose (12 hours by default, up to 48), your desk's regime readings then and now, every lit signal that switched on and on which market (a signal made only of on/off conditions set one way says whether every one of its conditions came true, or how many did and which — when it switched on and now; one set both ways, such as a bullish and a bearish cluster, reads buy or sell with the condition that made it, then and now), a line for each of your pinned markets — the move, where it sits in the window's range, net taker flow, open-interest change, funding and the desk's score with the signals lit in it (one made only of on/off conditions says whether every one of its conditions is true, or how many are and which; where a screen — a signal made only of on/off conditions — holds inside that score, the line also says what the score is without it, since a screen's vote is the direction it was set to: the market's side for a condition such as a bid lean or a new high, but not for one that holds both ways, such as RSI outside 30–70) — and the news in the window. Nothing pinned? It covers the biggest movers and the markets where signals switched on. Name a saved desk to read it without switching to it. The board reaches back about 280 bars, so a long window at 1-minute bars covers only its last few hours — the reply says so.
• vyx_scan — your board scored live by your active desk's signals (or one named signal — one of yours, or one a built-in desk lights, read as that desk runs it), with per-signal contributions and where price sits in its recent range — and where a signal made only of on/off conditions all set one way holds inside a market's Total, what that Total reads without it, since such a condition votes the direction it was set to — the market's side for a condition such as a bid lean or a new high, but not for one that holds both ways, such as RSI outside 30–70. A side filter, a buy/sell sort and a minimum score pick on the Total, the board's own colours, and the reply names the markets a held condition moved in or out, so an oversold market an RSI screen holds on is named in a sell-side answer. Conditions set opposite ways — a bullish and a bearish cluster — light by whichever holds, so that side stays in the Total and the signal reads as buy or sell on each market, as the board paints it. Sort, filter, and cap the slice. Ask for the analyst view and it returns the desk analyst's whole board as text instead — the session clock, the field, each regime as its recent series, every row with its percentile against its own history, price against range and ATR, higher-timeframe trends, fillability, co-movers and chart structure, the tape, positions, live setups and the record — the same context the analyst hunts from.
• vyx_symbol — one market read top-down. It opens by saying what the market is — its name and the venue's one-line description — so an index such as Bitcoin Dominance is never read as a coin's price. Then: where price sits in its recent structure and the path that got it there, the tape (sweeps, absorption, presses, level tests, range breaks — with what is still standing), then your signals' scores with the per-indicator why, and the current bar last. Read it again one interval up for the higher frame. Any Hyperliquid market reads, including ones your desk's board filters out — those come back with the same structure, tape and microstructure, and say plainly that they carry no desk score. Ask for bars and the candle history comes back under a window summary: what price did across the whole slice, and what order-flow imbalance, cumulative volume delta and open interest did through each third of it — so a rally that ran the whole way on negative book pressure reads at a glance instead of bar by bar. The reply also says whether older bars exist and hands back the exact timestamp to page further, so your AI knows when it is holding a slice of a move rather than the move. Each page further back comes back on its own and quickly, without the live read of the market — that rides the first call. Pass fields and any formula variable or expression (trade count, base volume, the bar's CVD change, its move net of BTC, a 96-bar volume sum) comes back as a column beside each candle, evaluated by the same engine your signals run on.
• vyx_search — screen the whole universe by one metric condition (spread, imbalance, OFI, funding, OI change, and more).
• vyx_regime — your regime tiles evaluated on the live universe. Each tile's high, neutral or low names the fixed rule behind it — above or below 0, a share of its markets, or above or below its baseline — not where it sits in its own range. Ask for the series and each tile comes back over its last 100 bars, oldest to newest — the read the desk analyst gets — so where now sits against the read's own range is yours to see, not a label's. Name any saved desk, a window (from, to) or a page (before) and it reads that desk's tiles over the past instead — one row per closed bar with the bar's open and close in UTC, each tile's value and how many markets it counted — without switching the desk you have open. To line a tile up with an event, ask for the window ending at the event's time and read the last row: that bar had closed by then.
• vyx_signal_history — how one market has been scoring over time. Leave the signal out and it reads your whole desk: every lit signal and the Total per bar, exactly as the board blends them — an on/off signal reads hold rather than its set direction, and where one holds inside the Total a second column gives what the other signals read without it; name a signal to drill in — one of yours, or one a built-in desk lights, read as that desk runs it. Signals that fire on a few bars list just those bars, so "when did the desk last fire on BTC, and which way?" is one call. Ask for detail and every bar shows each indicator's raw value, its normalized value and whether its condition passed, with what each condition tests in the column key — the inputs behind the score, so your own AI can reproduce a firing in its own backtest. Name several signals and they come back time-aligned in one table, a stage machine's stages side by side, with each one's firing runs listed as events (on, off, how many bars). A draft replays too, nothing saved: pass the indicators of a variant instead of a name, several drafts for the aligned table, or one draft with a sweep to see it once per value — so your AI watches a variant bar by bar before it grades or saves it. Closed bars only; the header says which bars the venue may still correct and what is exact. A value a bar cannot carry reads n/a with the reason — warming up (needs N bars), no tape on the forming bar, a field that bar lacks, not applicable on this market (relative strength on BTC itself) — and sits out of the score; vyx never prints a 0 for a number it could not compute.
• vyx_levels — a signal's level zones on one symbol (one of yours, or one a built-in desk lights): price bands, touches, breaks, and where price sits against each zone (inside, or above / below by how much). Zones start from the bars a signal fired on, and the reply says so when a window had none.
• vyx_pulse — the live order-flow pulse over the liquid crypto perps (the 60 most-traded that are deep enough to trade), from the latest closed hour, with a legend of what each number means — led by the session clock and the markets out of character for that hour against their own 90-day normal (pass session — asia, london, newYork or overnight — to read the boards over that session instead), and what the options market prices for BTC, ETH, SOL, HYPE, XRP, AVAX and TRX (implied volatility, the implied hour and day move, skew, put/call open interest, the next expiry's biggest strikes). Pass view: read for the market read — it opens with the whole market before any asset class: how many markets rose and fell, the median move, volume against normal, net taker flow and how many moved against their own flow; then one row each for crypto, equities, indices, commodities and FX with their breadth, flow, the Market Internals and Market Sentiment signals averaged across the class, the event screens firing in it and its positioning; then whether each class and the whole market reads risk-on or risk-off, trending or chopping, and how confident, with the rule behind it. Then the story of the latest Asia, London or New York session across every liquid market (crypto, stocks, indices, metals, oil, currencies): a storyline and threads, the groups, money flows, extremes and headlines behind them, and what would confirm or break each storyline by the next open, with how it turned out once that time has passed. Pass since with view: read — the asOf your last read returned, or how long ago, such as 3h — and the read comes with what changed since you last looked: the reads written since, the playbook conditions that flipped, and over the hours since where the biggest money went, money that reversed, open interest that turned, volume far above normal and the biggest movers. Pass view: brief for the morning brief — written each weekday at 13:00 UTC (6am Pacific) for a trader starting the US day: what happened since New York closed, the regime, and a playbook that runs to the US cash close. Pass view: open for the first 15 minutes after the US cash open — one 15-minute bar across every market, written right after it closes, with a playbook to the close. Add desk: active (or one of your desks by name) and either read comes through that desk: its universe, the regime over just those markets, where the money went and what was unusual inside it, the playbook conditions on its markets, its regime rows live and the markets its signals light right now.
• vyx_news — the live news wire behind the board: crypto wires plus world coverage, each item mapped to the markets it names with freshness and an expected direction. The catalyst check — if nothing on the wire names a mover, the move is flow.
• vyx_list / vyx_watchlists — your saved objects and watchlists as a short index, the count first: each signal's name, id, how it combines, how many indicators it has, when it last changed and which desks it is lit on. Ask for one signal by id or name and it comes back whole — indicators, formulas, weights, gates and levels. Kind templates lists the built-in desks as they ship today. For signals, match narrows the index to names containing a piece of text — the same filter vyx_delete deletes by.
• vyx_positions — every position you are holding right now, real money and practice books alike, in one list, each labelled with the trade desk that opened it and the stops and targets on it. Size, entry, mark, unrealized PnL, leverage and liquidation come from the venue for real positions and from the practice book for practice ones. It reads every builder-dex market you trade, not just the main exchange, so nothing you hold is quietly left out. A position VYX has no record of opening is shown as unattributed rather than guessed at. If Hyperliquid is briefly too busy to share your trade history, your positions, equity and orders still come back — only the desk label reads unavailable, and your AI is told to ask again in about 30 seconds. Filter by desk, or by book.
• vyx_analyst_latest / vyx_trader_decisions — the desk analyst, desk-scoped: the standing orders it runs under, its faculties and cadence, whether it is running, the setup cards it filed newest first, and the desk's record by author; and a trader's auditable decision log (what it decided and why). Raise limit to page further back.
• search / fetch — a plain-language way in: find the markets, signals, or desks relevant to a question, then pull the full live record for one. Clients that only support these two (ChatGPT's research modes among them) can still read VYX through them.

Tools: studies and setup cards

Most sessions with your AI are a search for an idea, not a call. These tools let it show its work on your desk as it goes — the Workbench tab in the desk’s left rail fills in the moment each read is filed — and file a setup card when a real level and an invalidation exist.

• vyx_analyze — file a study on the desk, in the vyx feed: a chart (one market at an interval, with the next timeframe up drawn hollow behind it), a comparison (the market against the ones it moves with, every line rebased to zero at the window's start — name the peers, or let the desk pick the strongest co-movers), a metric (OFI, CVD, funding, open interest or volume over the window), or a signal read (one signal's score bar by bar — name a signal on your desk, or let your AI compose one and score it without saving it, which you can then Keep as signal from the bench), or a regime read (your desk's regime tiles over a past window you name in UTC — each tile its own row on one timeline, with up to three markets drawn above as their move from the window's open; point at any moment to read that bar across every row, the same numbers your AI reads from the regime history). Your AI chooses what to look at and writes one sentence; VYX draws it from the venue's own candles, so nothing on the bench is a number the model made up. Every analysis is kept; the bench scrolls back as far as the record goes.
• vyx_analyses — read the bench: what has been filed on a desk, newest first, or only what one setup linked.
• vyx_create_setup — file a setup card: symbol, side, archetype, the context (the regime, where price sits in the higher timeframe, and optionally the market's group — one sentence each, settled before the thesis), thesis, entry, invalidation and two targets. It is held to the same fence as the desk's analyst — entry near the last price, every level inside the recent range, ordered for the side — and a card without its context is not filed. The card wears your AI as its author, links the analyses it leaned on, and is graded by VYX exactly like the analyst's: from the bar its entry prints. A stop or the 48-hour deadline reached before the entry ever prints voids the card — no trade happened, so no result is claimed. Your AI can also point at what it means with up to two marks — a stretch of candles, one candle, or a price level, by bar time as vyx_symbol printed it: VYX checks each against the market’s real bars, a mark the bars don’t show is dropped and named in the reply (the card still files), and hovering the card draws its marks on your chart beside the plan.
• vyx_setups — the desk's setup cards: the context, the frame, the marks its author pointed at on the chart, the status and grade (including void and withdrawn), when the entry filled, who authored each, and how many analyses it links — plus the desk's record by author, your AI's beside the analyst's and the desk trader's, so it calibrates on the outcomes before it.
• vyx_withdraw_setup — pull one of your AI's own live cards before it resolves, with a one-line reason. It stays on the record as withdrawn — a pulled call is information, never a deletion. Nothing is cancelled anywhere: a card was never an order.
• vyx_revise_setup — revise one of your AI's own live cards: pass only what changes. The revision runs the whole fence again; on success the original steps aside as withdrawn (revised) and points to the new card, so a call's lineage stays on the record. Up to three revisions per call. Its marks carry over unless the revision brings new ones, and are checked again.

Tools: trade together

Your AI can be your co-trader: the two of you analyze, agree on a setup, and it places and manages the position from the conversation — the same order ticket you use in the app, driven by your words instead of your click. No setup stands in the way: your practice books — play money at real prices — are open to it from the first message. The live wallet you approved in the app sits behind one switch on your account, off by default; when you tell your AI to trade live, it flips the switch itself, says so, and it stays on until either of you turns it off. Every live open passes your money guardrails against the venue's own account state and refuses with the reason when it would breach them; the kill switch stops everything; and when a desk trader is enabled on the wallet, that wallet is the trader's — the connection will not place, move or close anything beside it until you stop the trader. Every position it opens carries its stop from the first bar; a stop is moved cancel-first so the venue never holds two; every order records the desk it was sent from, so what you hold reads with who opened it. The key it trades with can place and close, never withdraw.

• vyx_trading_status — read first: your practice books (armed, equity, open positions), the approved live wallet and its network, whether live trading is on your plan, whether the live switch is on, the kill switch, the guardrails, and whether a desk trader currently owns the wallet.
• vyx_set_trading — the live switch: on lets connected AIs trade the approved wallet; off closes it again. Your AI flips it when you ask to trade live, and tells you it did.
• vyx_open_position — open a position you agreed on, practice or live: market (fills now, bracket rests at once) or limit / post_only (rests at price). Requires the stop; takes a target; size in coin units or USD notional; records the desk and the setup card it follows.
• vyx_close_position — close all or a fraction at market, reduce-only. A full close clears the orphaned stop and target; a partial re-sizes them to what remains. A limit add you have resting on the same market — and its own stop and target — is left as you placed it, and named in the reply.
• vyx_set_protection — move or set the stop and/or target on an open position. Only the sides you pass change; on the live book the old trigger is cancelled before the new one rests. A resting limit add's own stop and target are not the position's — Hyperliquid places them only once that add fills — so they are never moved or cancelled here.
• vyx_move / vyx_cancel — move a resting entry to a new price, or cancel one order by id.
• "Let's trade my Mean reversion desk together on the practice book, risking $50 a trade." — the trade_session prompt walks this: books and holdings first, the hunt, your yes, the order with its stop, then managing it with you one dated line at a time.

Tools: check, then build

The same check-your-work loop the in-app chat runs before it builds anything — a quick check on the live field, then a grade over history for each draft (nothing saved), and only the version that holds up gets created. A signal that lights a small share of the board (about 2–10% of market-bars) reads as events; one that lights most of it reads as noise.

• vyx_preview_indicator — one formula across the universe: range, median, dead-data detection.
• vyx_preview_signal — a candidate composite on the current bar: fire count, buy/sell split, dead gates, the top markets with each one’s value, and any field that reads nothing on Hyperliquid. A signal made only of on/off conditions set one way lists the markets where all its conditions are true instead of a buy/sell split, and apart from them the markets only some of its conditions light — its hit says its conditions are true, not which side a market is on. Conditions set opposite ways keep the buy/sell split, with each side’s markets listed under the condition that holds there. Nothing is saved.
• vyx_preview_regime — a candidate regime's reading, distribution, and whether it moves, with the same scope and relative options as vyx_create_regime, so a cohort row (memes, AI, a watchlist) or a row measured against crypto previews exactly as it will read, with its member count.
• vyx_create_signal — create or update a composite from the same rich item shape the chat composes.
• vyx_create_regime — one instrument of a desk's read: a regime tile (median, mean, dispersion, or breadth), market-wide or scoped to one sector or theme (memes, L1s, semis, AI), a set of asset classes, or a watchlist; relative:true reads a scoped tile minus the whole field. It lands on the desk's strip as it is created; place:true puts a cohort row under its own divider on the board and place:false brings it back to the band, and the reply says whether the desk's board is grouped so the row shows there yet.
• vyx_validate_signal — proof over about 1,000 bars of history, for a saved signal or for drafts that are never saved (up to four side by side on one window): how much of the board it lights, whether the markets it lights move more than the rest, and its direction after costs — and it names any on/off condition that never passed, or passed on nearly every bar. Pass sweep ({name: 'N', values: [4, 8, 12, 24]}) with one draft and every $N in its formulas takes each value in turn, on one window: one table, one row per value, the best by attention named — how a window or a lag is tuned without saving a signal per value. Pass classes (for example ['crypto']) and it grades only markets of those kinds, so each candle is measured against their own move and range, not a board mixed with equities and indices; every answer lists each kind, BTC and ETH against the rest of crypto, and the board in thirds by 24-hour volume, each with its fires, its markets and a 95% range. Pass ablate: true with a saved screen or one draft and it answers why a screen is dark: each condition alone, then the conditions stacked one by one, and the step where the lit share collapses named — so a condition that can never pass, or two states that never happen together, is found in one call instead of a dozen test signals. On a very wide board, drafts that rank against the whole field may be graded over fewer bars; the answer’s first line says how many and why.
• vyx_set_server_side — run a signal 24/7 server-side (Trader and up).
• vyx_delete — remove a saved object by kind and id; for signals, several ids in one call, or a whole family by a piece of its name ('_TEST', 'C2HD_'): the first call lists exactly what would go and deletes nothing, confirm: true deletes those, and the reply names each one. Deleted signals come off every desk that carried them.

Tools: work your trade desk

Full desk control, the way the in-app chat has it. A desk's lit signals are exactly what its AI trader trades — changing them changes what an armed trader acts on at its next tick, and your agent is briefed to say so before doing it. AI traders follow the same plan gating as in the app (Autopilot and up).

• vyx_desk — a desk whole, starting with its mandate: description and explainer (what it is for), the analyst's standing orders and faculties, the live setups that already stand across every author, then lit signals, interval, liquidity floor, its trader (strategy, mode, whether it can run and why), open trades, recent closed trades with R, and your armed posture. Your AI is briefed to read it before its first call and never to guess a desk's strategy from its signal names. If a desk was made from a starter desk, it says so and whether the starter has changed since; pass a template instead to read a starter desk as it ships, formulas and all.
• vyx_create_desk / vyx_switch_desk — stand up a new desk, empty or started from a starter desk exactly as Add on the starter shelf in New desk does in the app; switch the active one (syncs to your devices).
• vyx_set_desk_interval — set the bar a desk scores on (1m to 1d). It moves every lit signal together, like the desk's own interval control, so the analyst and trader read the same bar you do.
• vyx_set_desk_regimes — set, add or remove the regimes on a desk's strip. A desk's regimes are its read: the strip is exactly what its analyst reads, and what its setup cards must descend from.
• vyx_set_desk_signals — set, add, or remove the desk's lit signals by id or name.
• vyx_set_desk_columns — add or remove columns on the desk's Screen: one of your signals, a template, an indicator study or a formula. A column never lights the signal or changes how the board ranks markets; vyx_desk lists the desk's columns.
• vyx_create_analyst / vyx_edit_analyst / vyx_delete_analyst — the desk's analyst, whole: stand one up with its standing orders, faculties and cadence; steer it, switch it on or off; remove it and its cards. Turning an analyst on is safe authority — it files setup cards, never orders.
• vyx_set_desk_info — rewrite a desk's name, one-line description, or its ⓘ explainer (what it shows, how it's built, how to use it) in place. Send only the sections that changed and the rest keep their text — so when your AI relights a desk's signals or regimes, it can bring the desk's own description up to date without rebuilding the desk.
• vyx_set_analyst_brief — write a desk's standing orders: what it hunts, what it skips, how entries are timed, no-trade conditions. The same brief the desk's own analyst obeys, so one text steers both minds on the desk, and the next session starts from it instead of re-explaining. Creates the desk's analyst if it has none, left off until you turn it on.
• vyx_create_trader — compose the desk's autonomous follower with the chat's strategy model: summary, setups, planning, management, sizing, avoid. Always created disabled; running it stays with you.
• vyx_edit_trader — revise the strategy in place (version bumps, learnings preserved). It cannot enable, arm, or switch modes.
• vyx_create_watchlist / vyx_update_watchlist — named watchlists.
• vyx_share_desk — make a desk public and get its no-login link.

Tell us when something is wrong

Your AI can report a bug or send feedback straight from the session that hit it, with vyx_report_issue. It is briefed to file the moment a tool errors, the data reads back wrong, stale or empty, or it needed something no tool could do — rather than quietly working around it and leaving you with a worse answer. A fault report carries the exact call it made, what it expected, and the verbatim response; a vague one is refused with a list of what to add, so what reaches us is something we can reproduce. Feature requests and plain feedback go through the same tool and are held to a different bar — say what you want to be able to do and why today's tools cannot, and no reproduction is asked for. It reaches the VYX team directly, and your AI will tell you what it filed.

• vyx_report_issue — a bug, a data problem, a missing capability, or a feature request.
• "That 4h read looks off — report it to VYX with what you actually got back."
• "Ask VYX for a way to screen the whole universe by realized volatility, and say why I want it."

And read our answer back

Reports are not a one-way send. We read what your AI files the same day and answer in writing, and vyx_reports hands that answer back to the AI that filed it: where each report stands — being looked at, fixed, answered, queued, declined, or waiting on more detail from you — and the note we wrote to it. So a session that hit a wall last week starts by checking whether the wall is still there instead of building the same workaround again, and a fix reaches your AI without you having to relay it. Your AI sees the reports filed from your account and nobody else's. Ask it to check, or leave it to the prompt it already has. You see them too: every report your AI files sits in Support on the desk, with our answer under it.

• vyx_reports — the status and our written note on everything your account has filed, newest first.
• "Did VYX ever come back on that 4h candle problem you reported?"
• "Before you work around that again — check your filed reports."

Resources

Resources are read-only context you can attach so the model grounds its reasoning in your live board and the analyst's view — two analysts at once.

• vyx://signals — your signal definitions.
• vyx://board — your board scored live by your active desk signals.
• vyx://desk — your active trade desk whole: lit signals, trader, open trades, recent trades.
• vyx://pulse — the same order-flow pulse as a snapshot.
• vyx://analyst — the AI analyst's latest notes.

Guided prompts

The server ships slash-command prompt templates — pre-written best-practice workflows your client surfaces as commands. Pick one instead of writing the prompt yourself.

• get_started — new here: your AI reads the live market, composes signals for what you want to catch, previews them before saving, and stands up your first desk around the ones that survive.
• morning_brief — the pulse and regime across the universe plus your board digest and what changed.
• inspect_symbol — a deep microstructure read of one symbol (depth, imbalance, CVD, funding, OI, structure).
• build_signal — a guided composer: preview first, then vyx_create_signal.
• desk_review — read a desk whole, judge its trader's recent trades, and propose one strategy revision.

Example prompts

Or just ask in plain language and the model picks the right tools.

• "What is the order-flow pulse right now — where are funding and aggression concentrated?"
• "Scan my board and summarize the three strongest signals and why."
• "Preview a signal that fires when the book fractures — spread blowout plus an unstable spread — and create it if it discriminates."
• "Read my desk, review the trader's last ten trades, and suggest one change to its sizing rules."
• "Switch to my Majors desk and light only the OI Surge and Fracture signals."

What it will never do

The MCP server holds no execution authority, on purpose. It cannot place, modify, or cancel an order; it cannot enable a trader, arm your account, or switch a trader between analyst, testnet, and live. Traders it composes are born disabled. Your AI can see everything and shape everything — the decision to let a strategy touch money stays with you, inside the app, behind the same hard rails the built-in chat obeys.