Remote MCP · Endpoint

Algo Trader Tools MCP server

No. Algo Trader Tools answered an MCP handshake 30 minutes ago.

UpLast checked 30 minutes ago

Server URL

https://mcp.algotradertools.com/mcp

The last check completed an MCP handshake.

Registry name
com.algotradertools/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
440 ms
Tools exposed
14 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Manage MetaTrader 4 and 5 trade copying: accounts, copiers, followers and their copy rules.
Listing
From the official MCP registry (active).
Recent checks of Algo Trader Tools
CheckedResultHandshake
30 minutes agoHandshake completed440 ms
3 days agoHandshake completed383 ms
13 days agoHandshake completed592 ms

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

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 Algo Trader Tools and makes no claim about it beyond what these checks measured.

Algo Trader Tools MCP server - status, uptime and latency - Glide