Remote MCP · Endpoint

link.hultra/mcp-registry-uptime MCP server

No. link.hultra/mcp-registry-uptime answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://link-mcp.hultra-site.workers.dev/

The last check completed an MCP handshake.

Registry name
link.hultra/mcp-registry-uptime
Transport
Streamable HTTP
Protocol negotiated
2026-07-28
Handshake latency
51 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Annuaire vérifié des serveurs MCP : ce qui est mort, protégé ou en retard de spec.
Listing
From the official MCP registry (active).
Recent checks of link.hultra/mcp-registry-uptime
CheckedResultHandshake
1 hour agoHandshake completed51 ms
9 days agoHandshake completed65 ms
10 days agoHandshake completed68 ms
11 days agoHandshake completed50 ms
12 days agoHandshake completed43 ms
14 days agoHandshake completed62 ms
14 days agoHandshake completed66 ms
15 days agoHandshake completed300 ms
17 days agoHandshake completed99 ms
19 days agoHandshake completed77 ms
21 days agoHandshake completed47 ms
24 days agoHandshake completed95 ms
26 days agoHandshake completed77 ms
28 days agoHandshake completed48 ms

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

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 link.hultra/mcp-registry-uptime and makes no claim about it beyond what these checks measured.