Skip to main content
Glama

Typosquat Scanner

typosquat
Read-onlyIdempotent

Generate typosquat permutations for a domain and check which variants are registered. Produces omission, transposition, keyboard-adjacent replacement, insertion, repetition, hyphenation, vowel-swap, homoglyph, plural/singular, and TLD-swap variants. Each result includes the variant domain, mutation type, prefix TLD count (how many TLDs the prefix is registered under), and registration date if known.

Use for brand protection, phishing detection, and defensive registration planning.

Related tools: nrds, ns_reverse, dns, whois.

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": "typosquat"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain to scan (e.g. example.com)

Output Schema

NameRequiredDescriptionDefault
dataNo
totalNoNumber of permutations generated
domainNoThe input domain
successNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / required
      Removed value: -[
      -  "success"
      -]
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. Beyond that, the description adds genuine value by enumerating the mutation strategies applied and explaining a non-obvious output field ('prefix TLD count — how many TLDs the prefix is registered under'). It says nothing about cost or latency, which matters for a scan that implies many registration lookups.

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?

Purpose and output shape are front-loaded in the first two sentences, with use cases and related tools pushed to the end. The ten-item mutation list is long but each item is a distinct behavior an agent could not otherwise infer, so it earns its space; the phrasing is tight overall.

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?

With rich annotations, a fully documented single parameter, and an output schema, the description only needs to frame purpose and usage — which it does, plus it pre-explains an opaque result field. It stops short of covering failure modes (invalid or unregistered base domain) or the scale of the scan, minor gaps given the structured coverage.

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?

There is a single required parameter with 100% schema description coverage and an inline example ('example.com'), so the schema carries the semantics. The description adds no constraint beyond that — nothing about whether a bare apex domain is required, whether IDN/unicode input is accepted, or how subdomains are handled — so the baseline of 3 is right.

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 first sentence gives a precise verb-plus-resource pair: generating typosquat permutations for a domain and checking which variants are registered. The mutation taxonomy and the note that this is about registration status distinguish it clearly from lookups like dns or whois.

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 names three concrete use cases (brand protection, phishing detection, defensive registration planning), which tells an agent when this tool is appropriate. What is missing is any exclusion or routing logic — the 'Related tools' line lists nrds, ns_reverse, dns, and whois but never says when to prefer one of them over this scanner.

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.