Remote MCP · Endpoint

Git.Top MCP server

No. Git.Top answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://git.top/mcp/core

The last check completed an MCP handshake.

Registry name
io.github.haocn-ops/git-top
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
3.42 s
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Evidence-backed open-source project search, recommendations, alternatives, and comparisons.
Listing
From the official MCP registry (active).
Recent checks of Git.Top
CheckedResultHandshake
1 hour agoHandshake completed3.42 s
2 days agoHandshake completed139 ms
4 days agoHandshake completed81 ms
5 days agoHandshake completed74 ms
7 days agoHandshake completed54 ms
8 days agoHandshake completed307 ms
9 days agoHandshake completed74 ms
12 days agoHandshake completed70 ms
13 days agoHandshake completed85 ms
15 days agoHandshake completed71 ms
17 days agoHandshake completed179 ms
18 days agoHandshake completed30 ms
19 days agoHandshake completed124 ms
20 days agoHandshake completed61 ms
20 days agoHandshake completed39 ms
21 days agoHandshake completed56 ms
23 days agoHandshake completed52 ms

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

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