Remote MCP · Endpoint
Pipe2.ai MCP server
No. Pipe2.ai answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://mcp.pipe2.ai/mcp
The last check completed an MCP handshake.
- Registry name
- ai.pipe2/mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 307 ms
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Run multi-step AI pipelines for video, image, audio and text: upload media, run, poll results.
- Website
- https://pipe2.ai/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 307 ms |
| 1 day ago | Handshake completed | 333 ms |
| 3 days ago | Handshake completed | 308 ms |
| 3 days ago | Handshake completed | 325 ms |
| 4 days ago | Handshake completed | 312 ms |
| 5 days ago | Handshake completed | 383 ms |
| 7 days ago | Handshake completed | 307 ms |
| 10 days ago | Handshake completed | 308 ms |
| 12 days ago | Handshake completed | 306 ms |
| 15 days ago | Handshake completed | 295 ms |
| 17 days ago | Handshake completed | 335 ms |
| 19 days ago | Handshake completed | 307 ms |
| 21 days ago | Handshake completed | 302 ms |
| 23 days ago | Handshake completed | 300 ms |
| 25 days ago | Handshake completed | 301 ms |
| 26 days ago | Handshake completed | 303 ms |
| 28 days ago | Handshake completed | 304 ms |
| 29 days ago | Handshake completed | 300 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 Pipe2.ai and makes no claim about it beyond what these checks measured.