Remote MCP · Endpoint

io.github.QueryQuarry/queryquarry MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://queryquarry.com/api/mcp

The last check failed: the server returned an HTTP error.

Registry name
io.github.QueryQuarry/queryquarry
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
11 tools
Uptime, last 30 days
94.1% from 17 checks
Described by its publisher as
Double-blind talent marketplace: AIs search anonymous opted-in candidates; reveal on consent.
Listing
From the official MCP registry (active).
Recent checks of io.github.QueryQuarry/queryquarry
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
2 days agoHandshake completed161 ms
4 days agoHandshake completed118 ms
5 days agoHandshake completed120 ms
7 days agoHandshake completed177 ms
8 days agoHandshake completed1.08 s
9 days agoHandshake completed109 ms
12 days agoHandshake completed119 ms
13 days agoHandshake completed112 ms
15 days agoHandshake completed203 ms
17 days agoHandshake completed116 ms
18 days agoHandshake completed165 ms
19 days agoHandshake completed123 ms
20 days agoHandshake completed132 ms
20 days agoHandshake completed141 ms
21 days agoHandshake completed177 ms
22 days agoHandshake completed121 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 16 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 io.github.QueryQuarry/queryquarry and makes no claim about it beyond what these checks measured.