LuxAlgo MCP
NPM · @LUXALGO/MCP · 2 COMPONENTS
LuxAlgo for AI agents: the Library, prop firms, Market Trackers, Edge Stats, and your Trade Journal
Available components
Last scanned (20 hours ago)
Scores higher than 95% of npm servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 3 of 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to LuxAlgo/luxalgo-mcp-server). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 21 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 18810 tokens (~391/item across 48 items; 48 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
- 97% 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 48 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 48 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.
- 16 Oct 26 +1
- Stability: 0.97 → pass security
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 −3
- Stability: pass → 0.80 functional
- 2 Oct 26 +1
- Stability: 0.97 → pass security
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 −3
- Stability: pass → 0.80 functional
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 16 Oct 2026 · Analysed npm/@luxalgo/mcp@1.5.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | LuxAlgo/luxalgo-mcp-server |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/LuxAlgo/luxalgo-mcp-server/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 2945066770 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:fadc7f336a1d20a37809cb528ead466854ac16e5d4a63ca1449e3f1506d334a5049411d0e19876b4ac1b1534089cd2b5266370f18ca68028ec17e5ccc |
Background: How many MCP packages publish verified provenance →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| Stale | 3 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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_datasets List Market Trackers datasets ~184
The Market Trackers catalog: every dataset of US public-record market data the LuxAlgo pipeline publishes as CC0 dumps — 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. Returns each dataset's row count, freshness, the years with data (live tree vs deep-history archives), and whether it is ticker-searchable. Pass dataset for the full field roster, filterable paths, caveats, per-year coverage, source health, and dump URLs — read it before composing trackers_query filters.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | – | One dataset for the detailed view; omit to list all |
No output schema declared.
No examples provided.
trackers_latest Newest Market Trackers rows ~279
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 |
|---|---|---|---|
| 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 ~476
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 senator's trades → congress-trades, text 'Tuberville'; who lobbied on a bill → lobbying-filings, text 'H.R.1234'.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 ~162
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 |
|---|---|---|---|
| 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 runs locally as an npm package, launched with npx -y @luxalgo/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @luxalgo/mcp
claude mcp add luxalgo-luxalgo-mcp-server -- npx -y @luxalgo/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 npm package (@luxalgo/mcp).
Is the LuxAlgo MCP server safe to use?
LuxAlgo MCP scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 48 tools: library_search, library_get_concept, library_get_indicator, library_get_source_code, library_list_concepts, and 43 more. Their descriptions and schemas cost roughly 18,810 tokens of context every time the server is loaded.
Is the LuxAlgo MCP server still maintained?
LuxAlgo MCP is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the LuxAlgo MCP server under?
LuxAlgo MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.