Bukku accounting API tools for Claude via Model Context Protocol
from $29/mo
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.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
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 — run it from where its publisher ships it
npx -y @lmex-official/lmex-mcp-server
# 2 — ask your agent something
> A Model Context Protocol (MCP) server for the LMEX exchange API — full spot and futures trading, market data, wallet management, and more.
Lmex is free: there is no plan to choose, no cap to set and nothing that can bill you.
Publishernot claimed
LMAll 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. It is scanned, signed and pinned to the version you choose — 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. Claude Code registers it in one command.
claude mcp add 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 to install, and it runs from its publisher’s own package: no account, no key, no card.
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.
Takes no parameters.
Example callreturns →
Get the current risk limit settings for a futures market.
Takes no parameters.
Example callreturns →
Set the risk limit for a futures market. Higher risk limits allow larger positions but may require higher margin.
Takes no parameters.
Example callreturns →
Get the current leverage setting for a futures market. Returns 0 for cross maximum leverage.
Takes no parameters.
Example callreturns →
Set the leverage for a futures market.
Takes no parameters.
Example callreturns →
Set the settlement currency for futures trading (settle-in).
Takes no parameters.
Example callreturns →
Get the current position mode (one-way or hedge) for a futures market.
Takes no parameters.
Example callreturns →
Set the position mode for a futures market (one-way or hedge mode).
Takes no parameters.
Example callreturns →
Get the margin summary for a specific futures market.
Takes no parameters.
Example callreturns →
Get futures market summary information. Returns all markets if no symbol is provided.
Takes no parameters.
Example callreturns →
Get OHLCV (candlestick) chart data for a futures market. Returns up to 300 data points.
Takes no parameters.
Example callreturns →
Get current futures market price(s). Returns indexPrice, lastPrice, and markPrice.
Takes no parameters.
Example callreturns →
Get the grouped Level 2 orderbook snapshot for a futures market.
Takes no parameters.
Example callreturns →
Get the raw Level 2 orderbook snapshot for a futures market at the specified depth.
Takes no parameters.
Example callreturns →
Get recent trade fills for a futures market. Maximum 30-day window; defaults to last 3 days.
Takes no parameters.
Example callreturns →
Get funding rate history for a perpetual futures market.
Takes no parameters.
Example callreturns →
Create a new futures order. Supports LIMIT, MARKET, OCO, PEG, and trigger orders.
Takes no parameters.
Example callreturns →
Amend price, size, or trigger price of a futures order.
Takes no parameters.
Example callreturns →
Cancel a pending futures order. Cancels by orderID, clOrderID, or all orders for the market.
Takes no parameters.
Example callreturns →
Query details of a specific futures order by orderID or clOrderID.
Takes no parameters.
Example callreturns →
Create a new futures algo (PEG) order. Price tracks the index price by a deviation %.
Takes no parameters.
Example callreturns →
Dead man
Takes no parameters.
Example callreturns →
Retrieve open futures orders that have not yet been matched.
Takes no parameters.
Example callreturns →
Retrieve the authenticated user
Takes no parameters.
Example callreturns →
Bind Take Profit (TP) and/or Stop Loss (SL) orders to an existing futures position.
Takes no parameters.
Example callreturns →
Close an open futures position at market or limit price.
Takes no parameters.
Example callreturns →
Retrieve the authenticated user
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
Get OHLCV (candlestick) chart data for a spot market. Returns up to 300 data points. Each candle is [unixTime, open, high, low, close, volume].
Takes no parameters.
Example callreturns →
Get current spot market price(s). Returns indexPrice, lastPrice, and markPrice for the specified symbol.
Takes no parameters.
Example callreturns →
Get the grouped Level 2 orderbook snapshot for a spot market. Returns buyQuote and sellQuote arrays with price/size.
Takes no parameters.
Example callreturns →
Get the raw Level 2 orderbook snapshot for a spot market. Returns full price/size arrays at the specified depth.
Takes no parameters.
Example callreturns →
Get recent trade fills for a spot market. Maximum 30-day window; defaults to last 3 days.
Takes no parameters.
Example callreturns →
Get the LMEX spot server time in ISO format and epoch seconds.
Takes no parameters.
Example callreturns →
Create a new spot order. Supports LIMIT, MARKET, OCO, PEG, and trigger (STOP/TAKE-PROFIT) orders.
Takes no parameters.
Example callreturns →
Amend the price, size, or trigger price of an existing spot order.
Takes no parameters.
Example callreturns →
Cancel a pending spot order. Cancels by orderID, clOrderID, or all orders for the market if neither is provided.
Takes no parameters.
Example callreturns →
Query details of a specific spot order by orderID or clOrderID.
Takes no parameters.
Example callreturns →
Create a new spot algo (PEG) order. The price tracks the index price by a deviation percentage.
Takes no parameters.
Example callreturns →
Dead man
Takes no parameters.
Example callreturns →
Retrieve open spot orders that have not yet been matched. Filter by orderID or clOrderID.
Takes no parameters.
Example callreturns →
Retrieve the authenticated user
Takes no parameters.
Example callreturns →
Retrieve the authenticated user
Takes no parameters.
Example callreturns →
Get the futures wallet balance(s) for the authenticated user.
Takes no parameters.
Example callreturns →
Get the futures wallet transaction history. Includes deposits, withdrawals, funding, PnL, and transfers.
Takes no parameters.
Example callreturns →
Freeyour plan
$0 forever
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Lmex costs nothing to install and nothing to call, 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: $8.42
$16.58 left
ATrust score 98 / 100
Release 1.0.2 · scanned 26 Aug 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-08-26
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
Pinned to 1.0.2 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
1.0.2
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Lmex in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
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 an account with 50 real tool calls against it.