Remote MCP · Endpoint

Hydracept MCP server

No. Hydracept answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.hydracept.com/mcp

The last check completed an MCP handshake.

Registry name
com.hydracept/hydracept
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
97 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Hosted MCP for Hydracept: discover capabilities, run jobs, receipts, BYOK or managed billing.
Listing
From the official MCP registry (active).
Recent checks of Hydracept
CheckedResultHandshake
1 hour agoHandshake completed97 ms
1 day agoHandshake completed78 ms
3 days agoHandshake completed89 ms
6 days agoHandshake completed98 ms
7 days agoHandshake completed89 ms
9 days agoHandshake completed89 ms
10 days agoHandshake completed91 ms
11 days agoHandshake completed92 ms
13 days agoHandshake completed86 ms
15 days agoHandshake completed109 ms
17 days agoHandshake completed75 ms
19 days agoHandshake completed96 ms
20 days agoHandshake completed90 ms
21 days agoHandshake completed83 ms
22 days agoHandshake completed848 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 Hydracept and makes no claim about it beyond what these checks measured.