Remote MCP · Endpoint
Forge Engine MCP server
No. Forge Engine answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcp
The last check completed an MCP handshake.
- Registry name
- app.forgeengine/forge
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 374 ms
- Tools exposed
- 54 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Design spec + milestones AI coding agents read before building; drift flagged, changes reviewed.
- Website
- https://forgeengine.app/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 374 ms |
| 10 hours ago | Handshake completed | 430 ms |
| 1 day ago | Handshake completed | 210 ms |
| 2 days ago | Handshake completed | 176 ms |
| 4 days ago | Handshake completed | 250 ms |
| 4 days ago | Handshake completed | 242 ms |
| 5 days ago | Handshake completed | 282 ms |
| 6 days ago | Handshake completed | 265 ms |
| 8 days ago | Handshake completed | 290 ms |
| 11 days ago | Handshake completed | 320 ms |
| 13 days ago | Handshake completed | 274 ms |
| 16 days ago | Handshake completed | 227 ms |
| 18 days ago | Handshake completed | 192 ms |
| 20 days ago | Handshake completed | 274 ms |
| 22 days ago | Handshake completed | 227 ms |
| 24 days ago | Handshake completed | 336 ms |
| 26 days ago | Handshake completed | 270 ms |
| 27 days ago | Handshake completed | 245 ms |
| 29 days ago | Handshake completed | 264 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 31 responding of 31.
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 Forge Engine and makes no claim about it beyond what these checks measured.