Remote MCP · Endpoint
VibeDeploy MCP server
No. VibeDeploy answered an MCP handshake 6 hours ago.
UpLast checked 6 hours ago
Server URL
https://mcp.vibedeploy.be/mcp
The last check completed an MCP handshake.
- Registry name
- be.vibedeploy/vibedeploy
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 320 ms
- Tools exposed
- 43 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Deploy AI-built sites and apps to EU hosting from your AI agent. OAuth sign-in, 14-day free trial.
- Website
- https://vibedeploy.be/mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 6 hours ago | Handshake completed | 320 ms |
| 2 days ago | Handshake completed | 287 ms |
| 4 days ago | Handshake completed | 293 ms |
| 5 days ago | Handshake completed | 280 ms |
| 7 days ago | Handshake completed | 300 ms |
| 8 days ago | Handshake completed | 292 ms |
| 9 days ago | Handshake completed | 298 ms |
| 12 days ago | Handshake completed | 503 ms |
| 13 days ago | Handshake completed | 287 ms |
| 15 days ago | Handshake completed | 290 ms |
| 16 days ago | Handshake completed | 294 ms |
| 17 days ago | Handshake completed | 288 ms |
| 18 days ago | Handshake completed | 289 ms |
| 19 days ago | Handshake completed | 287 ms |
| 20 days ago | Handshake completed | 290 ms |
| 21 days ago | Handshake completed | 289 ms |
| 22 days ago | Handshake completed | 322 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
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 VibeDeploy and makes no claim about it beyond what these checks measured.