TradeOS (test) is listed as active in the registry but did not answer our last check. 26 installs a week from npm. Last commit 3 Jun 2026.
[TEST] TradeOS MCP bridge: ticker search, My Agent, chart TA, macro news. npm or HTTP.
We read the source, 23 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const { status, error } = spawnSync(
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.
claude mcp add tradeos-mcp-test --transport http https://ai.tradeos.xyz/api/agent/mcp-call
{
"mcpServers": {
"tradeos-mcp-test": {
"url": "https://ai.tradeos.xyz/api/agent/mcp-call"
}
}
}
[mcp_servers.tradeos-mcp-test]
url = "https://ai.tradeos.xyz/api/agent/mcp-call"
{
"mcpServers": {
"tradeos-mcp-test": {
"url": "https://ai.tradeos.xyz/api/agent/mcp-call"
}
}
}
{
"mcpServers": {
"tradeos-mcp-test": {
"url": "https://ai.tradeos.xyz/api/agent/mcp-call"
}
}
}
This one needs environment variables set before it will start:
TRADEOS_ACCESS_TOKEN (OAuth Bearer for mcp-call. Run: npx -y @tradeos/tradeos-mcp-test oauth, then paste the printed token.).
The author declared them in the registry entry; get the values from the project itself.
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://ai.tradeos.xyz/api/agent/mcp-call | streamable-http | answering | 249 ms | 11 min ago |
A test MCP server for task management
Semantic map of a .NET test-automation solution for AI agents — search, impact, endpoints
Mock, record/replay, verify and chaos-test any HTTP, REST, gRPC or LLM dependency over MCP.
Build, run and live-test FiveM servers with AI agents: RCON, DevCon, window control, mcpb bridge.
MCP server for API testing. 35 tools: HTTP, assertions, flows, OpenAPI, collections.
MCP server for API testing: HTTP requests, cURL generation, health checks.
MCP server for QMetry Test Management for Jira (QTM4J) Open API.
A standardized testing harness for MCP servers and agent workflows
Answers built from our own checks of this server.