Remote MCP · Endpoint
GitEasy MCP MCP server
No. GitEasy MCP answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://giteasy-mcp.azurewebsites.net/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.greenmtnsun/giteasy
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 243 ms
- Tools exposed
- 22 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Plain-English git for agents: 22 tools to branch, commit, push and tag. Free tier.
- Repository
- https://github.com/greenmtnsun/GitEasy
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 243 ms |
| 1 day ago | Handshake completed | 317 ms |
| 2 days ago | Handshake completed | 246 ms |
| 3 days ago | Handshake completed | 307 ms |
| 4 days ago | Handshake completed | 221 ms |
| 5 days ago | Handshake completed | 217 ms |
| 6 days ago | Handshake completed | 294 ms |
| 9 days ago | Handshake completed | 257 ms |
| 11 days ago | Handshake completed | 291 ms |
| 14 days ago | Handshake completed | 390 ms |
| 16 days ago | Handshake completed | 329 ms |
| 18 days ago | Handshake completed | 328 ms |
| 20 days ago | Handshake completed | 309 ms |
| 22 days ago | Handshake completed | 313 ms |
| 24 days ago | Handshake completed | 361 ms |
| 26 days ago | Handshake completed | 407 ms |
| 27 days ago | Handshake completed | 356 ms |
| 29 days ago | Handshake completed | 305 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 GitEasy MCP and makes no claim about it beyond what these checks measured.