Remote MCP · Endpoint

serpgrab: Google Search and Maps MCP server

No. serpgrab: Google Search and Maps answered an MCP handshake 6 days ago.

UpLast checked 6 days ago

Server URL

https://api.serpgrab.com/mcp

The last check completed an MCP handshake.

Registry name
com.serpgrab/google-search
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
311 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Real-time Google search (AI Overview, answer box, People also ask) and Google Maps places.
Listing
From the official MCP registry (active).
Recent checks of serpgrab: Google Search and Maps
CheckedResultHandshake
6 days agoHandshake completed311 ms
7 days agoHandshake completed492 ms
7 days agoHandshake completed350 ms
9 days agoHandshake completed314 ms
10 days agoHandshake completed469 ms
11 days agoHandshake completed359 ms
12 days agoHandshake completed448 ms
13 days agoHandshake completed468 ms
15 days agoHandshake completed491 ms
17 days agoHandshake completed308 ms
20 days agoCredentials required—
22 days agoCredentials required—

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

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 serpgrab: Google Search and Maps and makes no claim about it beyond what these checks measured.