Remote MCP · Endpoint
io.github.DataLeadsPRO/jobs-search-multi MCP server
No. io.github.DataLeadsPRO/jobs-search-multi answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://data.dataleads.pro/mcp/jobs-search-multi
The last check completed an MCP handshake.
- Registry name
- io.github.DataLeadsPRO/jobs-search-multi
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 284 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Search job postings across Indeed, LinkedIn, and more from one request - titles, companies
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 284 ms |
| 2 days ago | Handshake completed | 303 ms |
| 4 days ago | Handshake completed | 289 ms |
| 5 days ago | Handshake completed | 282 ms |
| 7 days ago | Handshake completed | 309 ms |
| 8 days ago | Handshake completed | 170 ms |
| 9 days ago | Handshake completed | 126 ms |
| 12 days ago | Handshake completed | 115 ms |
| 14 days ago | Handshake completed | 120 ms |
| 15 days ago | Handshake completed | 101 ms |
| 17 days ago | Handshake completed | 401 ms |
| 18 days ago | Handshake completed | 100 ms |
| 19 days ago | Handshake completed | 124 ms |
| 20 days ago | Handshake completed | 323 ms |
| 20 days ago | Handshake completed | 699 ms |
| 22 days ago | Handshake completed | 107 ms |
| 23 days ago | Handshake completed | 103 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 io.github.DataLeadsPRO/jobs-search-multi and makes no claim about it beyond what these checks measured.