Remote MCP · Endpoint

io.github.terradev-cloud/quorum MCP server

Yes, as of 43 minutes ago: the request timed out.

DownLast checked 43 minutes ago

Server URL

https://quorum-mcp.terradev.cloud/mcp

The last check failed: the request timed out.

Registry name
io.github.terradev-cloud/quorum
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
7 tools
Uptime, last 30 days
78.6% from 14 checks
Described by its publisher as
Attested multi-agent consensus: proposals, votes, and outcomes stamped and traced.
Listing
From the official MCP registry (active).
Recent checks of io.github.terradev-cloud/quorum
CheckedResultHandshake
43 minutes agoFailed - the request timed out—
10 days agoFailed - the request timed out—
10 days agoFailed - the request timed out—
11 days agoHandshake completed37 ms
12 days agoHandshake completed24 ms
14 days agoHandshake completed34 ms
14 days agoHandshake completed33 ms
15 days agoHandshake completed27 ms
17 days agoHandshake completed25 ms
19 days agoHandshake completed45 ms
21 days agoHandshake completed22 ms
24 days agoHandshake completed27 ms
26 days agoHandshake completed32 ms
28 days agoHandshake completed27 ms

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

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.terradev-cloud/quorum and makes no claim about it beyond what these checks measured.