Remote MCP · Endpoint
HasData Google Maps MCP server
No. HasData Google Maps answered an MCP handshake 13 minutes ago.
UpLast checked 13 minutes ago
Server URL
https://mcp.hasdata.com/api/mcp?apis=google_maps
The last check completed an MCP handshake.
- Registry name
- com.hasdata/google-maps
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 173 ms
- Tools exposed
- 6 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Google Maps places, reviews, contributor history, photos and posts as JSON. No Google Cloud.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 13 minutes ago | Handshake completed | 173 ms |
| 2 days ago | Handshake completed | 47 ms |
| 4 days ago | Handshake completed | 120 ms |
| 5 days ago | Handshake completed | 152 ms |
| 7 days ago | Handshake completed | 123 ms |
| 8 days ago | Handshake completed | 123 ms |
| 9 days ago | Handshake completed | 44 ms |
| 12 days ago | Credentials required | — |
| 13 days ago | Credentials required | — |
| 15 days ago | Credentials required | — |
| 17 days ago | Credentials required | — |
| 18 days ago | Credentials required | — |
| 19 days ago | Credentials required | — |
| 20 days ago | Credentials required | — |
| 20 days ago | Credentials required | — |
| 22 days ago | Credentials required | — |
| 23 days ago | Credentials required | — |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
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 HasData Google Maps and makes no claim about it beyond what these checks measured.