Remote MCP · Endpoint
Gemot Deliberation Server MCP server
No. Gemot Deliberation Server answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://gemot.dev/mcp
The last check completed an MCP handshake.
- Registry name
- dev.gemot/gemot
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 101 ms
- Tools exposed
- 7 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Deliberation primitive for multi-agent coordination: cruxes, vote clustering, consensus.
- Website
- https://gemot.dev/
- Repository
- https://github.com/justinstimatze/gemot
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 101 ms |
| 1 day ago | Handshake completed | 148 ms |
| 2 days ago | Handshake completed | 119 ms |
| 3 days ago | Handshake completed | 198 ms |
| 4 days ago | Handshake completed | 264 ms |
| 5 days ago | Handshake completed | 177 ms |
| 6 days ago | Handshake completed | 138 ms |
| 9 days ago | Handshake completed | 124 ms |
| 12 days ago | Handshake completed | 114 ms |
| 14 days ago | Handshake completed | 199 ms |
| 16 days ago | Handshake completed | 186 ms |
| 18 days ago | Handshake completed | 142 ms |
| 20 days ago | Handshake completed | 118 ms |
| 22 days ago | Handshake completed | 120 ms |
| 24 days ago | Handshake completed | 121 ms |
| 26 days ago | Handshake completed | 208 ms |
| 27 days ago | Handshake completed | 122 ms |
| 28 days ago | Handshake completed | 126 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 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 Gemot Deliberation Server and makes no claim about it beyond what these checks measured.