Remote MCP · Endpoint
Disco MCP server
No. Disco answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://disco.leap-labs.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.leap-labs/discovery-engine
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 322 ms
- Tools exposed
- 14 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Find novel, statistically validated patterns in tabular data — hypothesis-free.
- Website
- https://www.leap-labs.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 322 ms |
| 19 hours ago | Handshake completed | 237 ms |
| 2 days ago | Handshake completed | 212 ms |
| 3 days ago | Handshake completed | 496 ms |
| 4 days ago | Handshake completed | 604 ms |
| 5 days ago | Handshake completed | 5.39 s |
| 6 days ago | Handshake completed | 184 ms |
| 7 days ago | Handshake completed | 688 ms |
| 10 days ago | Handshake completed | 167 ms |
| 13 days ago | Handshake completed | 1.07 s |
| 15 days ago | Handshake completed | 3.39 s |
| 17 days ago | Handshake completed | 188 ms |
| 19 days ago | Handshake completed | 4.50 s |
| 21 days ago | Handshake completed | 214 ms |
| 23 days ago | Handshake completed | 234 ms |
| 25 days ago | Handshake completed | 506 ms |
| 27 days ago | Handshake completed | 407 ms |
| 28 days ago | Handshake completed | 235 ms |
| 29 days ago | Handshake completed | 500 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.
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 Disco and makes no claim about it beyond what these checks measured.