Remote MCP · Endpoint

Pipefork Management MCP MCP server

No. Pipefork Management MCP answered an MCP handshake 4 days ago.

UpLast checked 4 days ago

Server URL

https://www.pipefork.com/mcp

The last check completed an MCP handshake.

Registry name
com.pipefork/management
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
330 ms
Tools exposed
27 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Manage Pipefork API projects, drafts, connections, secrets, and deployments through MCP.
Listing
From the official MCP registry (active).
Recent checks of Pipefork Management MCP
CheckedResultHandshake
4 days agoHandshake completed330 ms
4 days agoHandshake completed285 ms
5 days agoHandshake completed319 ms
7 days agoHandshake completed1.57 s
8 days agoHandshake completed1.55 s
9 days agoHandshake completed2.59 s
10 days agoHandshake completed906 ms
11 days agoHandshake completed1.80 s
12 days agoHandshake completed1.15 s
15 days agoHandshake completed239 ms
18 days agoHandshake completed943 ms
20 days agoHandshake completed349 ms
22 days agoHandshake completed1.53 s
24 days agoHandshake completed297 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

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 Pipefork Management MCP and makes no claim about it beyond what these checks measured.