Remote MCP · Endpoint

Gitlab MCP server

No. Gitlab answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/gitlab/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/gitlab
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
118 ms
Tools exposed
49 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
GitLab MCP — wraps the GitLab REST API v4 (BYO API key)
Listing
From the official MCP registry (active).
Recent checks of Gitlab
CheckedResultHandshake
1 hour agoHandshake completed118 ms
1 day agoHandshake completed159 ms
2 days agoHandshake completed175 ms
3 days agoHandshake completed148 ms
4 days agoHandshake completed220 ms
5 days agoHandshake completed70 ms
6 days agoHandshake completed153 ms
9 days agoHandshake completed175 ms
12 days agoHandshake completed52 ms
14 days agoHandshake completed82 ms
16 days agoHandshake completed76 ms
18 days agoHandshake completed60 ms
21 days agoHandshake completed77 ms
23 days agoHandshake completed78 ms
25 days agoHandshake completed54 ms
26 days agoHandshake completed104 ms
28 days agoHandshake completed57 ms
29 days agoHandshake completed206 ms

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

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