Remote MCP · Endpoint

GMaps Lead Finder MCP server

No. GMaps Lead Finder answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://gmapsleadfinder.com/mcp

The last check completed an MCP handshake.

Registry name
com.gmapsleadfinder/gmaps-lead-finder
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
420 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Scrape Google Maps business leads, reviews, and photos via hosted Remote MCP.
Listing
From the official MCP registry (active).
Recent checks of GMaps Lead Finder
CheckedResultHandshake
2 hours agoHandshake completed420 ms
2 days agoHandshake completed639 ms
4 days agoHandshake completed484 ms
5 days agoHandshake completed351 ms
7 days agoHandshake completed694 ms
8 days agoHandshake completed70 ms
9 days agoHandshake completed443 ms
12 days agoHandshake completed529 ms
13 days agoHandshake completed345 ms
15 days agoHandshake completed258 ms
17 days agoHandshake completed299 ms
18 days agoHandshake completed502 ms
19 days agoHandshake completed484 ms
20 days agoHandshake completed513 ms
20 days agoHandshake completed295 ms
21 days agoCredentials required—

The last 16 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 GMaps Lead Finder and makes no claim about it beyond what these checks measured.