Remote MCP · Endpoint

Deeplead MCP server

No. Deeplead answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.deeplead.io/api/mcp

The last check completed an MCP handshake.

Registry name
io.deeplead/deeplead
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.64 s
Tools exposed
13 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Find local businesses, companies and decision makers with verified emails for B2B outreach.
Listing
From the official MCP registry (active).
Recent checks of Deeplead
CheckedResultHandshake
1 hour agoHandshake completed1.64 s
2 days agoHandshake completed409 ms
4 days agoHandshake completed380 ms
6 days agoHandshake completed1.98 s
7 days agoHandshake completed395 ms
9 days agoHandshake completed379 ms
10 days agoHandshake completed572 ms
11 days agoHandshake completed1.87 s
14 days agoHandshake completed425 ms
15 days agoHandshake completed54 ms
17 days agoHandshake completed58 ms
19 days agoHandshake completed51 ms
20 days agoHandshake completed46 ms
21 days agoHandshake completed61 ms
22 days agoHandshake completed111 ms

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

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 Deeplead and makes no claim about it beyond what these checks measured.