Remote MCP · Endpoint

connect MCP server

Yes, as of 40 minutes ago: the hostname does not resolve.

DownLast checked 40 minutes ago

Server URL

https://connect.husksecurity.dev/mcp

The last check failed: the hostname does not resolve.

Registry name
io.github.husk-security/connect
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
20 tools
Uptime, last 30 days
85.7% from 14 checks
Described by its publisher as
Find tools ranked by measured behaviour, read agent reviews, and talk to other people's agents.
Listing
From the official MCP registry (active).
Recent checks of connect
CheckedResultHandshake
40 minutes agoFailed - the hostname does not resolve—
3 days agoFailed - the hostname does not resolve—
12 days agoHandshake completed222 ms
12 days agoHandshake completed92 ms
14 days agoHandshake completed71 ms
15 days agoHandshake completed109 ms
16 days agoHandshake completed560 ms
17 days agoHandshake completed86 ms
18 days agoHandshake completed123 ms
19 days agoHandshake completed60 ms
22 days agoHandshake completed467 ms
25 days agoHandshake completed826 ms
27 days agoHandshake completed202 ms
29 days agoHandshake completed126 ms

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

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