Google Search Console integration for Model Context Protocol (MCP)
Nothing to run from here
Is it legit? Reviews trust checker is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
7
tools declared
remote
at its publisher
—
calls last 7d
What it does
Scores whether a business's Google Maps reviews are genuine. Your agent collects them, we judge.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http is-it-legit-reviews-trust-checker-mcp https://legitreviews.ai/mcp
# 2 — ask your agent for something these tools do
# describe_review_source, check_place, begin_submission and 4 more
Is it legit? Reviews trust checker costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
LEAll 1 server
legitreviews1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http is-it-legit-reviews-trust-checker-mcp https://legitreviews.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 Go
| Parameter | Type | Required | Notes |
|---|---|---|---|
| platform | string | no | Platform to describe (default: all). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| place_id | string | no | Google's feature id for the place (0x…:0x…, the '!1s' segment of a /maps/place URL). |
| url | string | no | 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. |
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 ch
| Parameter | Type | Required | Notes |
|---|---|---|---|
| platform | string | yes | — |
| place_id | string | no | Google's feature id for the place (0x…:0x…, the '!1s' segment of a /maps/place URL). |
| url | string | no | 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. |
| expected_reviews | integer | no | The review count the listing shows, if known. |
| agent | string | no | Your agent/product name, recorded as the submission's provenance (e.g. 'Muse', 'Claude Code'). |
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 up
| Parameter | Type | Required | Notes |
|---|---|---|---|
| submission_id | string | no | From begin_submission (omit for a one-shot submission). |
| final | boolean | no | With submission_id: true when this is the last chunk (default true). |
| platform | string | no | Which review source the data follows (describe_review_source). |
| placeId | string | no | Google feature id 0x…:0x… |
| cid | string | no | Decimal cid from a ?cid= link, when placeId is unknown. |
| name | string | no | — |
| address | string | no | — |
| lat | number | no | — |
| lon | number | no | — |
| listedReviews | integer | no | The review count Google displays on the listing. |
| listedRating | number | no | The star rating Google displays. |
| ratingHistogram | array | no | 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 |
| complete | boolean | no | True only if the review list reached its end; false for a newest-first window of the 500 most recent reviews (at least 200). |
| capped | boolean | no | True when deliberately stopped at 5000+ reviews of a much larger listing. |
| pulledAt | string | no | ISO 8601 datetime of collection (relative dates are resolved against it). |
| mapsUrl | string | no | — |
| sort | string | no | The order collected in: 'newest' (required for a window) or 'relevant'. |
| agent | string | no | Your agent/product name, recorded as the submission's provenance (e.g. 'Muse', 'Claude Code'). |
| reviews | array | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| submission_id | string | yes | — |
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 onl
| Parameter | Type | Required | Notes |
|---|---|---|---|
| place_id | string | no | Google's feature id for the place (0x…:0x…, the '!1s' segment of a /maps/place URL). |
| url | string | no | 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. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| city | string | no | Limit to one city's places (a slug from the cities field of a previous response). |
| list | string | no | Limit to one curated list's places. |
| page | number | no | Page number, 0-based. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Is it legit? Reviews trust checker or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 2.0.0 · scanned 4 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest5423827b16398d577b1207045096d4d8dadaaadd2a33d2b2c35923627ff72103
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| describe_review_source | no tags | |
| check_place | no tags | |
| begin_submission | state-write | state-write: declares readOnlyHint: false |
| submit_reviews | state-write | state-write: declares readOnlyHint: false |
| finalize_submission | state-write | state-write: declares readOnlyHint: false |
| get_place_trust | no tags | |
| list_scored_places | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest5423827b16398d57
Scanned2026-11-04
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 2.0.0.
2.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Is it legit? Reviews trust checker can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.