
LeanTrading MCP server
online · 100% uptimeio.leantrading/leantrading-mcp·v1.2.0OAuth LeanTrading tools for eligible Pro, Elite, Blueprint, and Admin users.
0 stars
Reviews
Write oneNobody has reviewed LeanTrading MCP yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
LeanTrading MCP tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.10 · 2026-10-14 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 522ms (auth required)20/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityOAuth resource metadata advertised on 40115/15
- Maintenancelast push 29 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year; website matches verified namespace10/10
How LeanTrading MCP compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 100/100
- higher than 100% of 48,243 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 1,053 ms
- faster than 12% of 30,027 servers
Install LeanTrading MCP in Claude Code, Cursor or VS Code
claude mcp add --transport http leantrading-mcp https://www.leantrading.io/api/mcp
What the publisher says
From the LeanTrading MCP repository's README, as published. We do not edit it. Read it on GitHub
LeanTrading MCP
Connect Cursor, Claude, and other MCP clients to the hosted LeanTrading assistant surface through OAuth 2.1/PKCE.
Hosted server
https://www.leantrading.io/api/mcpThe server requires a LeanTrading OAuth connection and an eligible account: paid Pro/Elite/Blueprint/Admin, or Product Tester during the first 14 days of the tester grant. After that window, Product Tester must upgrade to Pro. Explorer and free accounts are not granted hosted MCP access.
Installation
This repository contains the marketplace metadata and Cursor plugin wrapper. It does not contain credentials and does not require a manually copied Supabase session JWT.
The default OAuth request is read-only. Chart, write, and execute capabilities must be explicitly requested by the client and remain subject to LeanTrading scope checks and confirmation boundaries.
Safety boundaries
- OAuth authorization uses PKCE with the S256 method.
- Access and refresh tokens are not stored in plaintext by the server.
- Entitlements are checked again on every hosted MCP call.
- Webhook secrets are redacted and are not returned by the MCP tools.
- Silent broker order placement is not exposed as an MCP operation.
- Chart and alert mutations require stronger scopes and confirmation flows.
Marketplace listing is not a security certification. Review the source, requested scopes, and the LeanTrading privacy/security notices before connecting an account.
Repository packaging
This directory is the export bundle for the public LeanTrading/leantrading-mcp repository. It contains metadata and a thin wrapper for the hosted service; it does not contain the private server source.
Before submitting it to a marketplace:
deployed server.
- Keep the repository public and limited to this bundle.
- Keep the repository URL in server.json and plugin.json synchronized.
- Keep the hosted endpoint and version in all metadata synchronized with the
marketplace submission.
- Publish the approved data-retention and deletion policy before final
Privacy note
MCP requests can expose the user's requested LeanTrading system context, intelligence, risk-preview, advisory, and charting data to the connected client. Hosted MCP calls are audited using server-side metadata such as user, client, event, tool, status, and structured metadata; raw tool arguments are not stored. This metadata is retained only as long as necessary to provide the service, protect it, and comply with legal obligations, then deleted or anonymized when no longer needed. Account deletion remains subject to short backup cycles and statutory retention duties.
MCP hosting and database/authentication subprocessors include Vercel and Supabase. Data-protection requests can be sent to info@leantrading.de.
Nothing above is checked by us. What we check is on the safety report.
LeanTrading MCP: common questions
- Is LeanTrading MCP server safe?
- Yes, by our scan: it is graded A (100/100). Read the LeanTrading MCP safety report
- How do I install LeanTrading MCP?
- It runs remotely at www.leantrading.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does LeanTrading MCP need an API key?
- No key to paste: it signs you in with OAuth when your client connects.
- Is LeanTrading MCP maintained?
- The last commit was 51 days ago (2026-09-15). The latest release is v1.2.0.
- Is LeanTrading MCP up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does LeanTrading MCP compare with other MCP servers?
- safety score 100/100 (higher than 100% of 48,243 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 1,053 ms (faster than 12% of 30,027 servers). Full comparison.