
LeanTrading MCP
io.leantradingPublished by leantrading.ioOfficial publisherv1.2.0Updated Oct 24, 2026
OAuth LeanTrading tools for eligible Pro, Elite, Blueprint, and Admin users.
Overview
Hosted LeanTrading MCP server that connects MCP clients to the LeanTrading trading assistant over OAuth for eligible paid accounts.
- What you can do
- Connect an MCP client to the hosted LeanTrading assistant surface through OAuth 2.1 with PKCE, without copying a session token manually. Retrieve the user's LeanTrading system context, intelligence, risk-preview, advisory and charting data. Request chart, write and execute capabilities explicitly; these stay subject to LeanTrading scope checks and confirmation flows. No tool list is published, so exact operations are not documented here.
- When to use it
- Use it when you already hold an eligible LeanTrading account (Pro, Elite, Blueprint or Admin, or a Product Tester within the first 14 days) and want Cursor, Claude or another MCP client to work with your LeanTrading context, risk previews and charting data.
- Requirements
- A remote hosted endpoint reached over streamable HTTP; no local package or runtime. An OAuth connection to LeanTrading with an eligible paid account; Explorer and free accounts are not granted access. Chart, write and execute capabilities must be explicitly requested by the client.
Installation
In SourceWeft
- Open LeanTrading MCP in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.leantrading%2Fleantrading-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"leantrading": {
"type": "http",
"url": "https://www.leantrading.io/api/mcp"
}
}
}README
LeanTrading MCP
Connect Cursor, Claude, and other MCP clients to the hosted LeanTrading assistant surface through OAuth 2.1/PKCE.
Hosted server
The 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:
- Keep the repository public and limited to this bundle.
- Keep the repository URL in
server.jsonandplugin.jsonsynchronized. - Keep the hosted endpoint and version in all metadata synchronized with the deployed server.
- Publish the approved data-retention and deletion policy before final marketplace submission.
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 [email protected].
Source: README.md at commit d6fa5e3
Tools
0Version history
1- v1.2.0LatestSep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts