
TradeOnyx
io.tradeonyx由 tradeonyx.io 發布官方發布者v1.0.0更新於 Oct 24, 2026
Trading journal with pattern detection: log trades by voice, query your own history.
概覽
TradeOnyx 是託管的交易日誌 MCP 伺服器,讓助理記錄交易、回讀你的歷史,並查詢你自己交易中的規律。
- 可以做什麼
- 建立、編輯、平倉和刪除交易,並為交易附加截圖;讀取和更新交易後檢討與 AI 交易分析;觸發券商同步,列出帳戶與設定(唯讀)。撰寫、搜尋和讀取依日期歸檔的日誌條目,設定或清除預先規劃的交易劇本,並管理附件。管理策略劇本、具名策略、標籤和紀律規則,包括刪除與封存。讀取快取的 AI 產物:每日簡報、市場熱度、經濟事件與新聞分析、每週規律敘述與建議,以及每週摘要。取得彙總統計和依標籤的表現(僅 Pro Plus)。
- 適用情境
- 適合在 TradeOnyx 中記交易日誌的使用者,希望用對話方式讓助理記錄交易和檢討,或根據自己的交易歷史而非泛泛的市場評論來回答問題。
- 執行需求
- 透過 HTTP 與 JSON-RPC 2.0 存取的遠端端點,使用 Authorization 標頭中的 Bearer 權杖驗證(支援遠端連接器的用戶端也可走 OAuth 流程)。需要 TradeOnyx 帳戶,以及有效的 7 天連接器試用、Pro 或 Pro Plus 方案;四個批次彙總工具需要 Pro Plus。有每日呼叫上限(試用 30 次、Pro 150 次、Pro Plus 2000 次)。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 TradeOnyx,將其新增到工作區。
- 連接 所需的 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
交給代理程式安裝
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/io.tradeonyx%2Ftradeonyx/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。
{
"mcpServers": {
"tradeonyx": {
"type": "http",
"url": "https://tradeonyx.io/mcp"
}
}
}README
TradeOnyx MCP Server
Connect TradeOnyx to Claude, ChatGPT, Gemini or any other MCP-capable assistant. Log trades by voice, have the assistant read your journal back to you, and let it ground its answers in your actual trading history instead of guessing.
TradeOnyx is a trading journal with pattern detection: it imports trades from 40 brokers and runs 28 detectors over your own history to surface what repeats in your trading. This repository documents its MCP server. It contains no product code.
49 tools · JSON-RPC 2.0 over HTTP · hosted in Germany
Endpoint
Transport is HTTP with JSON-RPC 2.0. Authentication is a Bearer token in the
Authorization header. The server implements initialize, tools/list and
tools/call, and speaks protocol version 2025-06-18.
An unauthenticated call answers honestly rather than hanging:
Getting a token
- Create an account at tradeonyx.io. The account is free and asks for no payment details.
- Open Settings → Integrations and start the 7-day connector trial. A free account can start it once. After it runs out the connector needs Pro or Pro Plus; the journal, the broker imports and the tax export stay free either way. A call made without an active trial or plan is refused with a message saying so, never with a silent empty result.
- On the same screen, create an MCP token.
- Copy it immediately. The raw token is shown once; only a SHA-256 hash is stored, so a lost token cannot be recovered, only replaced.
- Revoke any token from the same screen at any time.
Tokens carry 256 bits of entropy. Treat one like a password: it grants the same access to your journal that you have.
Connecting an assistant
Any client that speaks MCP over HTTP works. For a client configured through a JSON file, the shape is:
Assistants that support remote MCP connectors directly (Claude's Connectors, for example) can add the endpoint through their own UI, including an OAuth flow, so no token needs to be pasted by hand.
What you can do with it
A few things people actually use it for:
- Log a trade in a sentence. "I bought 0.5 lots EURUSD at 1.0840, stop at 1.0810, because the London range broke upward." The assistant fills the fields and writes the reasoning into the journal next to the trade.
- Write the evening review by talking. The assistant reads back the day's trades, asks what you were thinking, and files the answers as a journal entry.
- Ask what actually happened. "Which of my setups lost money this month, and what did those trades have in common?" — grounded in your own rows, not in a guess.
- Prepare the session. Pull the daily briefing and the planned playbooks before the open.
Tools
49 tools. 45 need an active connector trial, Pro or Pro Plus; the 4 bulk aggregations need Pro Plus. The Plan column below says which.
Daily tool-call caps, counted per UTC day and shown in the app:
A call over the cap comes back as a normal tool result with isError: true,
naming the cap and when it resets, so an assistant can say what happened
instead of failing silently. It is HTTP 200: a cap is a business rule, not a
malformed request, and the specification's own worked example of a tool
execution error is an upstream rate limit.
How errors arrive
Two levels, and which one you get tells you whether the fix is in your arguments or in the data:
- Wrong arguments come back as a JSON-RPC error with code
-32602anddata.code = "invalid_arguments". That covers an unknown tool, an argument name the tool does not accept, a value outside a declaredenum, and a value past a declaredmaxLength/maxItems/maximum. Everything in that list is declared in theinputSchemayou already hold, so a client can correct it without asking. - Everything else comes back as a tool result with
isError: trueand a message incontent: a row that does not exist, a value the database will not store, a plan that does not include the tool, the daily cap.
Both are HTTP 200, because the transport requires exactly one JSON object per request. Values past a declared bound are refused, not shortened: a 5000 character note is rejected with the limit named rather than stored as its first 2000 characters, so what you keep is what you sent.
Accounts
Attachments
Broker sync
Daily briefing
Economic events
Journal
Market data
News
Patterns
Playbooks
Statistics
Strategies
Tags
Trades
Trading rules
Weekly digest
Plans
A free account starts the connector trial once, under Settings → Integrations. Before it is started, and after it has run out, the connector answers every call with an explicit refusal naming what to do; it does not return empty results. The web app itself stays free throughout.
Prices and current limits are on the pricing page.
Privacy and security
- Servers are in Germany and your journal and trades stay in the EU. The AI features send the text they analyse to a processor in the United States; every processor is named in the privacy policy, which is the authoritative list.
- Tokens are stored as SHA-256 hashes; the raw value exists only in your clipboard.
- Every tool resolves data through the authenticated user. A token reaches exactly the account it belongs to.
- Deleting your TradeOnyx account erases the associated data, including the access log for your requests.
Found a security issue? Please report it privately to the address in our security.txt ([email protected]) rather than opening a public issue.
Links
Disclaimer
TradeOnyx is a documentation and analysis tool. It does not provide investment advice or investment brokerage, and it does not generate trading signals. Trading financial instruments can lead to the total loss of the capital invested.
Licence
The documentation in this repository is MIT-licensed. TradeOnyx itself is a commercial product and is not open source.
來源:README.md,提交 ac6697f
工具
0版本歷史
1- v1.0.0最新Sep 16, 2026
評分
已滿足適用檢查項的 75%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通必需25 分
- 已宣告認證方式必需10 分
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分
請在儲存庫或註冊中心條目中宣告授權條款。