Remote MCP · Endpoint

Deeplead MCP server

No. Deeplead answered an MCP handshake 35 minutes ago.

UpLast checked 35 minutes 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
2.60 s
Tools exposed
31 tools
Uptime, last 30 days
100% from 14 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
35 minutes agoHandshake completed2.60 s
9 days agoHandshake completed394 ms
10 days agoHandshake completed387 ms
11 days agoHandshake completed399 ms
12 days agoHandshake completed406 ms
14 days agoHandshake completed369 ms
14 days agoHandshake completed375 ms
15 days agoHandshake completed185 ms
17 days agoHandshake completed393 ms
19 days agoHandshake completed476 ms
21 days agoHandshake completed425 ms
24 days agoHandshake completed396 ms
26 days agoHandshake completed411 ms
28 days agoHandshake completed1.64 s

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

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.