Remote MCP · Endpoint

Lyre Leads MCP server

No. Lyre Leads answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://lyreleads.com/mcp

The last check completed an MCP handshake.

Registry name
com.lyreleads/lyre-leads
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
157 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Every business of a kind in a city, from Google Maps, read from its website, with verified emails.
Listing
From the official MCP registry (active).
Recent checks of Lyre Leads
CheckedResultHandshake
13 minutes agoHandshake completed157 ms
10 days agoHandshake completed178 ms
10 days agoHandshake completed189 ms
11 days agoHandshake completed193 ms
13 days agoHandshake completed146 ms
14 days agoHandshake completed174 ms
14 days agoHandshake completed144 ms
15 days agoHandshake completed198 ms
17 days agoHandshake completed170 ms
19 days agoHandshake completed166 ms
21 days agoHandshake completed688 ms
24 days agoHandshake completed142 ms
26 days agoHandshake completed164 ms
28 days agoHandshake completed158 ms

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

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