Remote MCP · Endpoint

DAMO Market State MCP server

No. DAMO Market State answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://api.damolive.com/mcp

The last check completed an MCP handshake.

Registry name
com.damolive/market-state
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
222 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Crypto market state, 44 assets: 4 states x 10 timeframes. Recorded, never recomputed, verifiable.
Listing
From the official MCP registry (active).
Recent checks of DAMO Market State
CheckedResultHandshake
2 hours agoHandshake completed222 ms
1 day agoHandshake completed252 ms
2 days agoHandshake completed258 ms
3 days agoHandshake completed384 ms
4 days agoHandshake completed244 ms
5 days agoHandshake completed240 ms
7 days agoHandshake completed388 ms
9 days agoHandshake completed251 ms
12 days agoHandshake completed217 ms
14 days agoHandshake completed233 ms
16 days agoHandshake completed272 ms
18 days agoHandshake completed273 ms
20 days agoHandshake completed257 ms
22 days agoHandshake completed245 ms
25 days agoHandshake completed244 ms

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

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