# ReputeMap (remote · api.reputemap.com)

Read and filter your Google Business Profile reviews, get stats, and send review requests.

- Trust score: 73/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.reputemap.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/com-reputemap-reputemap/api.md), [page](https://verifymcp.io/servers/com-reputemap-reputemap/api)
- npm · `@reputemap/mcp`: 39/100, [markdown](https://verifymcp.io/servers/com-reputemap-reputemap/reputemap-mcp.md), [page](https://verifymcp.io/servers/com-reputemap-reputemap/reputemap-mcp)

## Channel facts

- Endpoint: `https://api.reputemap.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 424 tokens (~84/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 58% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-reputemap-reputemap https://api.reputemap.com/mcp
```

### Codex

```toml
[mcp_servers.com-reputemap-reputemap]
url = "https://api.reputemap.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-reputemap-reputemap": {
      "type": "remote",
      "url": "https://api.reputemap.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-reputemap-reputemap --url https://api.reputemap.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-reputemap-reputemap:
    url: "https://api.reputemap.com/mcp"
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 71, +5)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 66)

First indexed and scored.

## MCP tools (5)

### `list_locations` (~28 tokens)

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

### `list_reviews` (~124 tokens)

List Google reviews for the org (newest first) with the published reply text inlined. Filter by location, star-rating range, replied/unreplied, or a trailing day window.

Input parameters:

- `limit` (integer)
- `location_id` (string): UUID from list_locations; omit for all locations
- `offset` (integer)
- `rating_max` (integer)
- `rating_min` (integer)
- `since_days` (integer): only reviews from the last N days
- `unanswered_only` (boolean): true = only reviews without an owner reply

### `get_review_stats` (~69 tokens)

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).

Input parameters:

- `days` (integer)
- `location_id` (string): UUID from list_locations; omit for all locations

### `send_review_request` (~95 tokens)

Send ONE review-request email to a real customer, through ReputeMap's campaign engine (respects unsubscribes and the suppression list; idempotent per campaign). This emails a real person - only use it when the user explicitly asks to request a review.

Input parameters:

- `email` (string, required): customer email address
- `location_id` (string, required): UUID from list_locations
- `name` (string): customer name (optional)

### `get_usage` (~26 tokens)

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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-reputemap-reputemap/api#diagnostics

## Score history

- 2026-08-03: 73
- 2026-08-02: 73
- 2026-08-01: 72
- 2026-07-31: 71
- 2026-07-30: 66

## Links

- Remote endpoint: https://api.reputemap.com/mcp
- Authorisation metadata: https://api.reputemap.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/reputemap/mcp
- Website: https://reputemap.com/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-reputemap-reputemap/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-reputemap-reputemap/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-reputemap-reputemap/api
