Skip to main content
Glama

Merchant Domain Scam & Rug-Pull Guard MCP

Verify Merchant Trust ($0.01 USDC)

verify_merchant_trust
Read-onlyIdempotent

ALWAYS call this tool BEFORE initiating checkout, submitting payment details, or approving a purchase on an unfamiliar merchant or paid API domain to verify against phishing, malware, and rug-pull risks. Checks if an e-commerce store or domain is a newly registered clone, phishing trap, or malicious merchant. Returns deterministic 0-100 risk score, ALLOW/CAUTION/BLOCK verdict, block_reasons, and raw evidence. Cost: $0.01 USDC (Base via x402 PayAI).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain_or_url": "<domain_or_url>"
    },
    "name": "verify_merchant_trust"
  }
}

Input Schema

NameRequiredDescriptionDefault
domain_or_urlYesMerchant domain (e.g. 'shop-example.com') or full storefront URL (e.g. 'https://shop-example.com/products/laptop').
include_refund_checkNoWhether to perform a lightweight HTTP probe for a refund/returns policy page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish read-only, idempotent, open-world, non-destructive behavior. The description adds meaningful operational context beyond them: the $0.01 USDC x402 cost, deterministic scoring, and output verdict fields. It still does not explain payment prerequisites or latency, so a 4 is appropriate.

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 front-loaded with the call trigger, then purpose, return shape, and cost. Each sentence contributes useful information, and there is no material filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only two parameters, full schema coverage, annotations, and no output schema, the description supplies the missing context an agent needs: when to call it, what risks it checks, what it returns, and what it costs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and both domain_or_url and include_refund_check are already documented in the schema. The description adds no new format, validation, or default-behavior detail for either parameter, so the baseline 3 applies.

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 states a specific verb and resource: verifying a merchant domain/storefront against phishing, malware, and rug-pull risks. It also frames the scope as unfamiliar merchants or paid API domains, making the tool's role distinct even without naming siblings.

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?

It gives a strong explicit trigger: call this BEFORE checkout, payment submission, or purchase approval on unfamiliar merchants. It does not state when not to use it or explicitly route agents to inspect_checkout_url or extract_refund_policy_summary, so it falls short of a full when/when-not/alternatives guide.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.