Remote MCP · Endpoint
X402 Git MCP server
No. X402 Git answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://x402git.com/api/mcp
The last check completed an MCP handshake.
- Registry name
- com.x402git/git-x402
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 251 ms
- Tools exposed
- 6 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Buy private git repos and agent skills with USDC over x402. Read the manifest free, then pay.
- Website
- https://x402git.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 251 ms |
| 1 day ago | Handshake completed | 441 ms |
| 2 days ago | Handshake completed | 286 ms |
| 3 days ago | Handshake completed | 259 ms |
| 4 days ago | Handshake completed | 207 ms |
| 5 days ago | Handshake completed | 243 ms |
| 6 days ago | Handshake completed | 292 ms |
| 9 days ago | Handshake completed | 233 ms |
| 12 days ago | Handshake completed | 239 ms |
| 14 days ago | Handshake completed | 412 ms |
| 16 days ago | Handshake completed | 225 ms |
| 18 days ago | Handshake completed | 298 ms |
| 20 days ago | Handshake completed | 247 ms |
| 22 days ago | Handshake completed | 223 ms |
| 24 days ago | Handshake completed | 207 ms |
| 26 days ago | Handshake completed | 227 ms |
| 27 days ago | Handshake completed | 269 ms |
| 28 days ago | Handshake completed | 367 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 X402 Git and makes no claim about it beyond what these checks measured.