
TradeOS (Test)
Exercise the TradeOS test MCP package against alpha APIs for ticker search, TA, and macro news before adopting production TradeOS MCP.
Overview
TradeOS (test) MCP is an Idea-phase Finance MCP server for alpha TradeOS ticker search, My Agent, chart TA, and macro news over test npm or HTTP endpoints.
What is this MCP server?
- [TEST] bridge with same feature themes: ticker search, My Agent, chart TA, macro news
- stdio package @tradeos/tradeos-mcp-test at version 1.0.0-alpha.6
- Remote streamable-http at ai.tradeos.xyz/api/agent/mcp-call (test path differs from production mcp-call)
- TRADEOS_ACCESS_TOKEN via npx -y @tradeos/tradeos-mcp-test oauth
- Use only for integration experiments—not a substitute for io.github.TradeOS-AI/tradeos-mcp in production catalogs
- Test package version 1.0.0-alpha.6
- 2 transports: stdio npm and remote streamable-http
- Labeled [TEST] in catalog description
What problem does it solve?
Shipping agent finance tooling against production TradeOS without a staging MCP package risks breaking OAuth and API contracts under active development.
Who is it for?
Maintainers of TradeOS-integrated agents who need an explicit test npm id and mcp-call URL separate from production.
Skip if: Production solo products, live trading assistants, or builders who want stable semver without alpha churn.
What do I get? / Deliverables
After configuring the test package and token, you can validate MCP prompts and transports against TradeOS alpha before switching to tradeos-mcp 1.0.3.
- Alpha stdio MCP via @tradeos/tradeos-mcp-test
- Test streamable-http MCP registration against ai.tradeos.xyz
- Validated OAuth and agent prompts before production MCP cutover
Recommended MCP Servers
Journey fit
Test bridges belong in Idea research when you are proving agent integration against staging endpoints, not when you operate live user-facing finance features. Research subphase covers trying @tradeos/tradeos-mcp-test and alternate mcp-call URLs without committing your main product path.
How it compares
Alpha/test twin of TradeOS MCP—same research theme, different package id and remote path—not TradeRouter on-chain execution.
Common Questions / FAQ
Who is TradeOS MCP (test) for?
Agent developers testing TradeOS integrations with @tradeos/tradeos-mcp-test before they standardize on the production MCP server.
When should I use TradeOS MCP (test)?
Use it during Idea research and integration spikes when you need alpha APIs and the mcp-call test route, not for shipped user features.
How do I add TradeOS MCP (test) to my agent?
Run npx -y @tradeos/tradeos-mcp-test oauth, set TRADEOS_ACCESS_TOKEN, add stdio MCP for @tradeos/tradeos-mcp-test, or use the test streamable-http URL from server.json.