io.github.winter0x/lighter-mcp
NPM · LIGHTER-MCP · SCANNED SEP 20
Read Lighter perpetual markets and place guarded orders, including the H100 compute-price market.
Available components
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 Security98
- 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
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 17 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1434 tokens (~159/item across 9 items; 9 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 Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.winter0x/lighter-mcp server?
io.github.winter0x/lighter-mcp runs locally as an npm package, launched with npx -y lighter-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 · lighter-mcp
claude mcp add winter0x-lighter-mcp -- npx -y lighter-mcp
{
"mcpServers": {
"winter0x-lighter-mcp": {
"command": "npx",
"args": [
"-y",
"lighter-mcp"
]
}
}
} {
"servers": {
"winter0x-lighter-mcp": {
"command": "npx",
"args": [
"-y",
"lighter-mcp"
]
}
}
} codex mcp add winter0x-lighter-mcp -- npx -y lighter-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"winter0x-lighter-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"lighter-mcp"
],
"enabled": true
}
}
} openclaw mcp add winter0x-lighter-mcp --command npx --arg -y --arg lighter-mcp
mcp_servers:
winter0x-lighter-mcp:
command: "npx"
args: ["-y", "lighter-mcp"] {
"McpServers": {
"winter0x-lighter-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"lighter-mcp"
]
}
}
} assistant mcp add winter0x-lighter-mcp -t stdio -c npx -a -y lighter-mcp
{
"mcpServers": {
"winter0x-lighter-mcp": {
"command": "npx",
"args": [
"-y",
"lighter-mcp"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Analysed npm/lighter-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| 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 →
lighter_account Lighter account state ~129
Collateral, open positions, and account value for one Lighter sub-account. Defaults to the account in LIGHTER_ACCOUNT_INDEX. Pass a market selector to include the resting orders on that market. Order listing needs either a read-only token or a signing key, since Lighter authenticates that route.
| Name | Type | Req | Description |
|---|---|---|---|
| account_index | integer | – | Sub-account to read. Defaults to the configured account. |
| market_id | integer | – | Market id, for example 182 for H100. Use this or symbol. |
| symbol | string | – | Market ticker, for example H100. Use this or market_id. |
No output schema declared.
No examples provided.
lighter_cancel Cancel a Lighter order ~108
Cancel one resting order by market and order index. Read the order index from lighter_account with a market selector.
| Name | Type | Req | Description |
|---|---|---|---|
| market_id | integer | – | Market id, for example 182 for H100. Use this or symbol. |
| order_index | string | yes | Exchange-assigned order index, as a decimal string. It exceeds the safe integer range, so pass it exactly as lighter_account reported it. |
| symbol | string | – | Market ticker, for example H100. Use this or market_id. |
No output schema declared.
No examples provided.
lighter_cancel_all Cancel all Lighter orders ~44
Cancel every resting order on the configured sub-account, across all markets. Lighter cancels account-wide, so this cannot be scoped to one market. Open positions are untouched.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lighter_funding Lighter funding rates ~168
Current funding rates and settled funding history. The current rate is a fraction charged over one 8 hour period, and settled history is an hourly percent, so each number carries its unit in the response. A positive rate means longs pay shorts. Omit both selectors to rank Lighter's own markets by the largest rate. Rates from the other venues Lighter tracks are reference data and are left out, since a position opened here collects Lighter's rate.
| Name | Type | Req | Description |
|---|---|---|---|
| history_limit | integer | – | Settled hourly funding payments to return for the selected market, 0 to 50. |
| market_id | integer | – | Market id, for example 182 for H100. Use this or symbol. |
| symbol | string | – | Market ticker, for example H100. Use this or market_id. |
No output schema declared.
No examples provided.
lighter_h100 H100 compute price ~116
Price, funding, and book depth for market 182 (H100), a perpetual on the rental cost of an NVIDIA H100. Use it to read the traded cost of compute and to see which side funding pays before hedging a GPU bill. The H100 book is thin: about $7,100 of 24 hour volume, open interest near $10,000, and 4.00 of size at the top of book on each side when measured on 2026-08-26. Size hedges accordingly.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lighter_hedge_h100 Hedge H100 compute cost ~260
Size a hedge on market 182 (H100) for a number of GPU hours, price it against the live book, and report the funding it earns or pays. A short covers a renter against rising compute prices. This tool is a dry run and returns a plan. It signs and sends the order only when execute is true, and max_notional_usd is required either way. A Lighter API key is full write authority over the account it is bound to, so run this server against a dedicated sub-account funded with only what the agent may lose.
| Name | Type | Req | Description |
|---|---|---|---|
| execute | boolean | – | Set true to sign and send the hedge. Left false, the tool returns the plan and sends nothing. |
| gpu_hours | number | yes | H100 hours of rental cost to cover. One unit of base is one GPU hour. |
| max_notional_usd | number | yes | Required ceiling on order notional in USD. The order is refused when its worst-case notional exceeds this value. There is no default. |
| side | string | – | short covers a buyer of compute against rising prices. long covers a seller of compute against falling prices. |
| slippage_bps | number | – | Average execution bound in basis points from the touch. |
No output schema declared.
No examples provided.
lighter_market Lighter market detail ~96
Mark price, index price, funding rate, and top of book for one market. Select the market by market_id or by symbol.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | – | Order book levels per side, 1 to 20. |
| market_id | integer | – | Market id, for example 182 for H100. Use this or symbol. |
| symbol | string | – | Market ticker, for example H100. Use this or market_id. |
No output schema declared.
No examples provided.
lighter_markets List Lighter markets ~111
List or search the perpetual markets on a Lighter deployment. Mainnet lists id 182, H100, a perpetual on the rental cost of an NVIDIA H100, which the response always includes. Results are capped and the response reports the full count, so pass a query to narrow the list.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum markets to return, 1 to 100. |
| query | string | – | Case-insensitive substring match on the ticker, for example "H100" or "SOL". |
No output schema declared.
No examples provided.
lighter_place_order Place a Lighter order ~349
Sign and send one limit or market order. max_notional_usd is required and has no default. The order is priced against one book snapshot and refused above the ceiling before it is signed, so the order that goes out is the order that was checked. The server applies its own configured ceiling as well, and the lower of the two wins. A Lighter API key is full write authority over the account it is bound to, so run this server against a dedicated sub-account funded with only what the agent may lose.
| Name | Type | Req | Description |
|---|---|---|---|
| market_id | integer | – | Market id, for example 182 for H100. Use this or symbol. |
| max_notional_usd | number | yes | Required ceiling on order notional in USD. The order is refused when its worst-case notional exceeds this value. There is no default. |
| order_type | string | – | limit rests on the book. market is immediate-or-cancel with an average execution bound. |
| price | number | – | Limit price in quote units. Required for a limit order. |
| reduce_only | boolean | – | Refuse to open or increase a position. A reduce-only order can only shrink an existing position, so it is exempt from max_notional_usd and from the market size floor. |
| side | string | yes | Order side. |
| size | number | yes | Order size in base units, in human decimals. |
| slippage_bps | number | – | Average execution bound for a market order, in basis points. |
| symbol | string | – | Market ticker, for example H100. Use this or market_id. |
| time_in_force | string | – | Resting behaviour for a limit order. Defaults to gtt. |
No output schema declared.
No examples provided.
What is the io.github.winter0x/lighter-mcp server?
io.github.winter0x/lighter-mcp is listed in the public MCP registry as io.github.winter0x/lighter-mcp. Read Lighter perpetual markets and place guarded orders, including the H100 compute-price market. This page covers its npm package (lighter-mcp).
Is the io.github.winter0x/lighter-mcp server safe to use?
io.github.winter0x/lighter-mcp scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.winter0x/lighter-mcp server expose?
io.github.winter0x/lighter-mcp exposes 9 tools: lighter_markets, lighter_market, lighter_h100, lighter_funding, lighter_account, and 4 more. Their descriptions and schemas cost roughly 1,381 tokens of context every time the server is loaded.
Is the io.github.winter0x/lighter-mcp server still maintained?
io.github.winter0x/lighter-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.winter0x/lighter-mcp server under?
io.github.winter0x/lighter-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.