mcp-domain-radar
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_domainsA | Check availability of specific domain names. Use this when you already have exact domain names to verify (e.g. "mybrand.com", "mybrand.ai"). Checks via DNS + WHOIS for accurate results. |
| check_brand_domainsA | Check domain availability for a single brand name across many popular TLDs at once. Default TLDs: .com .io .dev .app .ai .co .so .me .xyz .tech .net .sh .run .cloud .to .gg .cc Supports 30+ TLDs including trending ones like .ai, .gg, .so, .lol, .wtf, .cool. |
| suggest_and_check_domainsA | Generate brand-name variations from keywords, then check domain availability for each. Creates variations using prefixes (get-, try-, my-…), suffixes (-hq, -lab, -flow…), compounds (keyword1+keyword2), and portmanteau blends. Great for brainstorming when obvious names are taken. |
| list_supported_tldsA | List all TLDs that this server can check via WHOIS, grouped by category. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| brand-naming | Guided brand naming workflow with domain availability checking |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct purpose: checking a brand across TLDs, checking specific domains, listing TLDs, and brainstorming variations. Minor potential confusion between check_brand_domains and check_domains, but descriptions clarify the difference.
Tool names follow a verb_noun pattern (check_, list_, suggest_and_check_). The compound verb in suggest_and_check_domains is a slight deviation, but overall consistent.
Four tools is appropriate for the domain checking and suggestion use case. Not too few or too many, each earns its place.
Covers core functionality: checking specific domains, checking a brand across TLDs, suggesting variations, and listing supported TLDs. Minor gaps like bulk brand checking or WHOIS details beyond availability, but sufficient for typical use.