ReputeMap MCP server — manage Google Business Profile reviews from Claude, Curso
ReputeMap MCP server — manage Google Business Profile reviews from Claude, Cursor or any MCP client. Hosted Streamable HTTP endpoint, official registry: com.reputemap/reputemap
active Production-safe Score 90/100 http no auth
At a glance
| Endpoint | https://api.reputemap.com/mcp |
|---|---|
| Source | https://github.com/reputemap-com/mcp |
| Transport | http |
| Tools | 7 |
| Auth | none |
| First seen | 2026-11-07 00:08:05 |
| Last checked | 2026-11-17 21:51:41 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 770 / 1107 ms |
| Last successful check | 2026-11-17 21:51:41 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (7)
list_locations— List every business location this ReputeMap org manages, with ids to use in the other tools.list_reviews— List Google reviews for the org (newest first) with the published reply text inlined. Filter by location, star-rating range, replied/unrepliget_review_stats— Review stats per location and org totals: review counts, average rating, 1-5 star breakdown, unanswered count, and activity in the trailingsend_review_request— Send ONE review-request email to a real customer, through ReputeMap's campaign engine (respects unsubscribes and the suppression list). Thisdraft_reply— Generate 2-3 reply drafts for one review using ReputeMap's tuned generator (the same one the app uses, with the business's saved voice and spublish_reply— PUBLISH a reply to this review's public Google profile. This is a public, customer-visible action - call it ONLY when the user has explicitlget_usage— Current month's API credit usage for this org (shared between the REST API and MCP tools).
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:51:41 | ✓ | ✓ | 651 ms | 90 | active |
| 2026-11-17 21:36:31 | ✓ | ✓ | 725 ms | 90 | active |
| 2026-11-17 21:21:15 | ✓ | ✓ | 794 ms | 90 | active |
| 2026-11-17 21:06:06 | ✓ | ✓ | 660 ms | 90 | active |
| 2026-11-17 20:50:44 | ✓ | ✓ | 652 ms | 90 | active |
| 2026-11-17 20:35:39 | ✓ | ✓ | 657 ms | 90 | active |
| 2026-11-17 20:20:38 | ✓ | ✓ | 878 ms | 90 | active |
| 2026-11-17 20:05:37 | ✓ | ✓ | 670 ms | 90 | active |
| 2026-11-17 19:49:51 | ✓ | ✓ | 739 ms | 90 | active |
| 2026-11-17 19:34:44 | ✓ | ✓ | 644 ms | 90 | active |
| 2026-11-17 19:19:35 | ✓ | ✓ | 776 ms | 90 | active |
| 2026-11-17 19:04:19 | ✓ | ✓ | 1119 ms | 87 | active |
| 2026-11-17 18:49:07 | ✓ | ✓ | 626 ms | 90 | active |
| 2026-11-17 18:33:55 | ✓ | ✓ | 725 ms | 90 | active |
| 2026-11-17 18:18:45 | ✓ | ✓ | 851 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://api.reputemap.com/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/api-reputemap-com-mcp # JSON