Remote MCP · Endpoint
LiveDataLink MCP server
No. LiveDataLink answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://livedatalink.ai/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.blackboxfoundry/livedatalink
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 693 ms
- Tools exposed
- 381 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- 294 public-data tools across 60 domains; source freshness varies. Free tier.
- Website
- https://livedatalink.ai/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 693 ms |
| 2 days ago | Handshake completed | 632 ms |
| 4 days ago | Handshake completed | 362 ms |
| 5 days ago | Handshake completed | 559 ms |
| 7 days ago | Handshake completed | 175 ms |
| 8 days ago | Handshake completed | 562 ms |
| 9 days ago | Handshake completed | 362 ms |
| 12 days ago | Handshake completed | 350 ms |
| 13 days ago | Handshake completed | 416 ms |
| 15 days ago | Handshake completed | 353 ms |
| 16 days ago | Handshake completed | 598 ms |
| 18 days ago | Handshake completed | 389 ms |
| 19 days ago | Handshake completed | 350 ms |
| 20 days ago | Handshake completed | 314 ms |
| 20 days ago | Handshake completed | 426 ms |
| 21 days ago | Handshake completed | 325 ms |
| 22 days ago | Handshake completed | 544 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 LiveDataLink and makes no claim about it beyond what these checks measured.