
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 分
请在仓库或注册中心条目中声明许可证。