Skip to main content
Glama

List lookalike domains of a brand and their DNS records

domain_typosquat
Read-only

Generates lookalike domains of a brand (omission, transposition, repetition, bit-flip, homoglyph, vowel swap, hyphenation, TLD swap; technique list after dnstwist), checks up to 30 of them in DNS (A records), and reads MX records for up to 8 that resolve. Resolving in DNS is not proof of registration or abuse. Related tools on this server, for a different need: domain when you need to look up domain registration (RDAP) and DNS. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": "<domain>"
    },
    "name": "domain_typosquat"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoVariants to look up in DNS, 1-40 (default 40)
domainYesBrand domain, e.g. example.com (a host name with a dot, no scheme or path)

Output Schema

NameRequiredDescriptionDefault
noteNo
domainNo
lookedNo
sourceNo
checkedAtNo
resolvingNo
registeredNo
unresolvedNo
variantsGeneratedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedOutput schema / properties / checkedAt
      Added value: +{}
    • addedOutput schema / properties / domain
      Added value: +{}
    • addedOutput schema / properties / looked
      Added value: +{}
    • addedOutput schema / properties / note
      Added value: +{}
    • addedOutput schema / properties / registered
      Added value: +{}
    • addedOutput schema / properties / resolving
      Added value: +{}
    • addedOutput schema / properties / source
      Added value: +{}
    • addedOutput schema / properties / unresolved
      Added value: +{}
    • addedOutput schema / properties / variantsGenerated
      Added value: +{}
  2. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds the details that actually matter for deciding to call: $0.002 per successful call via x402, failed calls uncharged, and the interpretive caveat that DNS resolution is not proof of registration or abuse. It also discloses internal sampling caps (30 DNS checks, 8 MX lookups), which are behavioral traits not visible in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core action and technique list, then moves to caveat, alternatives, and pricing in a logical order with no filler sentences. The single dense opening sentence packs three distinct operations together, which is efficient but slightly hard to parse on first read.

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?

An output schema exists, so return values need no explanation; pricing, the abuse caveat, the sibling alternative, and internal caps cover what an agent needs before calling. The only real gap is the unresolved 30-vs-40 conflict with the 'limit' parameter, which leaves the agent unsure what value to pass.

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

Parameters2/5

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

Schema coverage is 100%, so the baseline would be 3, but the description actively conflicts with the schema: it says variants are checked 'up to 30', while the 'limit' parameter is documented as 1-40 with a default of 40. The MX 'up to 8 that resolve' detail is genuinely new information, but the numeric mismatch on the one real parameter makes the description misleading rather than additive.

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?

States a specific verb and resource ('Generates lookalike domains of a brand'), enumerates the eight techniques used, and spells out the two-stage DNS work (A records, then MX for resolvers). It also names the sibling 'domain' as serving a different need, so an agent can distinguish the two without opening either schema.

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?

Explicitly routes the agent to 'domain' when the goal is RDAP registration plus DNS lookup, which is the main alternative an agent would confuse this with. It does not state outright when this tool is the wrong choice (e.g. for legitimate-domain research), so it stops just short of full when/when-not coverage.

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.

Resources