Remote MCP · Endpoint

QuailOS MCP server

No. QuailOS answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.quailos.com/api/mcp/message

The last check completed an MCP handshake.

Registry name
com.quailos/quailos
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
652 ms
Tools exposed
93 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Farm management for poultry, quail & egg farms: flocks, eggs, hatches, orders, tasks, calendar.
Website
https://www.quailos.com/llms.txt
Listing
From the official MCP registry (active).
Recent checks of QuailOS
CheckedResultHandshake
1 hour agoHandshake completed652 ms
2 days agoHandshake completed440 ms
5 days agoHandshake completed291 ms
7 days agoHandshake completed426 ms
9 days agoHandshake completed344 ms
11 days agoHandshake completed383 ms
13 days agoHandshake completed336 ms
15 days agoHandshake completed193 ms
17 days agoHandshake completed188 ms
19 days agoHandshake completed229 ms
20 days agoHandshake completed200 ms
21 days agoHandshake completed180 ms
23 days agoHandshake completed304 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with QuailOS and makes no claim about it beyond what these checks measured.