LuxAlgo is a remote MCP server that gives an AI agent 42 tools, among them edge_presets, edge_report, edge_symbols. It answers at https://mcp.luxalgo.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 20 October 2026, succeeded.
LuxAlgo for AI agents: the Library, prop firms, Market Trackers, Edge Stats, and your Trade Journal
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
edge_presets | 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 pr Inputs: category, context |
edge_report | 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 sec Inputs: preset, symbol, context |
edge_symbols | 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 in Inputs: context |
journal_add_trade | 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, Inputs: accountId, fills, context |
journal_breakdown | 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 Inputs: range, from, to, accounts, context |
journal_calendar | 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 Inputs: month, accounts, context |
journal_get_day | 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 Inputs: date, accounts, context |
journal_get_trade | 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 Inputs: key, context |
journal_list_accounts | 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 s Inputs: context |
journal_list_tags | 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 use Inputs: accounts, context |
journal_list_trades | 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, ratin Inputs: accounts, from, to, symbol, direction, status |
journal_overview | 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 Inputs: range, from, to, accounts, compare, context |
journal_search_notes | 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_upd Inputs: q, from, to, symbol, accounts, limit |
journal_update_note | 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 wi Inputs: noteId, body, date, context |
journal_update_trade | 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 Inputs: key, notes, tags, addTags, removeTags, mistakes |
journal_write_note | 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 sp Inputs: date, body, context |
library_get_concept | 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 librar Inputs: slug, context |
library_get_family | 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'. Inputs: key, context |
library_get_indicator | 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 indicato Inputs: slug, context |
library_get_source_code | The full, working source code of a Library indicator (works on TradingView). Kept separate from library_get_indicator because sources are long — call it only when the user wants the code itself. Inputs: slug, context |
library_list_concepts | 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; for keyword lookup prefer library_search. Inputs: family, page, page_size, context |
library_list_families | 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. Inputs: context |
library_list_indicators | Browse the indicator catalog with filters and server-side sorting (newest first by default). Filter by family, concept slug (implementations of one concept), tags (ids from library_list_tags, AND-combined), trading platform, or plan tier. U Inputs: family, text, concept, tags, platform, tier |
library_list_tags | The Library's indicator tag vocabulary (behavioral traits like 'Volatility', 'Trailing-Stop', 'Repainting Functionality'). Returns ids to pass as the tags filter of library_list_indicators — tags are orthogonal to the concept-family taxonom Inputs: context |
library_search | 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, in Inputs: query, type, family, limit, context |
luxalgo_account | 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 ar Inputs: context |
propfirms_challenge_rules | 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 wit Inputs: firmId, challengeId, context |
propfirms_compare | 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 |
propfirms_get | 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 Inputs: propfirmId, context |
propfirms_list_simulatable | 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 Inputs: productType, context |
propfirms_optimal_risk | 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 e |
propfirms_pass_rates | 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 Inputs: firmId, challengeId, context |
propfirms_search | 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 (accoun Inputs: text, propfirmId, productTypes, tradedMarketTypes, tradingPlatforms, isPreferredPartner |
propfirms_search_challenges | 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 Inputs: text, challengeId, challengeName, accountSizeMin, accountSizeMax, steps |
propfirms_search_offers | 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 Inputs: text, propfirmId, challengeId, offerId, promoCode, offerText |
propfirms_simulate | 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 mo |
propfirms_simulate_trades | 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 THIS BEATS WIN-RATE MATH: challenge rules are breached by streaks, not by averages - a daily-loss |
propfirms_validate_strategy | 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 spli Inputs: winRate, avgWinR, avgLossR, winStdR, lossStdR, tradesPerDay |
trackers_datasets | 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, Inputs: dataset, context |
trackers_latest | 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 disc Inputs: dataset, ticker, text, where, sort, limit |
trackers_query, trackers_ticker
Every block below points at https://mcp.luxalgo.com/mcp. Pick your client and copy.
claude mcp add --transport http luxalgo https://mcp.luxalgo.com/mcp
{
"mcpServers": {
"luxalgo": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.luxalgo.com/mcp"]
}
}
}{
"mcpServers": {
"luxalgo": {
"url": "https://mcp.luxalgo.com/mcp"
}
}
}{
"servers": {
"luxalgo": {
"type": "http",
"url": "https://mcp.luxalgo.com/mcp"
}
}
}{
"context_servers": {
"luxalgo": {
"url": "https://mcp.luxalgo.com/mcp"
}
}
}{
"mcpServers": {
"luxalgo": {
"serverUrl": "https://mcp.luxalgo.com/mcp"
}
}
}{
"mcpServers": {
"luxalgo": {
"url": "https://mcp.luxalgo.com/mcp"
}
}
}name: LuxAlgo
version: 0.0.1
schema: v1
mcpServers:
- name: LuxAlgo
type: streamable-http
url: https://mcp.luxalgo.com/mcp{
"mcpServers": {
"luxalgo": {
"httpUrl": "https://mcp.luxalgo.com/mcp"
}
}
}{
"mcpServers": {
"luxalgo": {
"type": "http",
"url": "https://mcp.luxalgo.com/mcp"
}
}
}{
"mcpServers": {
"luxalgo": {
"url": "https://mcp.luxalgo.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.luxalgo.com%2Fmcp&type=streamable_http&id=luxalgo&name=LuxAlgo
It answered our last check on 20 October 2026 in 162 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
42, as returned by the server's own tools/list on 12 September 2026: edge_presets, edge_report, edge_symbols, journal_add_trade, journal_breakdown, journal_calendar, journal_get_day, journal_get_trade, and 34 more.
It answered our last check on 20 October 2026 in 162 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.luxalgo.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.luxalgo. Endpoint host: mcp.luxalgo.com. ARD identifier: urn:air:io.github.luxalgo:mcp:luxalgo-mcp-server.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.