Remote MCP · Endpoint

TradeAlmanac MCP server

No. TradeAlmanac answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://tradealmanac.com/mcp

The last check completed an MCP handshake.

Registry name
com.tradealmanac/mcp-server
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
452 ms
Tools exposed
28 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
TradeAlmanac market data: dividends, screener, sentiment indicators, calendar effects, stock lists.
Listing
From the official MCP registry (active).
Recent checks of TradeAlmanac
CheckedResultHandshake
9 hours agoHandshake completed452 ms
15 hours agoHandshake completed488 ms
2 days agoHandshake completed455 ms
4 days agoHandshake completed874 ms
7 days agoHandshake completed440 ms
9 days agoHandshake completed410 ms
11 days agoHandshake completed412 ms
14 days agoHandshake completed408 ms
16 days agoHandshake completed388 ms
18 days agoHandshake completed400 ms
20 days agoHandshake completed385 ms
21 days agoHandshake completed399 ms
23 days agoHandshake completed440 ms

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

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