Remote MCP · Endpoint

MarketHeist Backtest MCP server

No. MarketHeist Backtest answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.marketheist.io/api/mcp

The last check completed an MCP handshake.

Registry name
io.marketheist/backtest
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
138 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Backtest and analyze any portfolio, incl. nested multi-strategy ones: returns, risk, factors, guides
Listing
From the official MCP registry (active).
Recent checks of MarketHeist Backtest
CheckedResultHandshake
1 hour agoHandshake completed138 ms
9 days agoHandshake completed58 ms
10 days agoHandshake completed158 ms
11 days agoHandshake completed140 ms
12 days agoHandshake completed153 ms
14 days agoHandshake completed211 ms
14 days agoHandshake completed189 ms
15 days agoHandshake completed193 ms
17 days agoHandshake completed166 ms
19 days agoHandshake completed148 ms
21 days agoHandshake completed144 ms
24 days agoHandshake completed159 ms
26 days agoHandshake completed291 ms
28 days agoHandshake completed113 ms

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

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