Remote MCP · Endpoint
Forge Engine MCP server
No. Forge Engine answered an MCP handshake 2 hours ago.
UpLast checked 2 hours 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
- 274 ms
- Tools exposed
- 54 tools
- Uptime, last 30 days
- 100% from 18 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 |
|---|---|---|
| 2 hours ago | Handshake completed | 274 ms |
| 2 days ago | Handshake completed | 227 ms |
| 4 days ago | Handshake completed | 336 ms |
| 6 days ago | Handshake completed | 270 ms |
| 7 days ago | Handshake completed | 245 ms |
| 9 days ago | Handshake completed | 264 ms |
| 10 days ago | Handshake completed | 175 ms |
| 11 days ago | Handshake completed | 276 ms |
| 14 days ago | Handshake completed | 179 ms |
| 15 days ago | Handshake completed | 229 ms |
| 17 days ago | Handshake completed | 256 ms |
| 18 days ago | Handshake completed | 151 ms |
| 19 days ago | Handshake completed | 196 ms |
| 20 days ago | Handshake completed | 216 ms |
| 21 days ago | Handshake completed | 223 ms |
| 22 days ago | Handshake completed | 235 ms |
| 23 days ago | Handshake completed | 225 ms |
| 24 days ago | Handshake completed | 235 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 18 responding of 18.
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.