domain-search-king
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_available_domainsA | Generate brandable .com names for a business idea and return ONLY names currently available to register, each verified live against the Verisign RDAP registry. Use this when the user wants name ideas they can actually buy. Do not use for a single known domain (use check_domain) or an exhaustive starts/ends/contains scan (use find_available_domains_by_pattern). Read-only: does not register or transfer domains. Availability can change; re-check before purchase. Free, no API key; subject to a daily rate limit. |
| find_available_domains_by_patternA | Enumerate every currently available domain matching a keyword pattern (starts-with, ends-with, contains, or all) across chosen TLDs. Use this when the user already has a keyword and wants an exhaustive list, not invented brandables. Do not use to brainstorm creative names (use find_available_domains) or to inspect one known domain (use check_domain). Every candidate is verified live against the registry; taken names are omitted. Default TLDs: .com and .net. Read-only; does not register domains. |
| check_domainA | Due-diligence report for one known domain: live RDAP registration/age/expiry/status, backlinks and authority from our Common Crawl graph, toxic-linker flags, Wayback history, and trademark search links. Use this before buying a specific name. Do not use to generate names (use find_available_domains) or to list pattern matches (use find_available_domains_by_pattern). Read-only lookup; does not register, transfer, or change DNS. No composite appraisal score — flags and per-section detail only. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: one generates brandable ideas, one enumerates pattern matches, and one performs a single known-domain lookup. The descriptions explicitly cross-reference when to use each tool, so an agent will not mis-select.
All tool names use snake_case and follow a verb_noun convention. The two 'find_available_domains' names are very similar, but the '_by_pattern' suffix disambiguates them, and 'check_domain' is a consistent verb-object name, so the pattern is mostly predictable.
At 3 tools, the server is tightly scoped and each tool earns its place: brainstorming, exhaustive pattern enumeration, and deep single-domain due diligence. This is appropriate for a domain search server.
The domain search surface is well covered, including availability checks, pattern enumeration, and due diligence for a specific domain. A minor gap is the lack of batch checking for a list of known candidate domains, but the core workflows are complete.