Marketing

reputemap.com

Manages business locations and Google reviews, including listing, stats, and sending review requests to customers.

1 endpoint7 known toolsFirst detected July 31, 2026Last detected September 6, 2026

ENDPOINT 1

https://api.reputemap.com/mcp

No auth detected

MCP server metadata

Name: reputemap
Version: 1.1

Capabilities

tools

Server instructions

ReputeMap manages Google reviews for local businesses. Tools cover the org behind the API key: list locations, read reviews (filterable), get review stats, draft AI replies, publish an approved reply to Google, send a review-request email, and check API credit usage. publish_reply is public and customer-visible - only call it with text the user has explicitly approved. Billable tool calls share the org's monthly API credits (default 1000/month) with the REST API. Docs: https://reputemap.com/docs/mcp

Known tools 7

list_locations

List every business location this ReputeMap org manages, with ids to use in the other tools.

Inferred read-only

list_reviews

List Google reviews for the org (newest first) with the published reply text inlined.

Inferred read-only

get_review_stats

Review stats per location and org totals: review counts, average rating, 1-5 star breakdown, unanswered count, and activity in the trailing window (default 30 days).

Inferred read-only

send_review_request

Send ONE review-request email to a real customer, through ReputeMap's campaign engine (respects unsubscribes and the suppression list).

Potential side effects

draft_reply

Generate 2-3 reply drafts for one review using ReputeMap's tuned generator (the same one the app uses), and save the draft so it appears in the app's editor.

Inferred read-only

publish_reply

PUBLISH a reply to this review's public Google profile.

Potential side effects

get_usage

Current month's API credit usage for this org (shared between the REST API and MCP tools).

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.reputemap]
url = "https://api.reputemap.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "reputemap": {
      "type": "http",
      "url": "https://api.reputemap.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: reputemap
Remote MCP URL: https://api.reputemap.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "reputemap": {
      "url": "https://api.reputemap.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "reputemap": {
      "type": "http",
      "url": "https://api.reputemap.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "reputemap",
  "transport": "streamable-http",
  "url": "https://api.reputemap.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.