Remote MCP · Endpoint

io.github.midasflowai-lab/midasflow-mcp-quickstart MCP server

No. io.github.midasflowai-lab/midasflow-mcp-quickstart answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.midasflow.ai/mcp

The last check completed an MCP handshake.

Registry name
io.github.midasflowai-lab/midasflow-mcp-quickstart
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
817 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Agent-native crypto market-data over MCP+REST: order flow, whales, liquidations, calibrated scores
Listing
From the official MCP registry (active).
Recent checks of io.github.midasflowai-lab/midasflow-mcp-quickstart
CheckedResultHandshake
2 hours agoHandshake completed817 ms
2 days agoHandshake completed783 ms
4 days agoHandshake completed906 ms
5 days agoHandshake completed1.41 s
7 days agoHandshake completed793 ms
8 days agoHandshake completed775 ms
9 days agoHandshake completed811 ms
12 days agoHandshake completed724 ms
13 days agoHandshake completed776 ms
15 days agoHandshake completed743 ms
17 days agoHandshake completed787 ms
18 days agoHandshake completed732 ms
19 days agoHandshake completed1.02 s
20 days agoHandshake completed939 ms
20 days agoHandshake completed722 ms
21 days agoHandshake completed3.09 s
23 days agoHandshake completed776 ms

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

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 io.github.midasflowai-lab/midasflow-mcp-quickstart and makes no claim about it beyond what these checks measured.