Remote MCP · Endpoint

TradingAgentStack MCP server

No. TradingAgentStack answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://tradingagentstack.com/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.intoApex/tradingagentstack
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
94 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Verified results for AI trading bots, vaults and algo strategies, plus safety scores and incidents.
Listing
From the official MCP registry (active).
Recent checks of TradingAgentStack
CheckedResultHandshake
6 hours agoHandshake completed94 ms
9 days agoHandshake completed81 ms
10 days agoHandshake completed90 ms
11 days agoHandshake completed636 ms
12 days agoHandshake completed84 ms
14 days agoHandshake completed88 ms
15 days agoHandshake completed98 ms
15 days agoHandshake completed155 ms
17 days agoHandshake completed109 ms
19 days agoHandshake completed605 ms
22 days agoHandshake completed650 ms
24 days agoHandshake completed593 ms
26 days agoHandshake completed453 ms
28 days agoHandshake completed127 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with TradingAgentStack and makes no claim about it beyond what these checks measured.