F
license-
qualityD
maintenanceAnalyzes and compares product reputation using data from Reddit, Hacker News, and YouTube, providing sentiment and dimensional scores.
Last updated
Vendor Legit Check
Server Details
Screen a vendor, store, or group-buy for legitimacy: reputation, red flags, Reddit sentiment.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.2/5.0
Tool DescriptionsA
Average 4.2/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
Only one tool exists, so there is no possibility of confusion with other tools.
Naming Consistency5/5
Single tool name 'vendor_legit_check' follows a clear verb_noun pattern, consistent within itself.
Tool Count3/5
One tool is borderline thin for a server; while it packs multiple functions, the count is at the low end of reasonable.
Completeness4/5
The tool covers the core need of screening vendors with reputation, red flags, and sentiment. Minor gaps (e.g., no follow-up actions) but complete for a single-purpose check.
Available Tools
1 toolvendor_legit_checkAInspect
Screen a vendor, store, or group-buy (by name or URL) for legitimacy before paying. Returns a reputation read, a red-flag checklist (e.g. no MOQ disclosed, brand-new vendor), and Reddit community sentiment. Use this to assess scam/non-delivery risk for a hobby/collectibles purchase or group buy.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Vendor, store, or group-buy name or URL, e.g. 'novelkeys' or a Kickstarter link. | |
| No | Include live Reddit sentiment (default true). Set false for a faster, lighter check. |
Tool Definition Quality
A4.2/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose behavior. It states what is returned but does not explicitly mention that the tool is read-only or any side effects. The implied usage suggests it is safe, but transparency could be improved.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise with two sentences. The first covers action and output, the second provides usage context. No unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema or annotations, the description adequately covers the return value and usage scenario. It lacks details on error conditions or limitations, but it is sufficient for a simple tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, and the description adds value by providing examples for 'query' ('e.g. 'novelkeys' or a Kickstarter link') and explaining the 'reddit' parameter's effect ('Includes live Reddit sentiment (default true). Set false for a faster, lighter check.').
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Screen' and the resource 'vendor, store, or group-buy', specifying the action and target. It also lists the outputs (reputation read, red-flag checklist, Reddit sentiment), providing a clear purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly tells when to use the tool: 'Use this to assess scam/non-delivery risk for a hobby/collectibles purchase or group buy.' This provides clear context, though no alternative tools exist to differentiate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Flicense-qualityBmaintenancePassive website security and trust auditor that checks for security, SEO, AI surface, email, and other exposures, producing a score and remediation plan.Last updated
- AlicenseBqualityBmaintenanceMachine-readable merchant verification infrastructure for AI shopping agents and agentic commerce systems.Last updated13MIT
- AlicenseAqualityCmaintenanceScans suspicious messages, URLs, and text for scams inside any MCP-compatible AI assistant. No signup or API key needed for anonymous use.Last updated139MIT