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.
Available components
Last scanned (22 hours ago)
Scores higher than 19% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Search and Retrieval
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. How we score → Why this is hard to score →
Endpoint Security91
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
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. Claim this server and supply a read-only token to verify it and lift the score.
Checks we ran (5)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 12 Nov 26 −34
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Stability: 0.20 → unverified ▼ security
- Authorization: partial → pass ▲ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 11 Nov 26 +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.
- 9 Nov 26 +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.
- 8 Nov 26 +32
- Authorization: pass → partial ▼ security
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 2107 → 2811 ▼ functional
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: behind authorisation → reachable ▲ functional
- Stability: unverified → 0.10 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- New tool “fetch_place_reviews” functional
- New tool “submit_takeaways” functional
- “submit_reviews” added an optional parameter “takeaways” cosmetic
- 7 Nov 26 −31
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Authorization: partial → pass ▲ security
- First check of Authorization: partial security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 67
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://isitlegitreviews.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=isitlegitreviews.com | CN=YE2,O=Let's Encrypt,C=US | 5 Nov 2026 | 3 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 6d29379f4129a0ac556afee2ca89a1a9a29 |
| SANs: isitlegitreviews.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of isitlegitreviews.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| isitlegitreviews.com. | DS published | 13481 | 13 | Verified |
| isitlegitreviews.com. | Verified address RRset verified with the apex keys |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://isitlegitreviews.com/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://isitlegitreviews.com/.well-known/oauth-protected-resource" | Header | Value |
|---|---|
| www-authenticate | Bearer resource_metadata="https://isitlegitreviews.com/.well-known/oauth-protected-resource" |
Protected resource metadata
| Document | https://isitlegitreviews.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://isitlegitreviews.com/mcp |
| Authorisation server | https://isitlegitreviews.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://isitlegitreviews.com/mcp | Auth required | 401 | |
| http (plaintext) | http://isitlegitreviews.com/mcp | HTTPS enforced | 308 | https://isitlegitreviews.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
begin_submission Start a review submission (get an upload URL) ~236
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| 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. |
No output schema declared.
No examples provided.
check_place Is this place already analyzed? ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
describe_review_source Which review fields to collect for a platform ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | – | Platform to describe (default: all). |
No output schema declared.
No examples provided.
fetch_place_reviews Have the server fetch the reviews (spends a monthly server fetch) ~231
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
finalize_submission Finalize a submission / fetch its report ~57
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.
| Name | Type | Req | Description |
|---|---|---|---|
| submission_id | string | yes | – |
No output schema declared.
No examples provided.
get_place_trust Trust analysis of a place's reviews (cached) ~184
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
list_scored_places Browse the directory of analyzed places ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
submit_reviews Submit review data inline ~589
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 (… |
No output schema declared.
No examples provided.
submit_takeaways Add your summary of the reviews to the place's page ~167
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cons | array | – | What they complain about. |
| pros | array | – | What recent reviewers praise. |
| submission_id | string | yes | The finalized submission these lists summarize (from begin_submission / submit_reviews). |
| tips | array | – | Practical advice they give. |
No output schema declared.
No examples provided.
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.
remote · isitlegitreviews.com
claude mcp add --transport http com-isitlegitreviews-isitlegit 'https://isitlegitreviews.com/mcp'
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.