mcpField
M
mcp-review-platform-reputation-enricher

mcp-review-platform-reputation-enricher

Local
github.com/mambalabsdevBusiness & Marketing0Updated 1w ago

About mcp-review-platform-reputation-enricher

mcp-review-platform-reputation-enricher is an MCP server for company reputation research, retrieving Trustpilot ratings and review data by Business Unit ID or company domain. Its default route reads public data; an optional public-page route also returns claimed status, verification, and categories.

Key features

  1. 01Retrieve TrustScore, star rating, and review count
  2. 02Show the one-to-five-star breakdown
  3. 03Optionally read claimed and verified status
  4. 04Distinguish blocked, not found, and unreadable data
  5. 05Return one flat JSON row

Use cases

  1. 01Compare a company’s Trustpilot rating and review volume
  2. 02Inspect the star distribution behind a rating
  3. 03Check whether a Trustpilot profile is claimed and verified

MCP support

The MCP server exposes the `get_trustpilot_reputation` tool to MCP clients. It accepts a Business Unit ID or company domain and returns the Apify Actor’s flat JSON result.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"com-mambabuilt-mcp-review-platform-reputation-enricher": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-review-platform-reputation-enricher"
],
"env": {
"APIFY_TOKEN": "<APIFY_TOKEN>"
}
}
}
}
Run commandnpx -y @mambalabsdev/mcp-review-platform-reputation-enricher
Environment variables to set
APIFY_TOKENSecretApify API token from https://console.apify.com/account/integrations

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@mambalabsdev/mcp-review-platform-reputation-enricher1.2.0

Tools

1

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
sourcesenumNoWhich review sources to query. This version serves Trustpilot only. G2, Capterra, and Glassdoor appear as columns and always report skipped, with the reason on the row. This setting exists so a saved configuration keeps working when a source is added. Sent as a string for Clay compatibility.trustpilot
skipCachebooleanNoWhen "false" (default) a successful lookup is cached for seven days and reused, which costs nothing on a repeated run. Set "true" to force a fresh fetch. Sent as a string for Clay compatibility.
company_namestringNoOptional. Carried through to the output row for joining. The lookup is keyed on the business unit id, so the name never changes which business is returned.
company_domainstringNoBare company domain, for example monzo.com. Used to look for a Trustpilot business unit id in the company's own widget embed. Supplying trustpilotBusinessUnitId instead skips this step and always resolves.
minReviewCountenumNoSets rating_is_meaningful on the row. A 5.0 rating from two reviews and a 4.2 from nine hundred are not comparable numbers, and this is the column that says which one you are looking at. It never drops a row and never changes the rating returned. Sent as a string for Clay compatibility.10 | 50 | 100 | 500 | none
publicPageAccessenumNoLeave at "off" (default) to read only Trustpilot's public TrustBox data endpoint, which Trustpilot's robots.txt allows. Set "unblocker" to read Trustpilot's public company pages through Apify Unblocker, which resolves any domain with no business unit id and also returns categories, claimed status, and verification. Trustpilot's robots.txt disallows those pages to automated agents, so this is the caller's call, and it spends Unblocker units from the caller's Apify account. A row resolved this way charges public-page-profile-returned instead of reputation-resolved, never both.off | unblocker
includeCategoriesbooleanNoHas no effect on the default route: Trustpilot publishes categories only on its public company page, so trustpilot_categories is null unless publicPageAccess is unblocker. Kept so saved configurations keep working. Sent as a string for Clay compatibility.
trustpilotBusinessUnitIdstringNoThe 24 character Trustpilot business unit id, for example 57da77be0000ff000594bcdb. The fastest and most reliable input: supplied here it always resolves. Find it in the page source of any site running a Trustpilot widget, as data-businessunit-id, or reuse trustpilot_business_id from an earlier row. Leave it empty and the actor looks for it on the company's own site.

Details

From the project README

Review Platform Reputation Enricher MCP Server

Smithery Glama score MCP Registry npm version npm downloads license mcpservers.org

Review Platform Reputation Enricher MCP server

An MCP server that resolves a company domain to its Trustpilot rating, review count and claimed status. It wraps the Mamba Labs Trustpilot Reputation Enricher actor on Apify and returns a Clay-ready flat JSON row to any MCP client.

What's Inside

What it does

Give it a Trustpilot business unit id, or a company domain, and it returns the TrustScore, review count, star score, and the one to five star breakdown. One flat row per company. By default it reads Trustpilot's public TrustBox data endpoint, which Trustpilot's robots.txt allows. No Trustpilot API key is needed.

The business unit id is the reliable route: supplied, it always resolves. A domain alone resolves only when the company's own site embeds a Trustpilot widget, so most domains come back not_found without the id. A row's trustpilot_business_id can be fed back as the id on a later call. Setting publicPageAccess to unblocker reads Trustpilot's public company page through Apify Unblocker instead, which resolves a domain with no id and adds categories, claimed status, and verification. Trustpilot's robots.txt disallows those pages to automated agents, so that route is your call, and it spends Unblocker units from your own Apify account.

The tool keeps four kinds of empty apart: a refused request reports blocked, a domain with no business unit reports not_found, a value nobody could read reports not_extractable, and a source that was never queried reports skipped. G2, Capterra and Glassdoor ship as explicit skipped status columns, so the row shape does not change when a source is added.

All of the lookup runs on Apify. This package is a thin client that calls the actor and hands back the result unchanged.

Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config:

{
  "mcpServers": {
    "mamba-review-platform-reputation-enricher": {
      "command": "npx",
      "args": ["-y", "@mambalabsdev/mcp-review-platform-reputation-enricher"],
      "env": {
        "APIFY_TOKEN": "your-apify-token"
      }
    }
  }
}

Get your token at https://console.apify.com/account/integrations, paste it in, and restart Claude Desktop. The get_trustpilot_reputation tool will be available.

Prerequisites

  • Node.js 18 or newer
  • An Apify account with an API token

Example prompts

  • "Get the Trustpilot rating for the business unit 4992d8e10000640005041a9a."
  • "What is the star breakdown for this company on Trustpilot?"
  • "Look up this domain's Trustpilot reputation and flag it only if it has at least 100 reviews."
  • "Is this company's Trustpilot profile claimed and verified? Use the public page route."

Inputs

  • company_domain (optional): bare company domain, for example monzo.com. Used to look for a Trustpilot business unit id in the company's own widget embed. Supplying trustpilotBusinessUnitId instead skips this step and always resolves.
  • company_name (optional): carried through to the output row for joining. The lookup is keyed on the business unit id, so the name never changes which business is returned.
  • trustpilotBusinessUnitId (optional): the 24 character Trustpilot business unit id, for example 57da77be0000ff000594bcdb. The fastest and most reliable input. Find it in the page source of any site running a Trustpilot widget, as data-businessunit-id, or reuse trustpilot_business_id from an earlier row.
  • publicPageAccess (optional): off (the default) or unblocker. unblocker reads Trustpilot's public company page through Apify Unblocker, which resolves a domain with no id and adds categories, claimed status, and verification. A row resolved this way charges public-page-profile-returned instead of reputation-resolved, never both.
  • minReviewCount (optional): one of none, 10, 50, 100 or 500. It sets rating_is_meaningful on the row. A 5.0 rating from two reviews and a 4.2 from nine hundred are not comparable numbers, and this is the column that says which one you are looking at. It never drops a row and never changes the rating returned.
  • includeCategories (optional): has no effect on the default route, because Trustpilot publishes categories only on its public company page. trustpilot_categories is null unless publicPageAccess is unblocker. Kept so saved configurations keep working.
  • sources (optional): which review sources to query. Version 1 serves trustpilot only. G2, Capterra and Glassdoor appear as columns and always report skipped, with the reason on the row. This setting exists so a saved configuration keeps working when a source is added.
  • skipCache (optional): when false (the default) a successful lookup is cached for seven days and reused. Set true to force a fresh fetch.
  • max_charge_usd (optional): spending cap for this call, in USD. The actor stops before any charge that would take the run past this amount and keeps every row already charged.

Output

The tool returns the actor's flat JSON row for the company, with 33 snake_case fields and no nested objects. trustpilot_status is the field to read before any rating, trustpilot_route and trustpilot_id_source say how the business unit was resolved, and rating_is_meaningful reflects the review count threshold you set. See the Apify Store page for the full output schema.

Example output

{
  "degraded": false,
  "degradation_reason": null,
  "company_domain": "mattressonline.co.uk",
  "company_name": "Mattress Online",
  "trustpilot_business_id": "4992d8e10000640005041a9a",
  "trustpilot_url": "https://www.trustpilot.com/review/www.mattressonline.co.uk",
  "trustpilot_name": "MattressOnline.co.uk",
  "trustpilot_rating": 4.8,
  "trustpilot_review_count": 72332,
  "trustpilot_stars": 5,
  "trustpilot_one_star": 1618,
  "trustpilot_two_stars": 768,
  "trustpilot_three_stars": 1485,
  "trustpilot_four_stars": 5850,
  "trustpilot_five_stars": 62611,
  "trustpilot_country_code": "GB",
  "trustpilot_route": "widget",
  "trustpilot_id_source": "homepage_embed",
  "trustpilot_claimed_status": "not_extractable",
  "trustpilot_is_claimed": null,
  "rating_is_meaningful": true,
  "trustpilot_status": "ok",
  "g2_status": "skipped",
  "capterra_status": "skipped",
  "glassdoor_status": "skipped",
  "coverage": 1,
  "fetch_status": "ok",
  "run_date": "2026-08-23T06:39:38.824Z"
}

Features

  • TrustScore, star score and total review count
  • The full one to five star breakdown, not just the average
  • Claimed and verified status, plus Trustpilot categories, on the optional public page route
  • Four kinds of empty, each with its own status, so a refusal is never a zero
  • G2, Capterra and Glassdoor ship as explicit skipped columns
  • 33 flat snake_case fields, one row per company
  • No Trustpilot API key needed

Pricing

You pay per event on Apify, billed to your own Apify account. Prices from the live pricing record, read 2026-10-16:

EventPrice per event (USD)Fires when
apify-actor-start$0.00005Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).
company-checked$0.003 on the Free plan, down to $0.0021 on higher Apify plansOnce per company for which the Trustpilot business unit lookup completed and a non degraded row was produced, whether or not anything was found. A not_found row fires this event, because looking and finding nothing is a real answer and it is the work you asked for. A degraded row, where the lookup could not run at all, fires nothing.
reputation-resolved$0.0035 on the Free plan, down to $0.00245 on higher Apify plansOnce per company where a Trustpilot business unit was found and its aggregate record returned. Does not fire on a company with no business unit, does not fire when Trustpilot refused the request, and does not fire when no API key was supplied, because in all three cases no reputation record was produced.
public-page-profile-returned$0.005 on the Free plan, down to $0.0035 on higher Apify plansOnce per company resolved through the optional public page route, which only runs when you set publicPageAccess to unblocker. It replaces the reputation resolved charge on that row rather than adding to it, so a row is never charged twice, and a run that leaves the setting alone never fires this event at all.

The actor's Apify page carries the current prices. Running this server consumes Apify credits.

Full actor documentation

This server is a thin client and holds no lookup logic. For the complete input and output reference, pricing, and run history, see the Apify Store page:

https://apify.com/mambalabs/review-platform-reputation-enricher


Mamba Labs GTM Suite

This server is one of the Mamba Labs GTM Suite MCP servers. Every actor in the suite takes a domain or a company and returns one flat row, so they stack in the same Clay table without reshaping anything. The actor behind this server is the Trustpilot Reputation Enricher, immutable Apify actor ID 3lIqfCt61j4hqE1xz.

Built by Mamba Labs | npm | Apify Store

License

MIT

Built by Mamba Labs. https://apify.com/mambalabs

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.