# Is it legit? Reviews trust checker (remote · isitlegitreviews.com)

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

- Trust score: 36/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `isitlegitreviews.com`: 36/100 (this document), [markdown](https://verifymcp.io/servers/com-isitlegitreviews-isitlegit/isitlegitreviews.md), [page](https://verifymcp.io/servers/com-isitlegitreviews-isitlegit/isitlegitreviews)

## Channel facts

- Endpoint: `https://isitlegitreviews.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- 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-21.

- **Endpoint Security**: 91/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata.
  - 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.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- **Schema Quality & AI Usability**: 0/100
  - Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Tool Safety**: 0/100
  - Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Capabilities**: 0/100
  - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

**Unverified: 6 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## 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://isitlegitreviews.com/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 com-isitlegitreviews-isitlegit 'https://isitlegitreviews.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-isitlegitreviews-isitlegit": {
      "url": "https://isitlegitreviews.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-isitlegitreviews-isitlegit": {
      "type": "http",
      "url": "https://isitlegitreviews.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-isitlegitreviews-isitlegit]
url = "https://isitlegitreviews.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-isitlegitreviews-isitlegit --url 'https://isitlegitreviews.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-isitlegitreviews-isitlegit:
    url: "https://isitlegitreviews.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-isitlegitreviews-isitlegit": {
      "Transport": "http",
      "Url": "https://isitlegitreviews.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-isitlegitreviews-isitlegit -t streamable-http -u 'https://isitlegitreviews.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-isitlegitreviews-isitlegit": {
      "type": "http",
      "url": "https://isitlegitreviews.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-11-12 (score 36, −34)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → unverified
- [security regression] Stability: 0.20 → unverified
- [security improvement] Authorization: partial → pass
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-11-11 (score 70, +1)

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

### 2026-11-09 (score 69, +1)

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

### 2026-11-08 (score 68, +32)

- [security regression] Authorization: pass → partial
- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 2107 → 2811
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: behind authorisation → reachable
- [functional improvement] Stability: unverified → 0.10
- [functional improvement] Tool coverage: unverified → 100
- [functional] New tool “fetch_place_reviews”
- [functional] New tool “submit_takeaways”
- [cosmetic] “submit_reviews” added an optional parameter “takeaways”

### 2026-11-07 (score 36, −31)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → unverified
- [security regression] Stability: 0.03 → unverified
- [security improvement] Authorization: partial → pass
- [security] First check of Authorization: partial
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-11-06 (score 67, 0)

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

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

First indexed and scored.

## MCP tools (9)

### `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.

### `fetch_place_reviews` (~231 tokens)

Have the server fetch the reviews (spends a monthly server fetch)

Fallback for when you cannot reach a browser tab signed in to Google. Queues a server-side pull of the listing's newest reviews (the same worker as the site's form) and scores it. Ask the user first: it spends one of their server-side fetches for the month (check_place's serverFetch block says how many are left). Returns the job's progress; call again with job_id every 10-15 seconds until status is done (the result is then in the response) or failed (nothing is spent). Takes a Maps link, including share short-links, or a place_id. A place that is already scored returns its result without a fetch.

Input parameters:

- `job_id` (string): A job from an earlier call: returns its progress, or the result once done.
- `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: any Google Maps place link, share short-links included (the server's browser expands them).

### `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` (~589 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).
- `takeaways` (object): Optional: your summary of the reviews you collected, shown on the place's page (never scored). Three lists of up to 6 short plain-English sentences, drawn from reviews by established accounts: pros (…

### `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)

### `submit_takeaways` (~167 tokens)

Add your summary of the reviews to the place's page

After a submission is finalized: send the summary you give the user of what recent reviewers praise (pros), complain about (cons) and advise (tips), up to 6 short plain-English sentences per list, drawn from reviews by established accounts rather than one-off ones. It is shown on the place's page next to the trust result and never affects the score. The same lists can travel inside the submission payload as `takeaways` instead. Only an accepted or kept submission can carry one; calling again replaces yours.

Input parameters:

- `cons` (array): What they complain about.
- `pros` (array): What recent reviewers praise.
- `submission_id` (string, required): The finalized submission these lists summarize (from begin_submission / submit_reviews).
- `tips` (array): Practical advice they give.

### `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/com-isitlegitreviews-isitlegit/isitlegitreviews#diagnostics

## Score history

- 2026-11-21: 36
- 2026-11-20: 36
- 2026-11-19: 36
- 2026-11-18: 36
- 2026-11-17: 36
- 2026-11-16: 36
- 2026-11-15: 36
- 2026-11-14: 36
- 2026-11-13: 36
- 2026-11-12: 36
- 2026-11-11: 70
- 2026-11-10: 69
- 2026-11-09: 69
- 2026-11-08: 68
- 2026-11-07: 36
- 2026-11-06: 67
- 2026-11-05: 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 com.isitlegitreviews/isitlegit. Scores whether a business's Google Maps reviews are genuine. Your agent collects them, we judge. This page covers its hosted endpoint (https://isitlegitreviews.com/mcp).

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

Is it legit? Reviews trust checker scores 36 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 9 tools: describe_review_source, check_place, fetch_place_reviews, begin_submission, submit_reviews, and 4 more. Their descriptions and schemas cost roughly 1,827 tokens of context every time the server is loaded.

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

Yes. Is it legit? Reviews trust checker asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### 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 21 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 5 checks on Is it legit? Reviews trust checker, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Is it legit? Reviews trust checker: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. 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://isitlegitreviews.com/mcp
- Website: https://isitlegitreviews.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-isitlegitreviews-isitlegit/isitlegitreviews.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-isitlegitreviews-isitlegit/isitlegitreviews/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-isitlegitreviews-isitlegit/isitlegitreviews.json
- HTML version of this page: https://verifymcp.io/servers/com-isitlegitreviews-isitlegit/isitlegitreviews
