Is it legit? Reviews trust checker MCP server

• Registry nameai.legitreviews/legitreviewsverified in the MCP registry

The registry name sits under legitreviews.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-11-03
• Tools7
• Server calls itselflegitreviews
• Server version2.0.0
• Protocol version2025-06-18

On 2026-11-03 the server answered initialize and tools/list without a sign-in. First answer in 540 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 2 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
• Answeredmeasuring2 of the 7 daily checks it takes to print a share
• Median first answer613 ms
• Space in an agent's context≈ 2,146 tokensthe definitions of all its tools (7), which an agent carries on every turn
• Tool definitionsA · 93 of 100
• Typed results0 of 7 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 3 of 7

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• describe_review_source

  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…

• check_place

  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…

• begin_submission

  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…

• submit_reviews

  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…

• finalize_submission

  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.

• get_place_trust

  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…

• list_scored_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…