LuxAlgo Library — the encyclopedia of trading & technical analysis for AI agents. Free, keyless.
io.github.LuxAlgo/luxalgo-mcp-server (MCP Server)
The LuxAlgo MCP server (“io.github.LuxAlgo/luxalgo-mcp-server”) provides the LuxAlgo Library—an encyclopedia of trading & technical analysis intended for AI agents. It is described as free and keyless, with 8 available tools.
🛠️ Key Features
LuxAlgo Library focused on trading and technical analysis
Free, keyless access
8 tools
🚀 Use Cases
Supplying trading/technical analysis knowledge to AI agents
Supporting research workflows involving finance and technical indicators
Running Monte Carlo–related exploration based on provided topics
⚡ Developer Benefits
MCP-compatible server for agent integrations
Tagged for knowledge-base, research, and trading contexts
Repository topics include “mcp” and “mcp-server” for discoverability
⚠️ Limitations
Limited details provided beyond description, tools count (8), and topics; specific tool capabilities are not included in the excerpt.
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.
Parameters4
query
string
required
A concept, indicator name, alias, or topic — e.g. 'order blocks', 'mean reversion', 'stochastics'
type
string
optional
Limit to 'concepts' (explanations) or 'indicators' (implementations); default all
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.
Parameters1
slug
string
required
Exact concept slug, e.g. 'rsi' or 'order-blocks' — from search or list results
Raw schema
{
"type": "object",
"properties": {
"slug": {
"type": "string",
"minLength": 1,
"description": "Exact concept slug, e.g. 'rsi' or 'order-blocks' — from search or list results"
}
},
"required": [
"slug"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
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 indicator.
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.
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.
Browse the indicator catalog with filters and server-side sorting (newest first by default). Use for structured browsing — 'latest indicators', 'everything in the volatility family'; for keyword discovery prefer library_search.
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.
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'.
It puts the LuxAlgo ecosystem behind a single MCP server: an encyclopedia of trading and technical analysis, read-only access to your own brokerage accounts, hosted session statistics with a sample size on every number, the public record of US markets (congressional trades, insider filings, lobbying, contracts, patents and more, with a primary-source link on every row), a Monte Carlo challenge simulator, and a live prop-firm directory. Free and read-only. No API key for anything hosted; the local broker tools use your own keys and never send them anywhere.
bash
claude mcp add --transport http luxalgo https://mcp.luxalgo.com/mcp
The encyclopedia of trading and technical analysis: hundreds of concept pages with formulas, the full indicator catalog with families and tags, and Pine Script sources where publicly served.
Trade Journal (sign-in)
Your own journal in the LuxAlgo app: the dashboard (metrics, Edge Score, equity curve), the P&L calendar, breakdowns by weekday / hold time / symbol / tag and more, every trade with its fills and annotations, day notes — and the writes that keep it alive: log fills by hand, annotate trades (tags, mistakes, rating, stop and target, review), write notes. Always as you, on your data; the app owns the rules.
Brokers (local only)
Read-only access to your own accounts across 22 brokers and exchanges via broker-sdk: balances, positions, trade history, FIFO performance stats. Keys live in your MCP client config as env vars and never leave your machine. The hosted endpoint does not carry these tools, on purpose.
Edge Stats
Hosted session statistics from the open-source edge-stats engine: how often a setup actually worked (gap fills, opening-range breakouts, day-of-week effects, event days) with the sample size and a Wilson 95% confidence interval on every number. A nightly build runs the real engine over free market data and publishes only derived statistics; these tools serve them verbatim.
The public record of US markets from primary sources only: 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 Reserve communications, committee assignments, Wikipedia pageviews. Read straight from the pipeline's CC0 dumps — live tree plus deep-history archives — with provenance.sourceUrl on every row. Data only: no signals, scores, or predictions.
Challenge Simulator
The open-source prop-firm-sim Monte Carlo engine, running locally inside the server. Your stats, or your real R-multiple trade series, through a firm's exact ruleset: pass probability with confidence intervals, expected attempts and cost, EV over the funded horizon, optimal-risk sweeps, cross-challenge comparison. Deterministic under seed, every assumption disclosed.
Prop Firm Directory
The live data the simulator draws from: firms, funded-account challenges with their full rulebooks (account sizes, fees, steps, profit splits, drawdown modes, trading restrictions), and current offers.
Charts (your browser)
Not a tool: the chart you draw with what the tools return. Vela, LuxAlgo's open-source charting engine, runs the Pine Script that library_get_source_code hands back and paints the fills that broker_trades lists, in a browser tab, on your machine. How the loop works.
Install
The hosted server is one URL:
code
https://mcp.luxalgo.com/mcp
Claude (web, desktop, mobile)
Customize → Connectors → Add custom connector, URL https://mcp.luxalgo.com/mcp, keep the detected defaults (Always required, Use Anthropic's hosted client metadata) and click Add, then Connect and sign in with your LuxAlgo account. Anthropic documents lazy authentication — connect anonymously, sign in only when a protected tool is called — as the intended behaviour with Required when the server asks, but as of September 2026 Claude.ai still opens the OAuth window at connect time for this server (it fetches /.well-known/oauth-protected-resource itself after the anonymous handshake). Every tool, keyless or not, works once connected; the anonymous-until-needed flow is available in the other clients.
Claude Code
bash
claude mcp add --transport http luxalgo https://mcp.luxalgo.com/mcp
Cursor
Use the Install in Cursor button above, or add this to .cursor/mcp.json:
Runs every hosted tool locally, and unlocks the broker tools. Set read-only credential env vars for the brokers you use. Any subset works: a broker connects when all of its vars are set, and with no vars at all the broker tools simply stay unconfigured.
Env var names derive from each broker's credential fields: BROKERS_<BROKER>_<FIELD> (for example BROKERS_OKX_PASSPHRASE, BROKERS_IBKR_FLEX_FLEX_TOKEN). The broker_setup tool lists every supported broker, its exact variables, and a one-line guide to creating each key with read-only scope, which is all this server ever needs.
Signing in with LuxAlgo (optional)
Almost everything here is keyless and works without an account. The tools in the Account and Trade Journal sections below need to know who you are; they use your LuxAlgo account through standard OAuth 2.1, with app.luxalgo.com as the authorization server. Nothing is required up front: every client can connect, list tools and use the public ones anonymously, and sign-in is only requested when you first call an account tool.
Hosted (ChatGPT, Claude, Cursor, any remote connector). The server advertises its protected-resource metadata and answers an unauthenticated account-tool call with a 401 + WWW-Authenticate challenge; MCP clients handle the rest (discovery, PKCE, consent screen in your browser) and keep the token for you. Each tool also declares its policy in tools/list (securitySchemes: noauth for public tools, oauth2 for account tools), so ChatGPT's per-tool linking works as well. Clients may identify themselves via Client ID Metadata Documents or Dynamic Client Registration — the app accepts both. One client-side exception: Claude.ai/Desktop connectors sign in at connect time whenever OAuth metadata is discoverable, regardless of their Authentication setting (see Install); ChatGPT, Cursor, Claude Code and the stdio server get the anonymous-until-needed flow.
Local (stdio). The server running on your machine is itself the OAuth client. Sign in once:
bash
npx -y @luxalgo/mcp login # opens your browser; tokens are stored under your user config dir (0600)
npx -y @luxalgo/mcp status # who is signed in, token expiry
npx -y @luxalgo/mcp logout
Tokens live in ~/.config/luxalgo/mcp-auth.json (%APPDATA%\luxalgo\mcp-auth.json on Windows, or LUXALGO_MCP_AUTH_FILE), are refreshed automatically, and are only ever sent to the LuxAlgo app. If your MCP client supports URL-mode elicitation (MCP 2026-07-28), you can skip the command: the first account-tool call asks the client to open the sign-in page and continues once you approve. Otherwise the tool answers with the challenge and the login hint.
What the token is for. This server never decides what you are entitled to — its code is public, so any such check would be decorative. Instead, once you are signed in, every request a tool makes to the LuxAlgo app carries your token, and the app resolves your account and plan from it exactly as it does when you use the web app. Public tools work without it; with it, the app can tailor what they return. When the app declines — no valid sign-in (401) or a feature outside your plan (403) — the tool reports that, naming the permission involved.
Tools
Library
Tool
Description
library_search
One search over concepts (alias-aware) and indicators
Library outputs are compact JSON with canonical urls for citation. Concept and family pages are also directly fetchable as markdown: append .md to any concept URL.
Account (sign-in required)
Tool
Description
luxalgo_account
The signed-in user's plan tier, entitlements (alerts, historical bars, AI credits, …) and profile basics — so an agent can tailor answers to what the plan actually allows
Trade Journal (sign-in required)
Your own trade journal in the LuxAlgo app — the same accounts, trades, annotations and notes the app shows — read and written as you. Dates are YYYY-MM-DD day keys in your journal timezone (journal_list_accounts reports it); account filters take ids from the same call.
Tool
Description
journal_list_accounts
Journal accounts (broker-synced, imported or manual; currency, initial balance, lot method, last sync, archived state) and the journal timezone — the first call, since every accounts filter takes these ids
journal_overview
The dashboard for a window: performance metrics, Edge Score, per-day P&L, equity curve, open positions, accounts and settings; compare adds the previous equal-length window
journal_calendar
One month of the P&L calendar: day cells, weekly and monthly totals, trading and winning days
journal_breakdown
Closed trades grouped by weekday, time of day, hold time, symbol, side, position size, tag, rating and asset class — where the P&L comes from
journal_list_trades
Trade summaries, keyset-paginated; filter by accounts, open-day window, symbol, direction, status, tag; sort by opened/closed time, net or gross P&L, duration, quantity, symbol or rating, either direction
journal_get_trade
One trade in full: fills (reported values, corrections, hidden), per-exit P&L, every annotation
journal_get_day
A single day's stats, trades and notes
journal_list_tags
The user's annotation vocabulary — tags, mistakes, playbooks with usage counts — so new annotations reuse existing words
journal_search_notes
Day notes and trade notes as one newest-first stream; text query, day window, symbol and account filters, paginated
journal_add_trade
Log a trade by hand: its fills into a manual or import account; returns the resulting trade(s)
journal_update_trade
Annotate a trade: notes, tags (replace or add/remove), mistakes, playbook, rating, stop loss, profit target, reviewed
journal_write_note
Add a note to a day
journal_update_note
Replace a day note's text or move it to another day
The journal tools and luxalgo_account are the only tools that need a LuxAlgo account; see Signing in with LuxAlgo. Without a sign-in they return an OAuth challenge instead of data — never a silent fallback. The write tools act only as the signed-in user and only on that user's journal; the app validates and owns every change.
Brokers (local stdio only)
Tool
Description
broker_setup
Supported brokers, their env vars (set or unset, never values), read-only key guides
Open positions with market values, asset class, entry price; negative quantity means short
broker_trades
Trade history, newest first; filter by broker or symbol
broker_stats
Total equity, equity by broker, top positions, FIFO win rate and realized PnL
broker_refresh
Bypass the 5-minute cache and re-fetch now
Read-only by construction: the SDK's root export has no trading endpoints, the server never writes secrets anywhere, and per-broker failures are reported alongside results, never silently dropped.
Edge Stats
Hosted session statistics from the open-source edge-stats engine, precomputed nightly:
Tool
Description
edge_symbols
What the hosted store covers: symbols, session calendars, coverage windows, last build
edge_presets
The catalog of precomputed questions, each stating in plain language what its number means
edge_report
One result in the engine's full honesty envelope: estimate, N, Wilson 95% CI, minimum-sample guards, stability split, per-year counts, distribution, disclaimer
Every number arrives with its sample size — the engine has no code path that returns a percentage without one. Results are historical conditional frequencies, never predictions. For arbitrary composed queries or your own market data, run edge-stats locally; its own MCP server exposes the full engine over your local store.
Market Trackers
Tool
Description
trackers_datasets
The catalog: every dataset's row count, freshness, years with data (live vs deep-history archive), ticker-searchability; pass dataset for its field roster, filterable paths, caveats, per-year coverage, source health and dump URLs
trackers_query
Search one dataset by ticker, free text, exact field values (where, dot paths) and event-date range, choosing which years to read; newest/oldest ordering with paging
trackers_latest
The newest daily delta of a dataset (today's insider filings, this week's congressional disclosures), optionally narrowed by ticker or text
trackers_ticker
One ticker across every ticker-bearing dataset for a year: per-dataset counts with the newest rows — a public-record dossier
The data is the CC0 output of LuxAlgo/market-trackers, published daily to LuxAlgo/market-trackers-data: year-sharded gzipped JSON in the repository's live tree, plus deep-history shards attached to the data repo's GitHub Releases and indexed in its archives.json. The server streams shards row by row (never loading a whole file) under a per-call budget of compressed bytes, so a deep-history year (often 30–60 MB compressed) is read one at a time. Amounts disclosed as ranges stay ranges; ticker mappings for contracts, lobbying, trials, FDA events and patents are best-effort against a curated map of public companies; every row keeps its primary-source deep link.
Challenge Simulator
Runs locally inside the server:
Tool
Description
propfirms_list_simulatable
Every simulatable firm and challenge in the live directory, provenance-disclosed
propfirms_challenge_rules
One challenge's full encoded ruleset (drawdown modes, consistency, payout gating, citations), editable and re-simulatable inline
propfirms_simulate
Monte Carlo of your stats (win rate, avg win, trades/day, risk sizing) through a firm's exact ruleset and funded horizon: pass probability with CI, which rule kills attempts, expected attempts and cost, EV, payout probability
propfirms_simulate_trades
Same, from your real R-multiple trade series; block bootstrap preserves your streaks
propfirms_optimal_risk
Risk sweep: pass-optimal vs EV-optimal risk per trade (they differ)
propfirms_compare
Same trader across up to 12 challenges, EV-sorted (not a ranking)
propfirms_pass_rates
The site's reference-archetype odds, recomputed live (seed 42, 10k paths)
propfirms_validate_strategy
Screen one strategy across every simulatable challenge against an explicit pass bar
Every simulation result carries its assumptions, unsimulated-rule flags, seed, and engine version. Results are distributions under stated assumptions, never promises. The engine runs locally; firm rules adapt live from the directory, and inline specs simulate fully offline.
Prop Firm Directory
The live directory the simulator draws from, queryable directly:
Tool
Description
propfirms_search
Search firms; firm filters (platforms, markets, payments, Trustpilot, country availability) compose with nested challenge and offer filters, and include nests matching children
propfirms_get
One firm's full dossier: profile, every challenge, live offers, written overview
propfirms_search_challenges
Search challenges by rules (size, fee, steps, profit split, drawdown, trading restrictions) and parent firm; can attach applicable live offers
propfirms_search_offers
Current discounts and promo codes, resolvable per firm or per challenge
Charts, in your browser, with Vela
Every tool above returns text and JSON. When the answer wants a chart, draw it with Vela (@luxalgo/vela, Apache-2.0), LuxAlgo's open-source charting engine: a headless chart with its own WebGL2 renderer that takes bars you already have, or fetches them from keyless public providers, and runs indicator scripts through pluggable engines. Pine Script lives in the @luxalgo/vela-pinets addon, which is what closes the loop with the Library: library_get_source_code hands an agent an indicator's exact Pine source, and Vela executes that source on a chart.
Not a mockup: the Library's SuperTrend source as returned by library_get_source_code, executed by @luxalgo/vela-pinets on a @luxalgo/vela 0.6 chart and screenshotted in headless Chromium. The bars are a labelled synthetic sample; point data at your own or register a provider for live ones.
The whole demo is two script tags and five lines. source is the source field of a library_get_source_code result:
With a bundler it is the same three calls over import { Vela } from '@luxalgo/vela' and import { PineEngine } from '@luxalgo/vela-pinets'; see Vela's quickstart. The same chart paints your own trades: Trade Journal takes the shape broker_trades returns and draws entries, exits and P&L labels through Vela's native-indicator API, engine-free, in one component you can lift as is.
Where each piece runs. This matters because it is the opposite of how the rest of this server works:
Piece
Where
Notes
Vela
A browser tab on your machine (Canvas 2D or WebGL2).
Never inside this server, hosted or stdio, and never in an MCP response. An agent gets the Pine source and the trades as text; the chart is what you build with them.
Bars
Yours, via data, or Vela's keyless Binance, Coinbase and Hyperliquid providers, fetched by the browser.
This server serves no market data, so a chart needs no LuxAlgo key and makes no LuxAlgo request.
Pine Script
@luxalgo/vela-pinets, which executes the PineTS runtime.
AGPL-3.0, licensed separately from Vela's Apache-2.0 and this server's MIT. Vela itself ships no engine and carries no Pine code.
Attribution
Vela's mark, bottom-left of every chart.
Stays on unless you show equivalent attribution next to the chart; see Vela's NOTICE.
npm install
npm run build
npm start # stdio
npm run start:http # streamable HTTP on :3333/mcp
npm test# smoke suite over stdio (hits live endpoints); --only library,edge for a subset
npm run test:http # the same suite against a running HTTP entry on :3333
npm run test:parity # simulator tools vs upstream package + raw engine
npm run test:trackers # offline checks of the Market Trackers streaming engine
Layout — one directory per concern, one directory per tool domain:
code
src/
index.ts the `luxalgo-mcp` binary → entries/stdio.ts
entries/ stdio.ts (local), node-http.ts (plain Node), hosted.ts (shared by node-http and api/server.ts)
server/ manifest.ts (the list of tool modules; protected / local-only derived from it),
create-server.ts (registration shared by every entry), version.ts (serverInfo)
tools/<domain>/ index.ts exports a ToolModule (name, tool names, protected, localOnly, register);
api.ts wraps the domain's endpoints; the rest is the domain's own
tools/_shared/ result/format helpers and the ToolModule contract
auth/ OAuth: config, gate, verify, metadata, challenge, runtime, protected-tool, local/ (stdio client)
platform/ app-client.ts (the one HTTP client for the LuxAlgo app), analytics.ts
api/server.ts the Vercel function
test/ smoke.mjs runner + smoke/<domain>.mjs suites, parity.mjs, trackers-check.mjs
Adding a tool domain: create src/tools/<domain>/index.ts exporting a ToolModule and list it in src/server/manifest.ts; registration asserts the module registers exactly the tools it declares. Mark tools that need a signed-in user in protectedTools (and register them with registerProtectedTool), and modules that read local credentials with localOnly.
Optional env: LUXALGO_APP_ORIGIN and LUXALGO_SITE_ORIGIN point the server at non-production environments; MARKET_TRACKERS_DUMPS_ORIGIN (default https://raw.githubusercontent.com/LuxAlgo/market-trackers-data/main) and MARKET_TRACKERS_DATA_REPO point the Market Trackers tools at another dumps tree.
OAuth env (see src/auth/config.ts): the authorization server is always LUXALGO_APP_ORIGIN + /api/auth; MCP_RESOURCE (default https://mcp.luxalgo.com/mcp) is this server's resource identifier and token audience — it must equal the app's LUXALGO_MCP_SERVER_RESOURCE. For local end-to-end work: LUXALGO_APP_ORIGIN=http://localhost:3001 MCP_RESOURCE=http://localhost:3333/mcp npm run start:http, with the app running on 3001 and the same MCP_RESOURCE exported for npx -y @luxalgo/mcp login / the stdio server. LUXALGO_AUTH_CHALLENGE=result makes the hosted entries let an anonymous protected call reach the tool (which answers the in-band _meta["mcp/www_authenticate"] challenge) instead of short-circuiting with HTTP 401 — the default; invalid tokens are always a 401. LUXALGO_SECURITY_SCHEMES=off drops the per-tool securitySchemes hint from tools/list (ChatGPT's per-tool linking extension; not part of Anthropic's lazy-auth recipe) so the anonymous surface is indistinguishable from an authless server's — the 401 challenge is unaffected. LUXALGO_REACTIVE_AUTH_ONLY=on hides the well-known PRM paths (404) and serves the metadata at /auth/prm, reachable only via the 401's resource_metadata — a temporary counter-measure for claude.ai starting OAuth at connect time (claude-ai-mcp#1013); see docs/auth.md §5 for the trade-off before enabling. npm test covers the anonymous paths and the advertised securitySchemes on both transports.
Disclaimer
Nothing this server returns is investment advice. Simulation outputs are modeled estimates under stated assumptions, not predictions or guarantees. Verify balances and performance numbers against your broker's own statements, and a prop firm's own page is authoritative for its current rules.
