Remote MCP · Endpoint

Signal Leads MCP server

No. Signal Leads answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://leads.botrecipe.com/mcp

The last check completed an MCP handshake.

Registry name
com.botrecipe/leads
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
230 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
25 sales leads with a real funding, hiring or tech signal, source link and draft message. $19.
Listing
From the official MCP registry (active).
Recent checks of Signal Leads
CheckedResultHandshake
20 minutes agoHandshake completed230 ms
9 days agoHandshake completed226 ms
9 days agoHandshake completed177 ms
11 days agoHandshake completed370 ms
12 days agoHandshake completed219 ms
13 days agoHandshake completed149 ms
14 days agoHandshake completed308 ms
15 days agoHandshake completed139 ms
16 days agoHandshake completed180 ms
19 days agoHandshake completed120 ms
21 days agoHandshake completed383 ms
24 days agoHandshake completed124 ms
26 days agoHandshake completed113 ms
28 days agoHandshake completed264 ms

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