Remote MCP · Endpoint
Upforge MCP server
No. Upforge answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://upforge.io/api/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.upforge-dev/upforge
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 351 ms
- Tools exposed
- 20 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Talk with Upforge Echo, compare services and proof, or request a human-approved project review.
- Website
- https://upforge.io/
- Repository
- https://github.com/upforge-dev/upforge
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 351 ms |
| 1 day ago | Handshake completed | 768 ms |
| 2 days ago | Handshake completed | 480 ms |
| 3 days ago | Handshake completed | 170 ms |
| 4 days ago | Handshake completed | 407 ms |
| 5 days ago | Handshake completed | 218 ms |
| 6 days ago | Handshake completed | 847 ms |
| 9 days ago | Handshake completed | 515 ms |
| 11 days ago | Handshake completed | 980 ms |
| 14 days ago | Handshake completed | 694 ms |
| 16 days ago | Handshake completed | 502 ms |
| 18 days ago | Handshake completed | 494 ms |
| 20 days ago | Handshake completed | 567 ms |
| 22 days ago | Handshake completed | 223 ms |
| 24 days ago | Handshake completed | 232 ms |
| 26 days ago | Handshake completed | 342 ms |
| 27 days ago | Handshake completed | 354 ms |
| 29 days ago | Handshake completed | 499 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 Upforge and makes no claim about it beyond what these checks measured.