mcp-review-platform-reputation-enricher
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from https://console.apify.com/account/integrations |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_trustpilot_reputationA | Resolve a company domain to its Trustpilot business unit and return the TrustScore, review count, star score, claimed and verified status and categories, through Trustpilot's documented Business Units API. Returns one flat Clay ready row. Requires the CALLER's own Trustpilot API key; without one every row reports skipped rather than pretending to have looked. A refused request reports blocked and a domain with no business unit reports not_found, and those two are never conflated. G2, Capterra and Glassdoor ship as skipped status columns so the row shape does not change when a source is added. Read only; requires an APIFY_TOKEN and consumes Apify credits per call. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusing it with another tool. Its sole purpose — resolving a domain to Trustpilot reputation data — is clearly described.
The single tool name follows a clear get_<source>_<data> convention and reads consistently with standard API naming. There are no other tools to conflict with the pattern.
One tool is on the thin side for a server named as a review-platform reputation enricher, especially since G2, Capterra, and Glassdoor are only represented as skipped statuses. However, the one tool is non-trivial and performs a complete Trustpilot lookup, so the count is borderline rather than extreme.
The tool covers Trustpilot reputation retrieval well, but the server's broader reputation-enrichment scope is not met: G2, Capterra, and Glassdoor are explicitly not fetched, only marked as skipped. An agent needing reputation data from those platforms would hit a dead end.