Remote MCP · Endpoint

Lead Friendly product info MCP server

No. Lead Friendly product info answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://www.leadfriendly.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.leadfriendly/lead-friendly-info
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
420 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Lead Friendly pricing, industries and capabilities for AI agents, plus demo and lead hand-off
Listing
From the official MCP registry (active).
Recent checks of Lead Friendly product info
CheckedResultHandshake
5 hours agoHandshake completed420 ms
9 days agoHandshake completed236 ms
10 days agoHandshake completed359 ms
11 days agoHandshake completed263 ms
12 days agoHandshake completed304 ms
14 days agoHandshake completed226 ms
14 days agoHandshake completed265 ms
15 days agoHandshake completed250 ms
17 days agoHandshake completed246 ms
19 days agoHandshake completed322 ms
21 days agoHandshake completed164 ms
24 days agoHandshake completed110 ms
26 days agoHandshake completed146 ms
28 days agoHandshake completed158 ms

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