# Is it legit? Reviews trust checker (remote · legitreviews.ai)

Scores whether a business's Google Maps reviews are genuine. Your agent collects them, we judge.

- Trust score: 68/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `legitreviews.ai`: 68/100 (this document), [markdown](https://verifymcp.io/servers/ai-legitreviews-legitreviews/legitreviews.md), [page](https://verifymcp.io/servers/ai-legitreviews-legitreviews/legitreviews)

## Channel facts

- Endpoint: `https://legitreviews.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.0.0`

## 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-11-05.

- **Endpoint Security**: 77/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2104 tokens (~300/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 76% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Is it legit? Reviews trust checker MCP server?

Is it legit? Reviews trust checker is a hosted endpoint at https://legitreviews.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http ai-legitreviews-legitreviews 'https://legitreviews.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-legitreviews-legitreviews": {
      "url": "https://legitreviews.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-legitreviews-legitreviews": {
      "type": "http",
      "url": "https://legitreviews.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-legitreviews-legitreviews]
url = "https://legitreviews.ai/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add ai-legitreviews-legitreviews --url 'https://legitreviews.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-legitreviews-legitreviews:
    url: "https://legitreviews.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-legitreviews-legitreviews": {
      "Transport": "http",
      "Url": "https://legitreviews.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-legitreviews-legitreviews -t streamable-http -u 'https://legitreviews.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-legitreviews-legitreviews": {
      "type": "http",
      "url": "https://legitreviews.ai/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-11-05 (score 68, +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-11-04 (score 67, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-03 (score 67)

First indexed and scored.

## MCP tools (7)

### `describe_review_source` (~109 tokens)

Which review fields to collect for a platform

Read this BEFORE scraping. Returns, per platform, the exact submission format: identity fields for the listing, the per-review fields (required vs optional; everything required is visible on the review card), where each lives on the platform's pages, the sort-by-newest and 500-most-recent rules, an example payload, and how to deliver it. Without a platform it lists the supported platforms. Only Google Maps exists today.

Input parameters:

- `platform` (string): Platform to describe (default: all).

### `check_place` (~143 tokens)

Is this place already analyzed?

Call first. Resolves a Google Maps link or place_id and reports whether a trust result is cached, how fresh it is, and a recommendation: use the cached result, or collect and submit the reviews (also when a cached single-source result would benefit from your corroboration). Never contacts Google.

Input parameters:

- `place_id` (string): Google's feature id for the place (0x…:0x…, the '!1s' segment of a /maps/place URL).
- `url` (string): Alternative to place_id: a Google Maps place link (long /maps/place/… URL or ?cid= link). Share short-links cannot be resolved; open them first.

### `begin_submission` (~236 tokens)

Start a review submission (get an upload URL)

Reserves a submission and returns an upload_url. POST the complete JSON payload (format from describe_review_source) to it from your own environment or the user's browser; the HTTP response is the trust report. The URL is a secret that completes the submission under YOUR identity whoever posts to it, so the POST needs no key. Alternatively feed the same submission_id to submit_reviews in inline chunks. Pending submissions expire after 2 hours (or are closed as superseded when you one-shot the same place instead).

Input parameters:

- `agent` (string): Your agent/product name, recorded as the submission's provenance (e.g. 'Muse', 'Claude Code').
- `expected_reviews` (integer): The review count the listing shows, if known.
- `place_id` (string): Google's feature id for the place (0x…:0x…, the '!1s' segment of a /maps/place URL).
- `platform` (string, required)
- `url` (string): Alternative to place_id: a Google Maps place link (long /maps/place/… URL or ?cid= link). Share short-links cannot be resolved; open them first.

### `submit_reviews` (~500 tokens)

Submit review data inline

Submit the review feed inside the tool call. Without submission_id this is a one-shot submission of the whole payload (fine up to about 150 reviews). For more, call begin_submission, then send chunks of up to 150 reviews each with the same submission_id and final=false; send final=true with the last chunk (the identity fields may arrive with any chunk). Use this only when you cannot POST to the upload_url yourself (no page fetch, no curl): retyping reviews you already hold in a page or script is slow and error-prone. Returns the trust report when finalized.

Input parameters:

- `address` (string)
- `agent` (string): Your agent/product name, recorded as the submission's provenance (e.g. 'Muse', 'Claude Code').
- `capped` (boolean): True when deliberately stopped at 5000+ reviews of a much larger listing.
- `cid` (string): Decimal cid from a ?cid= link, when placeId is unknown.
- `complete` (boolean): True only if the review list reached its end; false for a newest-first window of the 500 most recent reviews (at least 200).
- `final` (boolean): With submission_id: true when this is the last chunk (default true).
- `lat` (number)
- `listedRating` (number): The star rating Google displays.
- `listedReviews` (integer): The review count Google displays on the listing.
- `lon` (number)
- `mapsUrl` (string)
- `name` (string)
- `placeId` (string): Google feature id 0x…:0x…
- `platform` (string): Which review source the data follows (describe_review_source).
- `pulledAt` (string): ISO 8601 datetime of collection (relative dates are resolved against it).
- `ratingHistogram` (array): The five-bar rating histogram next to the star rating, as review counts for 1, 2, 3, 4 and 5 stars IN THAT ORDER (Google draws 5 stars first; reverse what you read). Each bar's accessibility label or…
- `reviews` (array)
- `sort` (string): The order collected in: 'newest' (required for a window) or 'relevant'.
- `submission_id` (string): From begin_submission (omit for a one-shot submission).

### `finalize_submission` (~57 tokens)

Finalize a submission / fetch its report

For a submission fed by inline chunks: validates, scores, stores and returns the report. For one already uploaded to its upload_url: returns the stored report. Pending with nothing uploaded yet: says so.

Input parameters:

- `submission_id` (string, required)

### `get_place_trust` (~184 tokens)

Trust analysis of a place's reviews (cached)

The cached fraud analysis for a place: verdict (looks_legit / not_sure / past_manipulation / inflated / manipulated) with its label and a one-sentence summary, letter grade, 0-100 trust score, the adjusted rating credible reviewers actually give (vs the headline average), reviewer-mix tiers, review-injection statistics, cross-business duplicate-review evidence, red flags, and provenance. Cache only: on a miss, collect and submit the reviews (see check_place).

Input parameters:

- `place_id` (string): Google's feature id for the place (0x…:0x…, the '!1s' segment of a /maps/place URL).
- `url` (string): Alternative to place_id: a Google Maps place link (long /maps/place/… URL or ?cid= link). Share short-links cannot be resolved; open them first.

### `list_scored_places` (~111 tokens)

Browse the directory of analyzed places

The ranked directory of places already analyzed for review fraud, best adjusted rating first (what the site's home and city pages show). 25 per page. Optional city or curated-list filter; the response lists the available cities/lists and their counts.

Input parameters:

- `city` (string): Limit to one city's places (a slug from the `cities` field of a previous response).
- `list` (string): Limit to one curated list's places.
- `page` (number): Page number, 0-based.

## Diagnostics

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

## Score history

- 2026-11-05: 68
- 2026-11-04: 67
- 2026-11-03: 67

## Common questions

### What is the Is it legit? Reviews trust checker MCP server?

Is it legit? Reviews trust checker is an MCP server listed in the public MCP registry as ai.legitreviews/legitreviews. Scores whether a business's Google Maps reviews are genuine. Your agent collects them, we judge. This page covers its hosted endpoint (https://legitreviews.ai/mcp).

### Is the Is it legit? Reviews trust checker MCP server safe to use?

Is it legit? Reviews trust checker scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Is it legit? Reviews trust checker MCP server expose?

Is it legit? Reviews trust checker exposes 7 tools: describe_review_source, check_place, begin_submission, submit_reviews, finalize_submission, and 2 more. Their descriptions and schemas cost roughly 1,340 tokens of context every time the server is loaded.

### Does the Is it legit? Reviews trust checker MCP server require authentication?

No. We connected to Is it legit? Reviews trust checker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Is it legit? Reviews trust checker MCP server still maintained?

Is it legit? Reviews trust checker is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Is it legit? Reviews trust checker MCP server?

VerifyMCP ran 13 checks on Is it legit? Reviews trust checker, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://legitreviews.ai/mcp
- Website: https://legitreviews.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-legitreviews-legitreviews/legitreviews.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-legitreviews-legitreviews/legitreviews/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ai-legitreviews-legitreviews/legitreviews.json
- HTML version of this page: https://verifymcp.io/servers/ai-legitreviews-legitreviews/legitreviews