Remote MCP · Endpoint

Quickgo MCP server

No. Quickgo answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/quickgo/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/quickgo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
365 ms
Tools exposed
47 tools
Uptime, last 30 days
94.4% from 18 checks
Described by its publisher as
QuickGO (EBI) MCP — Gene Ontology browser.
Listing
From the official MCP registry (active).
Recent checks of Quickgo
CheckedResultHandshake
1 hour agoHandshake completed365 ms
20 hours agoHandshake completed70 ms
2 days agoHandshake completed57 ms
3 days agoHandshake completed113 ms
4 days agoHandshake completed144 ms
5 days agoHandshake completed88 ms
6 days agoHandshake completed105 ms
8 days agoHandshake completed130 ms
11 days agoHandshake completed61 ms
13 days agoHandshake completed65 ms
16 days agoHandshake completed70 ms
18 days agoHandshake completed68 ms
20 days agoHandshake completed1.56 s
22 days agoHandshake completed60 ms
24 days agoFailed - the request timed out—
26 days agoHandshake completed53 ms
27 days agoHandshake completed72 ms
29 days agoHandshake completed69 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 27 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 Quickgo and makes no claim about it beyond what these checks measured.