Remote MCP · Endpoint

SERVIQO Agents MCP server

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

DownLast checked 1 hour ago

Server URL

https://agents.serviqo.co/mcp

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

Registry name
io.github.jdsleek/distributionos
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
12 tools
Uptime, last 30 days
84.6% from 13 checks
Described by its publisher as
SERVIQO Agents: Founding Agent network (DistributionOS). Tracked Rhapsody share links. Pilot.
Listing
From the official MCP registry (active).
Recent checks of SERVIQO Agents
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
3 days agoFailed - the server returned an HTTP error—
13 days agoHandshake completed265 ms
14 days agoHandshake completed254 ms
15 days agoHandshake completed265 ms
16 days agoHandshake completed258 ms
18 days agoHandshake completed275 ms
18 days agoHandshake completed288 ms
19 days agoHandshake completed272 ms
21 days agoHandshake completed255 ms
22 days agoHandshake completed269 ms
25 days agoHandshake completed279 ms
27 days agoHandshake completed252 ms

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

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