Remote MCP · Endpoint

Leads Fresh DB MCP server

No. Leads Fresh DB answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://leadsfreshdb.com/mcp

The last check completed an MCP handshake.

Registry name
com.leadsfreshdb/leads-fresh-db
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
298 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Live prices and quotes for fresh, filtered phone leads in any country, plus a free 200-number sample
Listing
From the official MCP registry (active).
Recent checks of Leads Fresh DB
CheckedResultHandshake
5 hours agoHandshake completed298 ms
10 hours agoHandshake completed239 ms
2 days agoHandshake completed453 ms
4 days agoHandshake completed274 ms
7 days agoHandshake completed235 ms
9 days agoHandshake completed509 ms
11 days agoHandshake completed416 ms
13 days agoHandshake completed395 ms
15 days agoHandshake completed436 ms
18 days agoHandshake completed183 ms
20 days agoHandshake completed210 ms
21 days agoHandshake completed399 ms
23 days agoHandshake completed187 ms

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

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