MCP servers observed by Lowdown
io.github.LuxAlgo/luxalgo-mcp-server MCP server: daily status and tool changes
Answered initialize and tools/list on all 4 checks recorded in the last 30 days (2026-11-09 to 2026-11-18) (Lowdown checks this server every 3 days); 56 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-09; no tool definition change in 3 compared days; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.LuxAlgo/luxalgo-mcp-server
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.LuxAlgo/luxalgo-mcp-server?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server answered initialize and tools/list.
- Observed days in the last 30: 4
- Answered initialize and tools/list: 4
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 4 observed days. Lowdown checks without credentials.
Did its tools change recently?
No change in tool schemas, descriptions or names across 3 compared days.
What tools does it list?
56 tools on 2026-11-18:
alerts_create_customalerts_create_pricealerts_historyalerts_listalerts_pausealerts_resumechart_commandchart_openchart_peekchart_syncedge_presetsedge_reportedge_symbolsjournal_add_tradejournal_breakdownjournal_calendarjournal_get_dayjournal_get_tradejournal_list_accountsjournal_list_tagsjournal_list_tradesjournal_overviewjournal_search_notesjournal_update_notejournal_update_tradejournal_write_notelayouts_listlibrary_get_conceptlibrary_get_familylibrary_get_indicatorlibrary_get_source_codelibrary_list_conceptslibrary_list_familieslibrary_list_indicatorslibrary_searchluxalgo_accountpropfirms_challenge_rulespropfirms_comparepropfirms_getpropfirms_list_simulatablepropfirms_optimal_riskpropfirms_pass_ratespropfirms_searchpropfirms_search_challengespropfirms_search_offerspropfirms_simulatepropfirms_simulate_tradespropfirms_validate_strategytrackers_datasetstrackers_latesttrackers_querytrackers_tickerwatchlists_add_symbolswatchlists_createwatchlists_listwatchlists_remove_symbols
MCP Registry declaration
- Registry name:
io.github.LuxAlgo/luxalgo-mcp-server - Declared version: 2.1.0
- Status: active
- Declared hosts:
mcp.luxalgo.com
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:io.github.LuxAlgo/luxalgo-mcp-server", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.LuxAlgo/luxalgo-mcp-server?menu=install-check
When running its declared package, wrap it with the stdio proxy. Since lowdown-proxy 0.1.22 the proxy adds this record (install-check) to the server's initialize response; it changes no tool result and blocks nothing:
npx -y lowdown-proxy --target mcp:io.github.LuxAlgo/luxalgo-mcp-server -- npx -y @luxalgo/mcp
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).