Model Context Protocol (MCP) server for freee API integration
Nothing to run from here
Lmex is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
98/100
trust score
2
downloads a day
local
runs on your machine
53
downloads in 30d
What it does
A Model Context Protocol (MCP) server for the LMEX exchange API — full spot and futures trading, market data, wallet management, and more.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user lmex-mcp '--' npx -y @lmex-official/lmex-mcp-server
# 2 — ask your agent for something these tools do
# lmex_futures_positions, lmex_futures_get_risk_limit, lmex_futures_set_risk_limit and 42 more
Lmex costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
LOAll 1 server
@lmex-official1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Lmex as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user lmex-mcp '--' npx -y @lmex-official/lmex-mcp-serverReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
45 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Retrieve open futures positions for the authenticated user.
No parameter schema on file.
Get the current risk limit settings for a futures market.
No parameter schema on file.
Set the risk limit for a futures market. Higher risk limits allow larger positions but may require higher margin.
No parameter schema on file.
Get the current leverage setting for a futures market. Returns 0 for cross maximum leverage.
No parameter schema on file.
Set the leverage for a futures market.
No parameter schema on file.
Set the settlement currency for futures trading (settle-in).
No parameter schema on file.
Get the current position mode (one-way or hedge) for a futures market.
No parameter schema on file.
Set the position mode for a futures market (one-way or hedge mode).
No parameter schema on file.
Get the margin summary for a specific futures market.
No parameter schema on file.
Get futures market summary information. Returns all markets if no symbol is provided.
No parameter schema on file.
Get OHLCV (candlestick) chart data for a futures market. Returns up to 300 data points.
No parameter schema on file.
Get current futures market price(s). Returns indexPrice, lastPrice, and markPrice.
No parameter schema on file.
Get the grouped Level 2 orderbook snapshot for a futures market.
No parameter schema on file.
Get the raw Level 2 orderbook snapshot for a futures market at the specified depth.
No parameter schema on file.
Get recent trade fills for a futures market. Maximum 30-day window; defaults to last 3 days.
No parameter schema on file.
Get funding rate history for a perpetual futures market.
No parameter schema on file.
Create a new futures order. Supports LIMIT, MARKET, OCO, PEG, and trigger orders.
No parameter schema on file.
Amend price, size, or trigger price of a futures order.
No parameter schema on file.
Cancel a pending futures order. Cancels by orderID, clOrderID, or all orders for the market.
No parameter schema on file.
Query details of a specific futures order by orderID or clOrderID.
No parameter schema on file.
Create a new futures algo (PEG) order. Price tracks the index price by a deviation %.
No parameter schema on file.
Dead man
No parameter schema on file.
Retrieve open futures orders that have not yet been matched.
No parameter schema on file.
Retrieve the authenticated user
No parameter schema on file.
Bind Take Profit (TP) and/or Stop Loss (SL) orders to an existing futures position.
No parameter schema on file.
Close an open futures position at market or limit price.
No parameter schema on file.
Retrieve the authenticated user
No parameter schema on file.
Get spot market summary information. Returns all markets if no symbol is provided. Includes last price, bid/ask, 24hr high/low, volume, and market constraints.
No parameter schema on file.
Get OHLCV (candlestick) chart data for a spot market. Returns up to 300 data points. Each candle is [unixTime, open, high, low, close, volume].
No parameter schema on file.
Get current spot market price(s). Returns indexPrice, lastPrice, and markPrice for the specified symbol.
No parameter schema on file.
Get the grouped Level 2 orderbook snapshot for a spot market. Returns buyQuote and sellQuote arrays with price/size.
No parameter schema on file.
Get the raw Level 2 orderbook snapshot for a spot market. Returns full price/size arrays at the specified depth.
No parameter schema on file.
Get recent trade fills for a spot market. Maximum 30-day window; defaults to last 3 days.
No parameter schema on file.
Get the LMEX spot server time in ISO format and epoch seconds.
No parameter schema on file.
Create a new spot order. Supports LIMIT, MARKET, OCO, PEG, and trigger (STOP/TAKE-PROFIT) orders.
No parameter schema on file.
Amend the price, size, or trigger price of an existing spot order.
No parameter schema on file.
Cancel a pending spot order. Cancels by orderID, clOrderID, or all orders for the market if neither is provided.
No parameter schema on file.
Query details of a specific spot order by orderID or clOrderID.
No parameter schema on file.
Create a new spot algo (PEG) order. The price tracks the index price by a deviation percentage.
No parameter schema on file.
Dead man
No parameter schema on file.
Retrieve open spot orders that have not yet been matched. Filter by orderID or clOrderID.
No parameter schema on file.
Retrieve the authenticated user
No parameter schema on file.
Retrieve the authenticated user
No parameter schema on file.
Get the futures wallet balance(s) for the authenticated user.
No parameter schema on file.
Get the futures wallet transaction history. Includes deposits, withdrawals, funding, PnL, and transfers.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Lmex or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 98 / 100
Release 1.0.2 · scanned 14 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score98
Findings1 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationnone
Surface digestbb1d092dc9e834737e41dec76af265daced4a5d6186e2f1933e20dee2f5bad71
Score vectorthreat 100 → client 98
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | none | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read | −2 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestbb1d092dc9e83473
Scanned2026-10-14
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.0.2. Pin a release below and the command asks for exactly that one.
1.0.2
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Lmex can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.