https://mcp.beatanalytics.org/maps/mcp ↗
Retrieve Google Maps reviews with full pagination, multiple sort modes, and date filtering. This MCP server also provides place search, place details, and a URL resolver that converts Google Maps or Yelp URLs into place IDs — so you can go from a link to structured data in one step. Typical use cases include analyzing customer feedback for a location, comparing review sentiment across competing businesses, monitoring review trends over time, and enriching CRM data with place details. To get started, create an API key at [beatanalytics.org/maps](https://beatanalytics.org/maps) and add it to your server configuration.
Google Maps Businesses and Reviews is a remote MCP server published at mcp.beatanalytics.org. It has been probed 6 times since 9/10/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 323 ms, placing it among the faster endpoints. It offers a narrow, focused set of 4 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
search — Parameter requirements (lat/lon vs location name) are mentioned but not explicitly labeled as required/optional.resolve — Input types (e.g., URL formats) are described but lack explicit schema validation details.details — Truncated description may omit critical parameter details (e.g., required Place ID).Risk: medium
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/beatanalytics-maps)<a href="https://mcpmetrics.io/servers/beatanalytics-maps"><img src="https://mcpmetrics.io/badge/beatanalytics/maps/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-11 13:13:33 | Legacy | 400 | 131 | 200 | 129 | 2025-11-25 |
| 2026-09-11 11:20:19 | Legacy | 400 | 383 | 200 | 386 | 2025-11-25 |
| 2026-09-11 09:28:19 | Legacy | 400 | 154 | 200 | 153 | 2025-11-25 |
| 2026-09-11 07:35:54 | Legacy | 400 | 133 | 200 | 134 | 2025-11-25 |
| 2026-09-11 05:44:28 | Legacy | 400 | 413 | 200 | 412 | 2025-11-25 |
| 2026-09-10 21:16:35 | Auth-gated | 401 | 323 | 401 | 346 | — |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.