Remote MCP · Endpoint
io.github.DataLeadsPRO/company-enrichment MCP server
No. io.github.DataLeadsPRO/company-enrichment answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://data.dataleads.pro/mcp/company-enrichment
The last check completed an MCP handshake.
- Registry name
- io.github.DataLeadsPRO/company-enrichment
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 291 ms
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Enrich any domain into a full company profile with firmographics and buying signals.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 291 ms |
| 18 hours ago | Handshake completed | 294 ms |
| 2 days ago | Handshake completed | 420 ms |
| 3 days ago | Handshake completed | 309 ms |
| 4 days ago | Handshake completed | 294 ms |
| 5 days ago | Handshake completed | 311 ms |
| 6 days ago | Handshake completed | 417 ms |
| 7 days ago | Handshake completed | 302 ms |
| 10 days ago | Handshake completed | 299 ms |
| 13 days ago | Handshake completed | 466 ms |
| 15 days ago | Handshake completed | 303 ms |
| 17 days ago | Handshake completed | 285 ms |
| 19 days ago | Handshake completed | 311 ms |
| 21 days ago | Handshake completed | 301 ms |
| 23 days ago | Handshake completed | 313 ms |
| 25 days ago | Handshake completed | 306 ms |
| 27 days ago | Handshake completed | 633 ms |
| 28 days ago | Handshake completed | 328 ms |
| 29 days ago | Handshake completed | 417 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 io.github.DataLeadsPRO/company-enrichment and makes no claim about it beyond what these checks measured.