{"id":"io.github.LuxAlgo/luxalgo-mcp-server","slug":"io-github-luxalgo-luxalgo-mcp-server","title":"LuxAlgo MCP","description":"LuxAlgo for AI agents: the Library, prop firms, Market Trackers, Edge Stats, and your Trade Journal","version":"2.1.0","publisher":{"kind":"github","id":"LuxAlgo","label":"@LuxAlgo on GitHub","url":"https://github.com/LuxAlgo"},"website":"https://www.luxalgo.com/mcp","repository":"https://github.com/LuxAlgo/luxalgo-mcp-server","remotes":[{"type":"streamable-http","url":"https://mcp.luxalgo.com/mcp"}],"packages":[{"registryType":"npm","identifier":"@luxalgo/mcp","version":"2.1.0","transport":{"type":"stdio"}}],"published":"2026-10-25","updated":"2026-10-25","status":"online","auth":"","latency_ms":1103,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"library_search","title":"Search the LuxAlgo Library","description":"Search the LuxAlgo Library — the encyclopedia of trading and technical analysis. One query over 800+ concepts (alias-aware: 'stochastics' finds Stochastic Oscillator) and 800+ ready-to-use indicators. Start here whenever you have a name, informal term, or topic; results carry slugs for the get tools plus canonical URLs for citation. Indicator hits that run on Vela carry `chart_url`, the link that ","read_only":true},{"name":"library_get_concept","title":"Get a Library concept","description":"Explain a trading concept: the Library's full write-up as markdown — definition, formula, how traders read it, and its indicator implementations. Use for any 'what is X / how does X work' question. Needs the exact slug — find it with library_search or library_list_concepts. `indicators` lists the concept's Library implementations, each with `chart_url` (opens it on a Vela chart) when it runs on Ve","read_only":true},{"name":"library_get_indicator","title":"Get a Library indicator","description":"Details for one indicator: what it does, how to read it, family, concept links, preview image — plus whether its source code is available (fetch the code itself with library_get_source_code). Use when the user asks about a specific indicator. `chart_url`, present when the indicator runs on Vela, opens it on a Vela chart.","read_only":true},{"name":"library_get_source_code","title":"Get an indicator's source code","description":"The Pine Script® source code of a Library indicator. Kept separate from library_get_indicator because sources are long — call it only when the user wants the code itself. For some indicators the app returns only the start of the source to a signed-out user (`complete: false`, with the line counts): signing in to a LuxAlgo account, free included, returns all of it. `chart_url`, present whenever the","read_only":true},{"name":"library_list_concepts","title":"List Library concepts","description":"Browse every trading and technical-analysis concept in the Library — paginated, optionally one family. Use to enumerate a topic area or find slugs for library_get_concept and the concept filter of library_list_indicators; for keyword lookup prefer library_search.","read_only":true},{"name":"library_list_indicators","title":"List Library indicators","description":"Browse the indicator catalog with filters and server-side sorting (newest first by default). The Library is organized by family and concept: filter by family (keys from library_list_families) or by concept slug (that concept's implementations; slugs from library_list_concepts or library_search), and optionally by trading platform or plan tier. Use for structured browsing — 'latest indicators', 'ev","read_only":true},{"name":"library_list_families","title":"List concept families","description":"The Library's top-level taxonomy: 17 families of trading concepts (trend, momentum, SMC/ICT, statistics, …) with concept counts and hub links. The natural first call for orientation.","read_only":true},{"name":"library_get_family","title":"Get a family hub","description":"A family's hub page as markdown — the written overview of that school of analysis plus its complete concept roster. Use after library_list_families, or when the user asks about a whole area like 'SMC' or 'Wyckoff'.","read_only":true},{"name":"propfirms_search","title":"Search prop firms","description":"Search LuxAlgo's prop-firm catalog (proprietary trading firms offering funded accounts). Combine firm filters (platforms, markets, payment/payout methods, country availability, Trustpilot, year founded) with nested challenge filters (account size, price, steps, profit split, trading rules) and offer filters — a firm matches when at least one of its challenges/offers matches all of them. Omit every","read_only":true},{"name":"propfirms_get","title":"Get a prop firm","description":"One prop firm's full dossier by slug: general profile (platforms, markets, payments, Trustpilot, restricted countries), every challenge with its rules, live offers with promo codes and affiliate links, and the written overview (about, rules, payout policy, FAQ). Find slugs with propfirms_search. Uncaptured (null) fields are omitted; challenges reference applicable offers via offerIds into the firm","read_only":true},{"name":"propfirms_search_challenges","title":"Search prop-firm challenges","description":"Search funded-account challenges across all visible prop firms. Filter by challenge rules (account size, fee, steps, profit split, drawdown mode, news/copy/auto trading, weekend holding, …) and by parent-firm properties. Pass propfirmId to list one firm's challenges, or challengeId to fetch specific ones. include=['offers'] returns a deduplicated top-level offers list, with each challenge referenc","read_only":true},{"name":"propfirms_search_offers","title":"Search prop-firm offers","description":"Search promotional offers (discounts and promo codes) across prop firms — defaults to live (active, unexpired) offers only. propfirmId narrows to one firm; challengeId resolves the offers that apply to a challenge (firm-wide offers included). Every offer carries the promo code, discount, end date, and affiliate link.","read_only":true},{"name":"propfirms_list_simulatable","title":"List prop firms and challenges","description":"List the prop firms in the live LuxAlgo directory together with every simulatable challenge (challengeId, display name, account size, currency, price, and its rule-semantics provenance). Call this first to discover the firmId + challengeId pairs accepted by propfirms_challenge_rules, propfirms_simulate, propfirms_optimal_risk, propfirms_compare and propfirms_simulate_trades. Challenges whose loss-","read_only":true},{"name":"propfirms_challenge_rules","title":"Get a challenge's full ruleset","description":"Fetch one directory challenge's complete ruleset (ChallengeSpec), adapted from the live LuxAlgo directory: evaluation steps (profit targets in percent units of the initial account, minimum trading days, time limits); the daily-loss rule with its exact semantics (basis = measured from prior-day balance vs prior-day equity; limitBasis = whether a pct limit is a fixed allowance of the initial balance","read_only":true},{"name":"propfirms_simulate","title":"Simulate a trader through a challenge","description":"Monte Carlo-simulate a trader with the given statistics through a prop-firm challenge and (by default) a funded horizon. Answers: \"What is my chance of passing per attempt, and of ever getting funded? How many attempts and how much total money should I expect? Is this challenge positive expected value for me, and which rule actually kills my attempts?\" Identify the challenge EITHER by directory re","read_only":true},{"name":"propfirms_optimal_risk","title":"Find pass- and EV-optimal risk per trade","description":"Sweep risk-per-trade over a grid, run the full journey simulation at every point, and report two optima separately: bestByPassProbability (the risk that maximizes a single attempt's chance of passing) and bestByEv (the risk that maximizes expected value across attempts, fees and funded payouts). They usually differ (diverges=true) - and that divergence is the insight: lower risk survives loss limi","read_only":true},{"name":"propfirms_compare","title":"Compare challenges for one trader","description":"Simulate the SAME trader across several challenges (directory references and/or inline specs, up to 12) under identical options and seed, and return one row per challenge sorted by expected value. THIS IS NOT A RANKING: rows are ordered by EV for the caller's specific inputs - trader stats, risk sizing, and options - and a different trader profile reorders them. The tool computes data for the user","read_only":true},{"name":"propfirms_simulate_trades","title":"Simulate from a real trade series","description":"Simulate a challenge by resampling the trader's OWN R-multiple trade series with a stationary block bootstrap instead of a win-rate model. Why resampling matters: challenge rules are breached by streaks, not by averages - a daily-loss limit dies to a cluster of losses inside one day, and a trailing drawdown dies to a losing streak right after an equity peak. Real trade series are streaky (autocorr","read_only":true},{"name":"propfirms_pass_rates","title":"Reference pass rates per archetype","description":"Reference challenge pass rates computed live from the directory's encoded rules with the same engine, seed (42), path count (10,000) and reference archetypes luxalgo.com/prop-firms uses — per challenge and per archetype (developing 45% win rate / consistent 48% / proven edge 52%, all risking conservatively). Returns per-attempt pass probability with 95% CI, P(funded), expected attempts and total c","read_only":true},{"name":"propfirms_validate_strategy","title":"Screen a strategy across all challenges","description":"Answer 'which challenges would MY strategy actually pass?' in one call: simulate the given strategy through every simulatable challenge in the live directory (optionally scoped by productType, account-size range, priceMax, or firm) and split the results by an explicit, caller-stated bar. Describe the strategy EITHER as real trades (rSeries/rSeriesText R-multiples, preferred: the stationary block b","read_only":true},{"name":"trackers_datasets","title":"List Market Trackers datasets","description":"The Market Trackers catalog: every dataset of US public-record market data the LuxAlgo pipeline publishes as CC0 dumps — congressional trades, insider (Forms 3/4/5) transactions, 13F holdings, federal contracts and grants, lobbying filings, FINRA short-sale volume, granted patents, clinical trials, FDA drug events, CFTC positioning, federal bills, FEC campaign finance, hearing transcripts, Federal","read_only":true},{"name":"trackers_query","title":"Query a Market Trackers dataset","description":"Search one Market Trackers dataset by ticker, free text, exact field values, and event-date range, with paging and newest/oldest ordering. Data is read from year-sharded CC0 dumps: pass years (or since/until) to choose which years to read — default is the newest year with data. Deep-history years (see archiveYears in trackers_datasets) can be tens of MB compressed each, so read them one or two at ","read_only":true},{"name":"trackers_latest","title":"Newest Market Trackers rows","description":"What the last daily publish added to one dataset — the newest ingestion day's rows (the dumps' latest.json), optionally narrowed by ticker or text. The cheapest way to see what is new: today's insider filings, this week's congressional disclosures, the latest lobbying registrations. Not available for snapshot-only bulk datasets (patents); use trackers_query there.","read_only":true},{"name":"trackers_ticker","title":"Ticker across Market Trackers","description":"One ticker across every ticker-bearing Market Trackers dataset for one year (default: the current year): insider transactions, congressional trades, 13F holdings, federal contracts and grants, lobbying filings by the company, short-sale volume, clinical trials, FDA events, patents, Wikipedia pageviews. Returns per-dataset match counts with the newest rows of each — a public-record dossier from pri","read_only":true},{"name":"edge_symbols","title":"Hosted Edge Stats coverage","description":"What the hosted Edge Stats store covers: the symbols, their session calendars, coverage windows, session counts, and when the nightly build last ran. Session statistics (how often a setup actually worked, with sample sizes and confidence intervals) come from the open-source edge-stats engine over free market data. Start here, then edge_presets for the questions you can ask, then edge_report for a ","read_only":true},{"name":"edge_presets","title":"List Edge Stats report presets","description":"The catalog of session-statistics questions the hosted store precomputes nightly — gap fills, opening-range breakouts, day-of-week effects, event-day behavior, and more. Each preset states in plain language what its number means. Returns preset ids for edge_report.","read_only":true},{"name":"edge_report","title":"Get a hosted Edge Stats report","description":"One precomputed session-statistics result: P(outcome | conditions) for a preset on a hosted symbol, in the engine's full honesty envelope — the estimate with N and a Wilson 95% confidence interval, minimum-sample guards, a first-half vs second-half stability split, per-year counts, the value distribution where the outcome is continuous, and the disclaimer. Historical conditional frequencies, not p","read_only":true},{"name":"luxalgo_account","title":"My LuxAlgo account","description":"The signed-in user's LuxAlgo account: plan tier, entitlements (limits such as alerts, historical bars, AI credits) and profile basics. Use it to tailor answers to what the user's plan actually allows, or when the user asks what plan they are on. Requires signing in with a LuxAlgo account (OAuth).","read_only":true},{"name":"journal_list_accounts","title":"List journal accounts","description":"The signed-in user's trade-journal accounts — id, name, broker, kind (`sync` mirrors a live broker connection, `import` came from statements, `manual` is hand-entered), currency, initial balance, P&L lot method, last broker sync, archived state — plus `timeZone`, the journal timezone every date in the journal tools is expressed in. Call this first: every other journal tool's `accounts` filter take","read_only":true},{"name":"journal_overview","title":"Journal dashboard","description":"The journal dashboard in one call for a window: performance metrics (net/gross P&L, fees, win rate, day win rate, profit factor, expectancy, average win/loss and their ratio, largest win/loss, streaks, max drawdown, recovery factor, profit concentration, average realized R), the Edge Score with its six components, per-day P&L stats, the cumulative equity curve, open positions, and the accounts and","read_only":true},{"name":"journal_calendar","title":"Journal P&L calendar","description":"One month of the P&L calendar: week rows of day cells (net and gross P&L, fees, trade/win/loss/breakeven counts, volume; null for days with no trades), each week's net P&L and trade count, and the month's net P&L, trade count, trading days and winning days. Days are in the journal timezone. Omit `month` for the current month. Drill into one day with journal_get_day. Requires signing in with a LuxA","read_only":true},{"name":"journal_breakdown","title":"Journal P&L breakdown","description":"Where the P&L actually comes from: closed trades in the window grouped nine ways — weekday, time of day, hold time, symbol, side, position size, tag, rating and asset class — each group with trade count, wins, losses, net P&L, average net P&L and win rate (breakevens excluded). Defaults to all time, since groups need sample size; narrow with `range` or `from`/`to`. The tool for 'what am I good or ","read_only":true},{"name":"journal_list_trades","title":"List journal trades","description":"Trade summaries — `key`, account, symbol, asset class, direction, status (open/win/loss/breakeven), open and close times, quantity and open quantity, average entry/exit, gross and net P&L, fees, fill count, duration, realized R, tags, rating, reviewed flag, hasNotes — newest-opened first by default. `sort` orders by any of openedAt, closedAt, netPnl, grossPnl, durationMs, quantity, symbol or ratin","read_only":true},{"name":"journal_get_trade","title":"Get one journal trade","description":"One trade in full: the summary fields plus its fills (each with the effective values, what the source reported, the user's corrections and whether it is hidden), per-exit gross P&L, hidden fills inside the trade's span, and every annotation — notes, tags, mistakes, playbook id, stop loss, profit target, review time. Use after journal_list_trades or journal_get_day when the user asks about a specif","read_only":true},{"name":"journal_get_day","title":"Get one journal day","description":"A single trading day: its stats (null when nothing traded), its trades (closed that day, or opened that day and still open) as summaries, and the day's notes with their ids. `date` is a YYYY-MM-DD day key in the journal timezone. Use it for 'how did Tuesday go', and to find note ids for journal_update_note. Requires signing in with a LuxAlgo account (OAuth).","read_only":true},{"name":"journal_list_tags","title":"List journal tags, mistakes and playbooks","description":"The user's annotation vocabulary: every tag, mistake and playbook id they have put on any trade (open or closed), most-used first with the number of trades carrying each. Check it before journal_update_trade so new annotations reuse the user's own words instead of minting near-duplicates. Per-trade tags are on each trade summary, not here. Requires signing in with a LuxAlgo account (OAuth).","read_only":true},{"name":"journal_search_notes","title":"Search journal notes","description":"Search the notes feed — day notes and trades that carry notes — newest first as one stream split by kind: `notes` (day notes, with ids for journal_update_note) and `tradeNotes` (the trade summary with its note text; annotate via journal_update_trade). Filter by case-insensitive text (`q`), day-key window, symbol (trade notes only — day notes have no symbol and drop out) and account ids; keyset-pag","read_only":true},{"name":"journal_add_trade","title":"Log a trade by hand","description":"Log a trade by adding its fills to a `manual` or `import` journal account (never a broker-synced one — the sync owns those). The journal derives trades from fills: a long round trip is a buy fill then a sell fill, a short is sell then buy, scale-ins and partial exits are just more fills, and a lone fill opens a position. Times are ISO 8601 instants with offset; fees are per fill. Fills identical t","read_only":false},{"name":"journal_update_trade","title":"Annotate a journal trade","description":"Annotate a trade — the user-owned fields only: `notes` (free text about this trade), `tags`, `mistakes`, `playbookId`, `rating` 1–5, `stopLoss` and `profitTarget` (price levels; the stop is what realized R is measured against) and `reviewed`. `tags`/`mistakes` replace the whole list; use `addTags`/`removeTags`/`addMistakes`/`removeMistakes` to change a few entries without clobbering the rest (chec","read_only":false},{"name":"journal_write_note","title":"Write a journal note","description":"Add a new note to a trading day — any day, traded or not; `date` is YYYY-MM-DD in the journal timezone. Days hold any number of notes, so this never overwrites: to change an existing note use journal_update_note, and for a note about one specific trade use journal_update_trade's `notes`. Returns the note with its id. Day notes in the LuxAlgo journal: https://docs.luxalgo.com/platform/workspaces/jo","read_only":false},{"name":"journal_update_note","title":"Update a journal note","description":"Replace a day note's text and/or move it to another day, by note id (from journal_get_day or journal_search_notes). The body is replaced whole — to append, read the current text first and send the full new version. Trade notes are edited with journal_update_trade, not here. Returns the updated note. Day notes in the LuxAlgo journal: https://docs.luxalgo.com/platform/workspaces/journal/notes Requir","read_only":false},{"name":"chart_open","title":"Vela chart","description":"Shows an interactive live chart from Vela, our next-generation charting platform, inside the chat: crypto candles streamed from Hyperliquid or Binance in the user's browser, with optional native indicators, horizontal levels, shaded zones and a date range. Use it when the user wants to see or discuss a crypto market visually. Returns a chart_id; change or read the open chart afterwards with chart_","read_only":true},{"name":"chart_command","title":"Vela chart change","description":"Edits or reads a chart already open in the chat (from chart_open): switch market or timeframe, add or remove a native indicator, draw a level or a zone, clear drawings, or zoom to a date range; {op: \"read\"} changes nothing and returns what the chart shows now. Ops apply in order. Usually waits a few seconds for the chart to confirm and returns what it shows, in words, with the numbers the user see","read_only":true},{"name":"chart_sync","title":"Chart view sync","description":"Used by the chart view itself, not by the model: acknowledges applied changes, reports the chart's state in words and fetches pending changes.","read_only":true},{"name":"watchlists_list","title":"My watchlists","description":"The signed-in member's watchlists, the same lists Vela shows on the web and in the Vela apps: each list's id and name with every symbol in it, as the market it streams (source:TICKER), its category and section, and a Vela chart link (chart_url). Use it to answer what the member watches, and before watchlists_add_symbols or watchlists_remove_symbols to get a list's id. It carries no prices. An empt","read_only":true},{"name":"watchlists_create","title":"Create a watchlist","description":"Creates a new watchlist in the signed-in member's account, optionally with its first symbols; it shows up in Vela on the web and in the Vela apps. Use watchlists_add_symbols to add to a list that exists. How many watchlists and symbols per list the member may have comes from their LuxAlgo plan: at a limit the call answers with the limit and where to upgrade, and nothing is saved. It changes the me","read_only":false},{"name":"watchlists_add_symbols","title":"Add to a watchlist","description":"Adds markets to one of the signed-in member's watchlists (its id from watchlists_list), at the end of the list or in a named section; a market already in the list is left as it is. Returns the list as saved, in words, with a Vela chart link per added market. How many watchlists and symbols per list the member may have comes from their LuxAlgo plan: at a limit the call answers with the limit and wh","read_only":false},{"name":"watchlists_remove_symbols","title":"Remove from a watchlist","description":"Removes markets from one of the signed-in member's watchlists (its id from watchlists_list). Name each one as watchlists_list shows it (source:TICKER) or by its bare symbol (\"AAPL\", \"BTCUSD\"), which removes every row of that symbol. The list itself stays; this server cannot delete a watchlist. Returns what was removed and what was not found. It changes the member's account, so the chat app may ask","read_only":false},{"name":"layouts_list","title":"My saved Vela layouts","description":"The signed-in member's saved Vela layouts (workspaces), newest first: each one's name, id, when it was last saved, whether it has a share link, and its Vela link (chart_url) that opens that layout. Use it when the member asks for their saved charts or layouts or wants one opened. Read only: it cannot save, rename, share or delete a layout. For a single market on a chart, give that market's chart_u","read_only":true},{"name":"alerts_list","title":"My alerts","description":"The signed-in member's LuxAlgo Alerts, Price Alerts and Custom Alerts, as Vela shows them: each alert's id, name, market, what it waits for (a Price Alert's level is the member's own), how often it fires, whether it is on, paused, fired or held back, whether it notifies anyone, and a Vela chart link for its market; plus how many of each kind are on against what the member's plan allows. Use it to ","read_only":true},{"name":"alerts_create_price","title":"Create a Price Alert","description":"Creates a Price Alert in the signed-in member's account: it fires when a market's price crosses, crosses above, crosses below, is above or is below a level the member chose, as often as `frequency` says. It notifies the member in-app (Vela on the web and on their phone) when the account has that channel; the result says plainly which channel it notifies, or that it notifies no one. With `chart_id`","read_only":false},{"name":"alerts_create_custom","title":"Create a Custom Alert","description":"Creates a Custom Alert in the signed-in member's account from an indicator's condition on one market and timeframe: either a Vela built-in indicator (`indicator`: RSI crosses above 70, MACD crosses above its signal line, price crosses below the lower Bollinger Band…) or an open-source LuxAlgo Library indicator (`library`: its slug, from library_search, firing on one of its alert conditions or on i","read_only":false},{"name":"alerts_pause","title":"Pause an alert","description":"Pauses one of the signed-in member's alerts (Price Alert or Custom Alert, its id from alerts_list): it stays saved and stops firing until alerts_resume. Returns the alert in words. It changes the member's account, so the chat app may ask the user to confirm first. Requires signing in with a LuxAlgo account (OAuth).","read_only":false},{"name":"alerts_resume","title":"Turn an alert back on","description":"Turns one of the signed-in member's alerts back on (paused, fired, expired or held back by the plan; its id from alerts_list). Returns the alert in words. How many alerts the member may have on comes from their LuxAlgo plan: at a limit the call answers with the limit and where to upgrade, and nothing is created. It changes the member's account, so the chat app may ask the user to confirm first. Re","read_only":false},{"name":"alerts_history","title":"Alert history","description":"When the signed-in member's alerts fired, newest first (kept 90 days): the alert, the market, the time, and whether each notification was delivered; the price it fired at only for crypto markets fed by an exchange's public feed (Hyperliquid, Binance). Optionally for one alert (`alert_id`). Paged with `cursor`. Use alerts_list for the alerts themselves. Requires signing in with a LuxAlgo account (O","read_only":true},{"name":"chart_peek","title":"See my open Vela chart","description":"A picture of the chart the signed-in member has open right now in Vela, our next-generation charting platform, in their browser, as they see it, with the market, timeframe and indicators in words and a Vela link (chart_url). Use it when the member asks about the chart they have open in Vela (\"look at my chart\", \"what do you see here?\"). To show a market inside the chat instead, use chart_open. Wor","read_only":true},{"name":"quant_generate_pine_script","title":"Write Pine Script® with Quant","description":"Has Quant, our coding agent, write a Pine Script® v6 indicator or strategy from a prompt, or change one in place: the script passed as `code`, or one of the member's saved scripts by its `script_id` (the result then has a unified diff). Quant works in the background with the Pine Script® reference, checks every attempt with LuxAlgo's linter and fixes what fails, until the script passes or its time","read_only":false},{"name":"quant_validate_pine_script","title":"Check Pine Script® with LuxAlgo's linter","description":"Checks a Pine Script® source with LuxAlgo's linter, the one Quant checks its own scripts with: whether it is valid (no errors), every error and warning with its code, message and position (1-based line and column), and what the script declares (indicator, strategy or library, its title, Pine version and overlay). It reads the source only: nothing runs, nothing is saved, and it uses no Quant usage.","read_only":true},{"name":"quant_search_user_scripts","title":"Search my scripts","description":"Searches the signed-in member's own Pine Script® scripts on LuxAlgo: the ones Quant wrote for them in a chat (`origin: quant`) and the ones they saved from the code editor (`origin: user`). Each result has its id, name, kind (indicator, strategy or library), origin, a one-line description when there is one, and when it was created and last saved; newest first. `query` matches names and description","read_only":true},{"name":"get_user_script","title":"Get one of my scripts","description":"The full Pine Script® source of one of the signed-in member's own scripts, by its id from quant_search_user_scripts, with its name, kind and origin. Kept apart from the search because sources are long: call it only when the code itself is needed, for example to change it with quant_generate_pine_script or check it with quant_validate_pine_script. It reads only the member's own scripts; for a LuxAl","read_only":true},{"name":"quant_plan_backtest_loop","title":"Plan a backtest loop","description":"Turns a prompt into the plan of a backtest loop and returns it with a plan_id; it starts nothing. A backtest loop is an autonomous run in which Quant, our coding agent, writes and backtests Pine Script® strategy versions until enough of them meet the plan's criteria. Quant writes the plan: the markets and timeframes, the tested date range and how much of it is held out, costs, order size, how many","read_only":false},{"name":"quant_start_backtest_loop","title":"Start a backtest loop","description":"Starts the backtest loop of a plan the member approved, by the plan_id quant_plan_backtest_loop returned, and returns its loop id. A backtest loop is an autonomous run in which Quant, our coding agent, writes and backtests Pine Script® strategy versions until enough of them meet the plan's criteria. Call it only after you showed the member that plan and they said yes in their own words; never star","read_only":false},{"name":"quant_stop_backtest_loop","title":"Stop a backtest loop","description":"Stops one of the member's backtest loops by its id: it finishes the attempt it is on, stops spending Quant usage, and keeps every strategy it found and tested. A stopped loop is not lost: the member can resume it from its Loop Report in Vela, where it picks up after its last attempt. A loop that already ended is left as it is, and the result says so. It never deletes a loop or its strategies. Requ","read_only":false},{"name":"quant_list_backtest_loops","title":"List my backtest loops","description":"The signed-in member's backtest loops, newest first: each one's id, status, whether it is active (`active` is true while it is running or waiting for more Quant usage), its markets, how many strategies it found against how many the plan asked for, its attempts, the time it has used against its limit, when it started and ended, and its report_url. `active: true` lists only the ones still going; `ac","read_only":true},{"name":"quant_get_backtest_loop_info","title":"Get a backtest loop's status and strategies","description":"Where one of the member's backtest loops stands, by its id: its status and whether it is still active, why it stopped when it did, Quant's closing summary once it ended, its markets, how many strategies it found against how many the plan asked for, its attempts and the time it has used against its limit, its report_url, and what it found so far: `strategies`, its best ones (10 at most) with each o","read_only":true},{"name":"quant_get_backtest_loop_strategy","title":"Get a strategy a backtest loop found","description":"One strategy of one of the member's backtest loops, by its id from quant_get_backtest_loop_info (`best_strategy_id`, or an id in `strategies`): whether it meets every criterion, what it does and how it trades in Quant's words, its Pine Script® source as it goes on a chart, and each market's backtest on the data it was developed on (`in_sample`) and on the data held out from it (`out_of_sample`): t","read_only":true},{"name":"vela_read_chart","title":"Read my open Vela chart","description":"What the signed-in member has open right now in Vela, our next-generation charting platform, in their browser, in words: the layout, and for each chart its market, timeframe, chart type, indicators, the dates on screen and its clock. Each indicator comes with the id vela_remove_indicators takes, and one that is a saved script of the member's also with its script_id, which quant_generate_pine_scrip","read_only":true},{"name":"vela_set_chart","title":"Change my open Vela chart","description":"Changes the chart the signed-in member has open right now in Vela, in their browser: the market (symbol), the timeframe, the chart type, the trading session, the price scale, the dates on screen, and the multi-chart layout. Send only what should change; everything else on the chart stays, and it never adds or removes an indicator or a drawing (vela_add_indicator and vela_remove_indicators do the f","read_only":false},{"name":"vela_mark_up_chart","title":"Mark up my open Vela chart","description":"Marks up the chart the signed-in member has open right now in Vela the way a professional discretionary trader would, from the chart's own candles: fair value gaps, buyside and sellside liquidity and equal highs and lows, market structure (BOS and MSS), order blocks and breakers, the dealing range with premium, discount and OTE, opening gaps, ICT killzones and macros, key levels (previous day and ","read_only":false},{"name":"vela_draw_on_chart","title":"Draw on my open Vela chart","description":"Draws on the chart the signed-in member has open right now in Vela, at times and prices you give: horizontal levels, shaded zones, trendlines, projection paths with an arrowhead, channels, Fibonacci retracements, text notes, vertical time lines and long or short positions with a stop and a target. Use it to put a plan, a scenario or a target on the member's own chart; for levels and concepts the c","read_only":false},{"name":"vela_remove_drawings","title":"Remove drawings from my open Vela chart","description":"Removes drawings an assistant or Quant, our coding agent, made on the chart the signed-in member has open right now in Vela: the groups named (a group vela_mark_up_chart or vela_draw_on_chart returned), or all of them. It never touches the member's own drawings. Use it to clear an analysis before drawing a new one, or when the member asks to clean up what was drawn for them. With the member's Vela","read_only":false},{"name":"vela_add_indicator","title":"Add an indicator to my open Vela chart","description":"Adds an indicator that already exists to the chart the signed-in member has open right now in Vela: one from the LuxAlgo Library, the largest indicator library in trading, by its slug (library_search and library_get_indicator return it), or one of the member's own saved scripts, by its id (quant_search_user_scripts returns it). Give exactly one of the two. Use it when the member asks to put an ind","read_only":false},{"name":"vela_remove_indicators","title":"Remove indicators from my open Vela chart","description":"Takes indicators off the chart the signed-in member has open right now in Vela, by id: the id vela_read_chart gives each indicator on that chart, or the id vela_add_indicator returned. Read the chart first when you do not have the id; never make one up. Use it when the member asks to take an indicator off or to clean up their chart, and to make room when their plan's tools per chart is reached. It","read_only":false},{"name":"vela_get_indicator_settings","title":"Read an indicator's settings on my open Vela chart","description":"The settings of one indicator on the chart the signed-in member has open right now in Vela, as its settings dialog shows them: each setting's name, its kind (a number, on/off, a choice, a colour, a source, a timeframe), the value it holds now and what it may hold (minimum, maximum, step, or the choices). Use it before vela_set_indicator_settings, to learn the names and what each accepts, and when ","read_only":true},{"name":"vela_set_indicator_settings","title":"Change an indicator's settings on my open Vela chart","description":"Changes settings of one indicator on the chart the signed-in member has open right now in Vela, as its settings dialog would: a length, a source, a mode, a toggle, a colour. Name the indicator by the id vela_read_chart gives it and each setting by the name vela_get_indicator_settings lists; read the settings first rather than guessing names. Use it when the member asks to tune an indicator on thei","read_only":false}],"server_info":{"name":"luxalgo","version":"2.1.0"},"category":"web-search","tags":["productivity","agents","data"],"kind":"remote","source":"registry","submitted":{},"first_party":false,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-08-12","stars":0,"badges":[],"sponsor":null,"page":"https://agentsindex.org/agents/io-github-luxalgo-luxalgo-mcp-server/"}