Remote MCP · Endpoint

Disco MCP server

No. Disco answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
214 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Find novel, statistically validated patterns in tabular data — hypothesis-free.
Listing
From the official MCP registry (active).
Recent checks of Disco
CheckedResultHandshake
1 hour agoHandshake completed214 ms
2 days agoHandshake completed234 ms
4 days agoHandshake completed506 ms
5 days agoHandshake completed407 ms
7 days agoHandshake completed235 ms
8 days agoHandshake completed500 ms
9 days agoHandshake completed248 ms
12 days agoHandshake completed800 ms
13 days agoHandshake completed505 ms
15 days agoHandshake completed162 ms
16 days agoHandshake completed1.04 s
17 days agoHandshake completed187 ms
18 days agoHandshake completed655 ms
19 days agoHandshake completed309 ms
20 days agoHandshake completed434 ms
21 days agoHandshake completed577 ms
22 days agoHandshake completed291 ms

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

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.