TradeOS MCP server
online · 96% uptimeTradeOS MCP: ticker search, My Agent, chart TA, macro news. npm stdio or HTTP.
18 stars47 downloads/wk
Reviews
Write oneNobody has reviewed TradeOS yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
TradeOS tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan9 source files scanned25/25
- Live reliabilityremote reachable in 128ms (auth required)20/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityOAuth resource metadata advertised on 40115/15
- Maintenancelast push 116 days ago8/15
- Maintainer identityregistry namespace matches repository owner7/10
Install TradeOS in Claude Code, Cursor or VS Code
claude mcp add --transport http tradeos-mcp https://ai.tradeos.xyz/api/agent/mcp/mcp-call
What the publisher says
From the TradeOS repository's README, as published. We do not edit it. Read it on GitHub
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:
Production endpoint (both modes ultimately call this):
https://ai.tradeos.xyz/api/agent/mcp/mcp-callProduct 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):
{
"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/:
claude --plugin-dir ./tradeos-skillsThen 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:
mkdir -p ~/tradeos-mcp-run # Windows: mkdir %USERPROFILE%\Downloads\tradeos-mcp-run
cd ~/tradeos-mcp-run # Windows: cd %USERPROFILE%\Downloads\tradeos-mcp-run
npm install @tradeos/tradeos-mcpPin a version if you prefer, e.g. @tradeos/tradeos-mcp@1.0.0.
2. Get TRADEOSACCESSTOKEN
Run the OAuth helper (opens browser → log in on TradeOS → prints token):
# Linux / macOS
npx -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.mjsWindows (recommended):
cd /d %USERPROFILE%\Downloads\tradeos-mcp-run
node node_modules\@tradeos\tradeos-mcp\scripts\fetch-token.mjsCopy the printed JWT (eyJ...). For local development of this repo, copy into .env:
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
{
"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:
"command": "C:/nvm4w/nodejs/node.exe"Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
TradeOS: common questions
- Is TradeOS MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the TradeOS safety report
- How do I install TradeOS?
- It runs remotely at ai.tradeos.xyz. 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 TradeOS need an API key?
- No key to paste: it signs you in with OAuth when your client connects.
- Is TradeOS maintained?
- The last commit was 117 days ago (2026-06-03). The latest release is v1.0.3.
- Is TradeOS up?
- 96% of our last 28 checks got an answer. We check remote servers about four times a day.
- What can I use instead of TradeOS?
- Servers from other publishers that do the same job: Agent-Native Analytics MCP server, Mockserver MCP server and Datawrapper MCP server. Compare all TradeOS alternatives.
Alternatives to TradeOS
Same job from other publishers: the closest match first, then the best rated.
- Agent-Native AnalyticsAgent-Native Amplitude/Mixpanel - connect data sources, prompt for chartsnot reviewedEstablishedA
- MockserverMock, record/replay, verify and chaos-test any HTTP, REST, gRPC or LLM dependency over MCP.not reviewedEstablishedA
- DatawrapperA Model Context Protocol (MCP) server and app for creating Datawrapper charts using AI assistantsnot reviewedEstablishedB
- HOL GuardLocal-first AI agent security evidence and approval workflows through HOL Guard's stdio MCP server.not reviewedEstablishedA