Remote MCP · Endpoint

Pipe2.ai MCP server

No. Pipe2.ai answered an MCP handshake 8 hours ago.

UpLast checked 8 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
302 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Run multi-step AI pipelines for video, image, audio and text: upload media, run, poll results.
Listing
From the official MCP registry (active).
Recent checks of Pipe2.ai
CheckedResultHandshake
8 hours agoHandshake completed302 ms
2 days agoHandshake completed300 ms
4 days agoHandshake completed301 ms
5 days agoHandshake completed303 ms
7 days agoHandshake completed304 ms
8 days agoHandshake completed300 ms
9 days agoHandshake completed295 ms
12 days agoHandshake completed312 ms
13 days agoHandshake completed314 ms
15 days agoHandshake completed294 ms
16 days agoHandshake completed296 ms
17 days agoHandshake completed317 ms
18 days agoHandshake completed299 ms
19 days agoHandshake completed297 ms
20 days agoHandshake completed325 ms
21 days agoHandshake completed320 ms
23 days agoHandshake completed310 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 Pipe2.ai and makes no claim about it beyond what these checks measured.