TradeOS (test)

io.github.TradeOS-AI由 GitHub 账号 TradeOS-AI 发布v1.0.0-alpha.6更新于 Nov 9, 2026

[TEST] TradeOS MCP bridge: ticker search, My Agent, chart TA, macro news. npm or HTTP.

已验证Streamable HTTP可网页运行网页搜索与抓取金融数据与分析

概览

AI 生成的概览

TradeOS MCP 将 TradeOS 交易情报接入 AI 助手，支持代码搜索、行情分析、价差比较、宏观新闻与自定义交易代理。

可以做什么
  • 搜索交易代码并查询市场标的
  • 分析图表与技术指标
  • 比较价差并获取宏观新闻背景
  • 创建和管理自定义交易代理（My Agent）
  • 通过 HTTP 或本地 stdio 桥接把上述能力代理到 TradeOS 远程端点
适用场景
适合希望用自然语言让助手研究行情、比较价差、做技术与宏观分析，并集中管理自定义交易代理的用户。已拥有具备 MCP API 访问权限的 TradeOS 账户时最合适。
运行要求
两种方式：使用远程 HTTP 端点并由客户端完成浏览器 OAuth；或在本地运行 npm 包，需要 Node.js 18+ 以及通过 OAuth 辅助工具获取的 TRADEOS_ACCESS_TOKEN 环境变量。需要具备 MCP API 访问权限的 TradeOS 账户。Windows 上 README 建议固定目录本地安装而非使用 npx。
安装前请注意
npm 模式需要 TradeOS 访问令牌（TRADEOS_ACCESS_TOKEN），不要提交到版本库或与他人共享的客户端配置中。该服务器可创建和管理交易代理，操作可能影响你的 TradeOS 账户。行情分析不构成投资建议，提示与数据会发送至 TradeOS 服务。

安装

在 SourceWeft 中

  1. 打开 控制台中的 TradeOS (test)，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.TradeOS-AI%2Ftradeos-mcp-test/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "tradeos-test": {
      "type": "http",
      "url": "https://ai.tradeos.xyz/api/agent/mcp-call"
    }
  }
}

README

tradeos-mcp

TradeOS MCP lets you connect TradeOS trading intelligence to MCP-compatible AI tools, so your assistant can analyze markets, search tickers, compare spreads, use macro context, and manage custom trading agents directly from natural-language prompts.

Overview

This repo publishes @tradeos/tradeos-mcp on npm: a stdio MCP bridge that proxies tools to TradeOS Streamable HTTP (mcp-call). You can connect in two ways:

ModeBest forAuth
HTTP (recommended)Cursor, Claude Code, most MCP clientsBrowser OAuth in the client
npm stdioClients that only support command / stdioTRADEOS_ACCESS_TOKEN env var

Production endpoint (both modes ultimately call this):

text
https://ai.tradeos.xyz/api/agent/mcp/mcp-call

Product docs: TradeOS MCP integration & usage

Prerequisites

  • Node.js 18+
  • A TradeOS account with MCP API access
  • For npm stdio: ability to run a local install (see Windows notes)

Option A — HTTP (recommended)

No npm install. The client handles OAuth.

Cursor

Edit user config ~/.cursor/mcp.json (Windows: %USERPROFILE%\.cursor\mcp.json):

json
{  "mcpServers": {    "tradeos": {      "url": "https://ai.tradeos.xyz/api/agent/mcp/mcp-call"    }  }}

Save, restart Cursor (or refresh MCP in Settings → MCP), then complete OAuth when prompted.

Claude Code (plugin — recommended)

Use the bundled plugin in tradeos-skills/:

bash
claude --plugin-dir ./tradeos-skills

Then complete OAuth and run /tradeos:analyze. Full plugin workflow (validate, community marketplace submit): tradeos-skills/README.md — aligned with Claude plugin docs.

Option B — npm stdio bridge

Use when your client requires a local process (command + stdio).

1. Install locally

Do not rely on npx inside MCP on Windows (cache/path issues). Install once to a fixed directory:

bash
mkdir -p ~/tradeos-mcp-run   # Windows: mkdir %USERPROFILE%\Downloads\tradeos-mcp-runcd ~/tradeos-mcp-run         # Windows: cd %USERPROFILE%\Downloads\tradeos-mcp-runnpm install @tradeos/tradeos-mcp

Pin a version if you prefer, e.g. @tradeos/[email protected].

2. Get TRADEOS_ACCESS_TOKEN

Run the OAuth helper (opens browser → log in on TradeOS → prints token):

bash
# Linux / macOSnpx -y -p @tradeos/tradeos-mcp tradeos-mcp-oauth
# Or subcommand on main bin:npx -y @tradeos/tradeos-mcp oauth
# Or, from your install directory:node node_modules/@tradeos/tradeos-mcp/scripts/fetch-token.mjs

Windows (recommended):

cmd
cd /d %USERPROFILE%\Downloads\tradeos-mcp-runnode node_modules\@tradeos\tradeos-mcp\scripts\fetch-token.mjs

Copy the printed JWT (eyJ...). For local development of this repo, copy into .env:

bash
cp .example.env .env# TRADEOS_ACCESS_TOKEN=eyJ...

End users who only npm install the package do not need .env — set the token in MCP client config (mcp.json) instead.

Do not commit tokens to git.

3. Configure Cursor

json
{  "mcpServers": {    "tradeos-npm": {      "command": "node",      "args": [        "C:/Users/YOU/Downloads/tradeos-mcp-run/node_modules/@tradeos/tradeos-mcp/build/index.js"      ],      "env": {        "TRADEOS_ACCESS_TOKEN": "eyJ..."      }    }  }}

Replace YOU and the path with your actual install location. Use forward slashes or escaped backslashes in JSON.

If Cursor cannot find node, set the full path:

json
"command": "C:/nvm4w/nodejs/node.exe"

Enable tradeos-npm in Settings → MCP. Status should show connected with tools listed.

4. Verify in terminal (optional)

Environment variables in mcp.json do not apply to your shell. Set the token in the same terminal session:

cmd
REM Windows CMDset TRADEOS_ACCESS_TOKEN=eyJ...node C:\Users\YOU\Downloads\tradeos-mcp-run\node_modules\@tradeos\tradeos-mcp\build\index.js
bash
# Linux / macOSexport TRADEOS_ACCESS_TOKEN=eyJ...node ~/tradeos-mcp-run/node_modules/@tradeos/tradeos-mcp/build/index.js

Success:

text
[tradeos-mcp] remote: https://ai.tradeos.xyz/api/agent/mcp/mcp-call[tradeos-mcp] stdio bridge ready

Press Ctrl+C to stop. Cursor starts its own process; you do not need to keep this terminal open.

Windows notes

  1. Use local node + install path in mcp.json, not npx, for MCP.
  2. If npm cache errors mention C:\Program Files\nodejs\node_cache, run once:
    cmd
    npm config set cache "%USERPROFILE%\.npm-cache"
  3. npx @pkg tradeos-mcp-oauth may run the wrong bin on Windows. Prefer:
    cmd
    npx -y -p @tradeos/tradeos-mcp tradeos-mcp-oauth
    or node .../scripts/fetch-token.mjs from your install directory.
  4. Clear a broken npx cache (quit Cursor first):
    cmd
    rmdir /s /q "%USERPROFILE%\.npm-cache\_npx"

npm package reference

ItemValue
Package@tradeos/tradeos-mcp
MCP Registry nameio.github.TradeOS-AI/tradeos-mcp
Bin: MCP bridgetradeos-mcp
Bin: OAuth tokentradeos-mcp-oauth
OAuth subcommandoauth on bin tradeos-mcp

Install:

bash
npm install @tradeos/tradeos-mcp

Development (this repo)

bash
git clone https://github.com/TradeOS-AI/tradeos-mcp.gitcd tradeos-mcpnpm cinpm run buildnpm run oauth:token    # browser OAuth → prints token (copy into .env if needed)npm run registry:verify
ScriptPurpose
npm run buildCompile stdio bridge to build/
npm run oauth:tokenBrowser OAuth → print token
npm run registry:verifyPre-publish checks (package.json ↔ server.json)
npm run registry:sync-version <ver>Sync version from release tag

Publishing (maintainers)

Push a version tag to trigger .github/workflows/publish-mcp.yml:

bash
git tag v1.0.0git push origin v1.0.0
  • Stable tags (v1.0.0) publish to npm latest and the MCP Registry.
  • Pre-release tags (v1.0.0-beta.1) publish with an npm dist-tag matching the prerelease label (e.g. beta).
  • Requires GitHub Actions secret NPM_TOKEN (Classic Automation token for @tradeos).

Verify on the registry API:

bash
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.TradeOS-AI/tradeos-mcp"

Troubleshooting

SymptomLikely causeFix
TRADEOS_ACCESS_TOKEN is requiredToken not set in env / mcp.jsonRun oauth helper; set env in MCP config
unauthorized on connectExpired or invalid tokenRe-run oauth; paste fresh JWT (no Bearer prefix)
EPERM / node_cachenpm cache under Program Filesnpm config set cache "%USERPROFILE%\.npm-cache"
TAR_ENTRY_ERROR / 'tradeos-mcp' is not recognizednpx failed on WindowsLocal install + node path in mcp.json
MODULE_NOT_FOUND for node_modules/...Ran script from wrong directorycd to install dir or use absolute path
Token works in terminal, not in Cursormcp.json path or token mismatchMatch paths; restart Cursor / refresh MCP
MCP connects but no toolsWrong server enabledDisable broken localhost entries; use production HTTP URL or working tradeos-npm

Related

来源：README.md，提交 2b620e3

工具

0
SourceWeft 尚未读取此服务器的工具。

版本历史

1
  1. v1.0.0-alpha.6最新Sep 16, 2026

评分

已满足适用检查项的 85%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分