Remote MCP · Endpoint

io.github.DataLeadsPRO/google-serp MCP server

No. io.github.DataLeadsPRO/google-serp answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://data.dataleads.pro/mcp/google-serp

The last check completed an MCP handshake.

Registry name
io.github.DataLeadsPRO/google-serp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
332 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Structured Google search, news, and local results at scale - organic results, news, and local packs
Repository
https://github.com/DataLeadsPRO/google-serp
Listing
From the official MCP registry (active).
Recent checks of io.github.DataLeadsPRO/google-serp
CheckedResultHandshake
1 hour agoHandshake completed332 ms
1 day agoHandshake completed466 ms
2 days agoHandshake completed282 ms
3 days agoHandshake completed327 ms
4 days agoHandshake completed477 ms
5 days agoHandshake completed311 ms
6 days agoHandshake completed327 ms
9 days agoHandshake completed285 ms
11 days agoHandshake completed284 ms
14 days agoHandshake completed284 ms
16 days agoHandshake completed307 ms
18 days agoHandshake completed356 ms
20 days agoHandshake completed304 ms
22 days agoHandshake completed298 ms
24 days agoHandshake completed330 ms
26 days agoHandshake completed374 ms
28 days agoHandshake completed293 ms
29 days agoHandshake completed300 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with io.github.DataLeadsPRO/google-serp and makes no claim about it beyond what these checks measured.