Remote MCP · Endpoint

Hybriqx Workout Adaptation MCP server

Yes, as of 9 hours ago: the server returned an HTTP error.

DownLast checked 9 hours ago

Server URL

https://www.hybriqx.com/mcp/

The last check failed: the server returned an HTTP error.

Registry name
io.github.LKennedyShare/hybriqx-workout-adaptation
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
2 tools
Uptime, last 30 days
84.6% from 13 checks
Described by its publisher as
Advisory workout adaptation via hosted MCP and x402. Python buyer with operator-approved tools.
Listing
From the official MCP registry (active).
Recent checks of Hybriqx Workout Adaptation
CheckedResultHandshake
9 hours agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
14 days agoHandshake completed20 ms
15 days agoHandshake completed22 ms
15 days agoHandshake completed20 ms
17 days agoHandshake completed21 ms
18 days agoHandshake completed27 ms
19 days agoHandshake completed28 ms
20 days agoHandshake completed22 ms
21 days agoHandshake completed31 ms
23 days agoHandshake completed25 ms
26 days agoHandshake completed21 ms
28 days agoHandshake completed25 ms

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

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