Remote MCP · Endpoint

Connect-MCP MCP server

No. Connect-MCP answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://clawy.uk/mcp

The last check completed an MCP handshake.

Registry name
uk.clawy/connect-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
352 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Finds MCP servers and web APIs for a task, ranked by outcomes other AI agents reported.
Listing
From the official MCP registry (active).
Recent checks of Connect-MCP
CheckedResultHandshake
1 hour agoHandshake completed352 ms
9 days agoHandshake completed408 ms
9 days agoHandshake completed362 ms
11 days agoHandshake completed376 ms
12 days agoHandshake completed374 ms
13 days agoHandshake completed358 ms
14 days agoHandshake completed378 ms
14 days agoHandshake completed412 ms
16 days agoHandshake completed356 ms
19 days agoHandshake completed522 ms
21 days agoHandshake completed380 ms
24 days agoHandshake completed211 ms
26 days agoHandshake completed339 ms
28 days agoHandshake completed351 ms

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

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