LuxAlgo MCP
REMOTE · MCP.LUXALGO.COM · 2 COMPONENTS
LuxAlgo for AI agents: the Library, prop firms, Market Trackers, Edge Stats, and your Trade Journal
Available components
Last scanned (4 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Finance and Payments
Recent critical change
Authorization (10 Oct 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (journal_update_trade). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 23678 tokens (~563/item across 42 items; 42 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 98% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 42 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 43 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 10 Oct 26 0
- Authorization: unverified → fail ▼ critical
- The server rewrote its instructions, which are the text every model session reads security
- Tool “propfirms_challenge_rules” rewrote its description, which is the text the model reads security
- Tool “trackers_query” rewrote its description, which is the text the model reads security
- Tool “propfirms_simulate_trades” rewrote its description, which is the text the model reads security
- Tool “propfirms_simulate” rewrote its description, which is the text the model reads security
- Tool “propfirms_optimal_risk” rewrote its description, which is the text the model reads security
- Tool “propfirms_list_simulatable” rewrote its description, which is the text the model reads security
- Tool “journal_write_note” rewrote its description, which is the text the model reads security
- Tool “journal_update_note” rewrote its description, which is the text the model reads security
- Tool “journal_update_trade” is now declared destructive security
- Tool “journal_update_note” is now declared destructive security
- 4 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 1 Oct 26 +7
- Stability: fail → pass ▲ security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Sept 26 0
- Schema quality: 661 → 567 ▲ functional
- New tool “journal_breakdown” functional
- New tool “journal_write_note” functional
- New tool “journal_update_trade” functional
- New tool “journal_update_note” functional
- New tool “journal_search_notes” functional
- New tool “journal_overview” functional
- New tool “journal_list_trades” functional
- New tool “journal_list_tags” functional
- New tool “journal_list_accounts” functional
- New tool “journal_get_trade” functional
- New tool “journal_get_day” functional
- New tool “journal_calendar” functional
- New tool “journal_add_trade” functional
- 10 Sept 26 0
- Server version: 1.4.0 → 1.4.1 functional
- New tool “luxalgo_account” functional
- 9 Sept 26 0
- The server changed its declared name: mcp-typescript server on vercel → luxalgo security
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- Server version: 0.1.0 → 1.4.0 functional
- “propfirms_compare” reworded the description of “context” cosmetic
- “edge_presets” reworded the description of “context” cosmetic
- “edge_report” reworded the description of “context” cosmetic
- “edge_symbols” reworded the description of “context” cosmetic
- “library_get_concept” reworded the description of “context” cosmetic
- “library_get_family” reworded the description of “context” cosmetic
- “library_get_indicator” reworded the description of “context” cosmetic
- “library_get_source_code” reworded the description of “context” cosmetic
- “library_list_concepts” reworded the description of “context” cosmetic
- “library_list_families” reworded the description of “context” cosmetic
- “library_list_indicators” reworded the description of “context” cosmetic
- “library_list_tags” reworded the description of “context” cosmetic
- “library_search” reworded the description of “context” cosmetic
- “propfirms_challenge_rules” reworded the description of “context” cosmetic
- “propfirms_get” reworded the description of “context” cosmetic
- “propfirms_list_simulatable” reworded the description of “context” cosmetic
- “propfirms_optimal_risk” reworded the description of “context” cosmetic
- “propfirms_pass_rates” reworded the description of “context” cosmetic
- “propfirms_search” reworded the description of “context” cosmetic
- “propfirms_search_challenges” reworded the description of “context” cosmetic
- “propfirms_search_offers” reworded the description of “context” cosmetic
- “propfirms_simulate” reworded the description of “context” cosmetic
- “propfirms_simulate_trades” reworded the description of “context” cosmetic
- “propfirms_validate_strategy” reworded the description of “context” cosmetic
- “trackers_datasets” reworded the description of “context” cosmetic
- “trackers_latest” reworded the description of “context” cosmetic
- “trackers_query” reworded the description of “context” cosmetic
- “trackers_ticker” reworded the description of “context” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://mcp.luxalgo.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.luxalgo.com | CN=YR1,O=Let's Encrypt,C=US | 10 Oct 2026 | 8 Jan 2027 | RSA 2048 | SHA256-RSA | 66e2019fddc000387496e824686ee8ab0f7 |
| SANs: mcp.luxalgo.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.luxalgo.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| luxalgo.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.luxalgo.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.luxalgo.com/mcp | HTTPS enforced | 308 | https://mcp.luxalgo.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
trackers_latest Newest Market Trackers rows ~412
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 disclosures, the latest lobbying registrations. Not available for snapshot-only bulk datasets (patents); use trackers_query there.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | 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,… |
| dataset | string | yes | Dataset id, from trackers_datasets |
| limit | integer | – | Rows to return (default 25, max 100) |
| offset | integer | – | Rows to skip, for paging (default 0) |
| sort | string | – | Order by event date (default newest) |
| text | string | – | Case-insensitive substring over the dataset's name/title fields (member, insider, issuer, recipient, registrant and client, sponsor, assignee, bill title, …); see textPaths in trackers_datasets |
| ticker | string | – | Trading symbol, case-insensitive (e.g. 'NVDA'); matches the dataset's ticker field(s). Only datasets flagged tickerSearchable carry tickers. |
| where | object | – | Exact field matches by dot path, e.g. {"side":"buy"}, {"member.state":"CA"}, {"code":"P"}, {"formType":"4"}; string comparisons are case-insensitive, arrays match when any element does |
No output schema declared.
No examples provided.
trackers_query Query a Market Trackers dataset ~612
Search one Market Trackers dataset by ticker, free text, exact field values, and event-date range, with paging and newest/oldest ordering. Data is read from year-sharded CC0 dumps: pass years (or since/until) to choose which years to read — default is the newest year with data. Deep-history years (see archiveYears in trackers_datasets) can be tens of MB compressed each, so read them one or two at a time; the tool refuses selections over its byte budget and says how to narrow. Every row carries provenance.sourceUrl (the SEC filing, disclosure, award, or record it came from). Examples: insider purchases at NVDA in 2024 → dataset insider-transactions, ticker NVDA, years [2024], where {code: 'P'}; a member of Congress's trades → congress-trades, text set to their name; who lobbied on a bill → lobbying-filings, text 'H.R.1234'.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | 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,… |
| dataset | string | yes | Dataset id, from trackers_datasets |
| limit | integer | – | Rows to return (default 25, max 100) |
| offset | integer | – | Rows to skip, for paging (default 0) |
| since | string | – | Earliest event date (YYYY-MM-DD, YYYY-MM or YYYY), inclusive |
| sort | string | – | Order by event date (default newest) |
| text | string | – | Case-insensitive substring over the dataset's name/title fields (member, insider, issuer, recipient, registrant and client, sponsor, assignee, bill title, …); see textPaths in trackers_datasets |
| ticker | string | – | Trading symbol, case-insensitive (e.g. 'NVDA'); matches the dataset's ticker field(s). Only datasets flagged tickerSearchable carry tickers. |
| until | string | – | Latest event date, inclusive |
| where | object | – | Exact field matches by dot path, e.g. {"side":"buy"}, {"member.state":"CA"}, {"code":"P"}, {"formType":"4"}; string comparisons are case-insensitive, arrays match when any element does |
| years | array | – | Event years to read (max 8); default is the newest year with data. Prefer one year at a time for deep-history datasets. |
No output schema declared.
No examples provided.
trackers_ticker Ticker across Market Trackers ~295
One ticker across every ticker-bearing Market Trackers dataset for one year (default: the current year): insider transactions, congressional trades, 13F holdings, federal contracts and grants, lobbying filings by the company, short-sale volume, clinical trials, FDA events, patents, Wikipedia pageviews. Returns per-dataset match counts with the newest rows of each — a public-record dossier from primary sources. Deep-history archive years too large for one fan-out are listed under skipped with the trackers_query call that reads them.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | 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,… |
| limit | integer | – | Newest rows to include per dataset (default 5) |
| ticker | string | yes | Trading symbol, e.g. 'NVDA' |
| year | integer | – | Event year to read (default: the current year) |
No output schema declared.
No examples provided.
How do I install the LuxAlgo MCP server?
LuxAlgo MCP is a hosted endpoint at https://mcp.luxalgo.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.luxalgo.com
claude mcp add --transport http luxalgo-luxalgo-mcp-server 'https://mcp.luxalgo.com/mcp'
What is the LuxAlgo MCP server?
LuxAlgo MCP is listed in the public MCP registry as io.github.LuxAlgo/luxalgo-mcp-server. LuxAlgo for AI agents: the Library, prop firms, Market Trackers, Edge Stats, and your Trade Journal. This page covers its hosted endpoint (https://mcp.luxalgo.com/mcp).
Is the LuxAlgo MCP server safe to use?
LuxAlgo MCP scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the LuxAlgo MCP server expose?
LuxAlgo MCP exposes 42 tools: library_search, library_get_concept, library_get_indicator, library_get_source_code, library_list_concepts, and 37 more. Their descriptions and schemas cost roughly 23,596 tokens of context every time the server is loaded.
Does the LuxAlgo MCP server require authentication?
No. We connected to LuxAlgo MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the LuxAlgo MCP server still maintained?
LuxAlgo MCP is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.