api.reputemap.com
https://api.reputemap.com/api/mcp
active Production-safe Score 89/100 http no auth
At a glance
| Endpoint | https://api.reputemap.com/api/mcp |
|---|---|
| Source | https://api.reputemap.com/mcp |
| Transport | http |
| Tools | 7 |
| Auth | none |
| First seen | 2026-11-07 12:56:59 |
| Last checked | 2026-11-17 21:43:05 |
Observed reliability
| 7-day uptime | 99% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 780 / 991 ms |
| Last successful check | 2026-11-17 21:43:05 |
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:43:05 | ✓ | ✓ | 734 ms | 90 | active |
| 2026-11-17 21:04:32 | ✓ | ✓ | 821 ms | 90 | active |
| 2026-11-17 20:41:06 | ✓ | ✓ | 718 ms | 90 | active |
| 2026-11-17 19:48:44 | ✓ | ✓ | 657 ms | 90 | active |
| 2026-11-17 19:26:30 | ✓ | ✓ | 837 ms | 90 | active |
| 2026-11-17 18:44:28 | ✓ | ✓ | 704 ms | 90 | active |
| 2026-11-17 18:02:05 | ✓ | ✓ | 952 ms | 90 | active |
| 2026-11-17 17:40:23 | ✓ | ✓ | 800 ms | 90 | active |
| 2026-11-17 16:56:14 | ✓ | ✓ | 1168 ms | 86 | active |
| 2026-11-17 16:13:59 | ✓ | ✓ | 833 ms | 90 | active |
| 2026-11-17 15:56:58 | ✓ | ✓ | 1001 ms | 86 | active |
| 2026-11-17 15:41:57 | ✓ | ✓ | 682 ms | 90 | active |
| 2026-11-17 15:26:56 | ✓ | ✓ | 669 ms | 90 | active |
| 2026-11-17 15:11:55 | ✓ | ✓ | 688 ms | 90 | active |
| 2026-11-17 14:56:54 | ✓ | ✓ | 782 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://api.reputemap.com/api/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/api-reputemap-com-api-mcp # JSON