Remote MCP · Endpoint

urlhub MCP server

No. urlhub answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://urlhub.cloud/mcp

The last check completed an MCP handshake.

Registry name
cloud.urlhub/urlhub
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
360 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Many links as one short link with a QR code; read urlhub sets and preview what links are about.
Listing
From the official MCP registry (active).
Recent checks of urlhub
CheckedResultHandshake
1 hour agoHandshake completed360 ms
4 days agoHandshake completed436 ms
14 days agoHandshake completed313 ms
15 days agoHandshake completed436 ms
15 days agoHandshake completed350 ms
17 days agoHandshake completed302 ms
18 days agoHandshake completed321 ms
19 days agoHandshake completed305 ms
20 days agoHandshake completed409 ms
21 days agoHandshake completed354 ms
23 days agoHandshake completed399 ms
25 days agoHandshake completed324 ms
28 days agoHandshake completed310 ms

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

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