LuxAlgo MCP
v2.1.0LuxAlgo for AI agents: the Library, prop firms, Market Trackers, Edge Stats, and your Trade Journal
Endpoint health
online- Last checked
- 11/20/2026, 4:17:29 AM
- Latency
- 131 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:io.github.LuxAlgo%2Fluxalgo-mcp-server
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"io.github.LuxAlgo/luxalgo-mcp-server": {
"url": "https://mcp.luxalgo.com/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
25 shown · authentication unknown
My alerts
alerts_list
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 answer what alerts the member has and to get an id for alerts_pause, alerts_resume or alerts_history. Requires signing in with a LuxAlgo account (OAuth).
Schema valid · SHA-256 f78ab961530b…
View input schema
{ "type": "object", "properties": { "type": { "description": "Only Price Alerts or only Custom Alerts.", "type": "string", "enum": [ "price", "custom" ] }, "status": { "description": "Only alerts in this state.", "type": "string", "enum": [ "active", "paused", "triggered", "expired", "suspended_plan", "error" ] }, "context": { "type": "string", "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"" } }, "required": [ "context" ], "$schema": "https://json-schema.org/draft/2020-12/schema" }Vela chart change
chart_command
Connections
streamable-http
https://mcp.luxalgo.com/mcp