MCP server list / midasflow-mcp-quickstart
Agent-native crypto market-data over MCP+REST: order flow, whales, liquidations, calibrated scores
Answered:
4 of 4 checks
- Status
- responds
- Typical response time
- 699 ms
- Last checked
- Latest check:
- This server answered at its latest check.Last checked · MCP initialize · 8s limit · HTTP 200 · answered in 677 ms.
- Address
- https://mcp.midasflow.ai/
mcp - Listed in:
- official MCP registry
mcp_registry - Registry name
- io.github.midasflowai-lab/
midasflow-mcp-quickstart - Transport
- streamable HTTP
streamable-http - Host
mcp.midasflow.ai
An outside server from a public listing, not run by Licium; being listed here is not an endorsement.
What the server says about itself
We have not checked it.- Server name:
- MidasFlow Flow API
- Version:
- 1.28.0
- MCP features it lists:
- experimental, prompts, resources, tools
- Tool names:
get_signalsscore_symbolget_candlesget_orderbookget_flowget_heatmapget_contextget_whalesget_marketget_accuracyaccountbacktestand 2 more
analyzecalc_ev- Instructions excerpt:
- MidasFlow Flow API — crypto market DATA / analytics, NOT financial advice. Recommended workflow: (1) get_accuracy → realized first-TP win-rate per source family; (2) feed a bucket's win-rate + average win/loss into calc_ev → expected value; (3) get_signals for the live feed. account shows your tier and remaining daily quota — self-throttle by it. Win-rate …
Reported Aug 17, 2026, 05:04 AM UTC.
Check history
oldest to newest; each row is one recorded check| Checked | Status | Took | Check |
|---|---|---|---|
| responds | 1,110 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 721 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 629 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 677 ms | MCP initialize · 8s limit · HTTP 200 |
Need a different server, page or part?
Say what you need. We log your request. It can then go on the bounty board, where anyone can add money toward it. Or put a price on it and start today. Your words go with it.
Agents do the same with request_source or POST /v1/requests; this record is GET /v1/directory/{slug} with the slug from this page's address. Run this server? Register it as a part.
Latest recorded check ; every row above is one recorded call.