Skip to main content
Glama
relayshield

relayshield-mcp

Official

check_domain_lookalikes

Detect lookalike domains impersonating a brand by generating typos, homoglyphs, and TLD swaps, then checking DNS and Certificate Transparency data for registered domains.

Instructions

Detect typosquat and lookalike domains impersonating a brand. Generates hundreds of permutations (TLD swaps, character typos, homoglyphs, phishing prefixes/suffixes), resolves them in parallel via DNS, and enriches live results with Certificate Transparency data (cert count, recent issuance). Returns all lookalike domains that are currently registered and resolving. Use to find domains impersonating your brand, or before an employee clicks a link that resembles a company domain. Pay-as-you-go: $0.50 USDC per scan (x402 on Base). Subscription: rapidapi.com/relayshield

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesRoot domain to scan (e.g. acme.com — no scheme or path needed)

Implementation Reference

  • Tool schema definition for check_domain_lookalikes — declares name, description, and inputSchema requiring 'domain'.
    types.Tool(
        name="check_domain_lookalikes",
        description=(
            "Detect typosquat and lookalike domains impersonating a brand. "
            "Generates hundreds of permutations (TLD swaps, character typos, homoglyphs, "
            "phishing prefixes/suffixes), resolves them in parallel via DNS, and enriches "
            "live results with Certificate Transparency data (cert count, recent issuance). "
            "Returns all lookalike domains that are currently registered and resolving. "
            "Use to find domains impersonating your brand, or before an employee clicks a "
            "link that resembles a company domain. "
            "Pay-as-you-go: $0.50 USDC per scan (x402 on Base). "
            "Subscription: rapidapi.com/relayshield"
        ),
        inputSchema={
            "type": "object",
            "required": ["domain"],
            "properties": {
                "domain": {
                    "type": "string",
                    "description": "Root domain to scan (e.g. acme.com — no scheme or path needed)",
                }
            },
        },
    ),
  • Registered as a tool via the @app.list_tools() handler returning this types.Tool object.
    types.Tool(
        name="check_domain_lookalikes",
        description=(
            "Detect typosquat and lookalike domains impersonating a brand. "
            "Generates hundreds of permutations (TLD swaps, character typos, homoglyphs, "
            "phishing prefixes/suffixes), resolves them in parallel via DNS, and enriches "
            "live results with Certificate Transparency data (cert count, recent issuance). "
            "Returns all lookalike domains that are currently registered and resolving. "
            "Use to find domains impersonating your brand, or before an employee clicks a "
            "link that resembles a company domain. "
            "Pay-as-you-go: $0.50 USDC per scan (x402 on Base). "
            "Subscription: rapidapi.com/relayshield"
        ),
        inputSchema={
            "type": "object",
            "required": ["domain"],
            "properties": {
                "domain": {
                    "type": "string",
                    "description": "Root domain to scan (e.g. acme.com — no scheme or path needed)",
                }
            },
        },
    ),
  • Handler dispatch for check_domain_lookalikes — posts to the /domain API endpoint with the supplied domain argument.
    if name == "check_domain_lookalikes":
        return await client.post(
            f"{base}/domain",
            headers=headers,
            json={"domain": arguments["domain"]},
        )
  • Pricing helper mapping the tool name to its pay-as-you-go cost of $0.50 USDC.
    PAYG_PRICING: dict[str, str] = {
        "check_breach":            "$0.10 USDC",
        "check_sim_swap":          "$0.25 USDC",
        "check_domain_lookalikes": "$0.50 USDC",
        "check_oauth_watchlist":   "$0.15 USDC",
        "check_scan_result":       "$0.00 USDC (free — poll result of a paid scan)",
        "scan_url":                "coming soon",
        "scan_file":               "coming soon",
    }
Behavior3/5

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

No annotations provided, so description carries full burden. Covers key behavioral traits (generates hundreds of permutations, parallel DNS, cert enrichment, pay-as-you-go cost) but omits details like rate limits or failure modes.

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?

Two short sentences plus pricing line, no filler. Every sentence adds value: purpose, method, output, and cost.

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?

Given simple input schema and no output schema, description covers purpose, usage, behavior, and pricing fully. No missing context needed.

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 coverage is 100% with a single parameter. Description adds no extra meaning beyond the schema's description; 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?

Description clearly states it detects typosquat/lookalike domains, generating permutations, resolving via DNS, and enriching with cert data. Distinguishes from sibling tools like check_breach or scan_url.

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?

Provides explicit use cases: 'Use to find domains impersonating your brand, or before an employee clicks a link.' Lacks explicit 'when not to use' but context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/relayshield/relayshield-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server