Remote MCP · Endpoint
@imqueue MCP server
No. @imqueue answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.imqueue.org/mcp
The last check completed an MCP handshake.
- Registry name
- org.imqueue/mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 171 ms
- Tools exposed
- 7 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Search @imqueue docs and scaffold typed services & clients from your AI coding agent.
- Website
- https://imqueue.org/mcp/
- Repository
- https://github.com/imqueue/mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 171 ms |
| 1 day ago | Handshake completed | 188 ms |
| 2 days ago | Handshake completed | 137 ms |
| 3 days ago | Handshake completed | 164 ms |
| 4 days ago | Handshake completed | 209 ms |
| 5 days ago | Handshake completed | 168 ms |
| 6 days ago | Handshake completed | 378 ms |
| 8 days ago | Handshake completed | 177 ms |
| 11 days ago | Handshake completed | 141 ms |
| 13 days ago | Handshake completed | 207 ms |
| 16 days ago | Handshake completed | 229 ms |
| 18 days ago | Handshake completed | 78 ms |
| 20 days ago | Handshake completed | 152 ms |
| 22 days ago | Handshake completed | 133 ms |
| 24 days ago | Handshake completed | 249 ms |
| 26 days ago | Handshake completed | 230 ms |
| 27 days ago | Handshake completed | 193 ms |
| 29 days ago | Handshake completed | 264 ms |
| 29 days ago | Handshake completed | 435 ms |
The last 19 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 @imqueue and makes no claim about it beyond what these checks measured.