mcp.luxalgo.com

Very long descriptions are sometimes used to bury instructions to the AI. Skim it before allowing.

Very long descriptions are sometimes used to bury instructions to the AI. Skim it before allowing.

Very long descriptions are sometimes used to bury instructions to the AI. Skim it before allowing.

Very long descriptions are sometimes used to bury instructions to the AI. Skim it before allowing.

Very long descriptions are sometimes used to bury instructions to the AI. Skim it before allowing.

Very long descriptions are sometimes used to bury instructions to the AI. Skim it before allowing.

Very long descriptions are sometimes used to bury instructions to the AI. Skim it before allowing.

Very long descriptions are sometimes used to bury instructions to the AI. Skim it before allowing.

Very long descriptions are sometimes used to bury instructions to the AI. Skim it before allowing.

Very long descriptions are sometimes used to bury instructions to the AI. Skim it before allowing.

Very long descriptions are sometimes used to bury instructions to the AI. Skim it before allowing.

This server isn't on gate's handpicked list. That's not necessarily bad, but there's no third-party signal about it — review its tools carefully.

Every tool in this collection (library_search, library_get_concept, library_get_indicator, library_get_source_code, library_list_concepts, library_list_indicators, library_list_tags, library_list_families, library_get_family, propfirms_search, propfirms_get, propfirms_search_challenges, propfirms_search_offers, propfirms_list_simulatable, propfirms_challenge_rules, propfirms_simulate, propfirms_optimal_risk, propfirms_compare, propfirms_simulate_trades, propfirms_pass_rates, propfirms_validate_strategy, trackers_datasets, trackers_query, trackers_latest, trackers_ticker, edge_symbols, edge_presets, edge_report) requires a 'context' string with imperative instructions directed at the AI model itself ('YOU MUST provide 15-25 words', 'NEVER use first person', 'maintain third-person perspective') under the guise of an 'analytics' field. This is a directive embedded in a tool schema that shapes the agent's output/behavior rather than describing what the tool does, and it forces the agent to generate and transmit a free-text description of the user's private goal/intent to the tool provider on every single call. While the field explicitly forbids including credentials/PII, the mechanism itself is a form of mandatory behavioral compliance and covert usage-intent telemetry baked into every tool invocation, which is unusual and could be leveraged to exfiltrate summarized user intent to a third party without explicit user consent for each call.location:

The tool accepts free-form pasted broker exports (MT4/MT5 account statements as CSV or HTML, ThinkOrSwim statements, TradingView trade lists, broker JSON fills) via tradeLogText/tradeLogTexts. These real-world export formats commonly include account numbers, account holder names, server/broker identifiers, and other account metadata beyond bare R-multiples. The tool does not instruct the agent to strip or warn about such identifying data before sending it to the MCP server, so an agent naively pasting a full statement could transmit more personal/account data than necessary for the stated simulation purpose.