Remote MCP · Endpoint

pro.horustek/horus-flow-mcp MCP server

Yes, as of 17 hours ago: the request timed out.

DownLast checked 17 hours ago

Server URL

https://flow.horustek.pro/mcp

The last check failed: the request timed out.

Registry name
pro.horustek/horus-flow-mcp
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
15 tools
Uptime, last 30 days
91.7% from 12 checks
Described by its publisher as
Crypto order flow, cross-venue derivatives and US market context for AI agents, with a track record.
Listing
From the official MCP registry (active).
Recent checks of pro.horustek/horus-flow-mcp
CheckedResultHandshake
17 hours agoFailed - the request timed out—
11 days agoHandshake completed360 ms
12 days agoHandshake completed434 ms
12 days agoHandshake completed391 ms
14 days agoHandshake completed347 ms
15 days agoHandshake completed363 ms
16 days agoHandshake completed355 ms
17 days agoHandshake completed361 ms
18 days agoHandshake completed474 ms
20 days agoHandshake completed450 ms
22 days agoHandshake completed356 ms
25 days agoHandshake completed378 ms

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

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 pro.horustek/horus-flow-mcp and makes no claim about it beyond what these checks measured.