mcp-server-domain-tools
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| full_domain_auditC | Performs comprehensive domain audit including brand score, TLD tier analysis, and DNS connectivity checks. |
| generate_brand_variationsC | Generates strategic brand suffixes and industry compound variations for portfolio expansion. |
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 2 tools
The two tools have fairly distinct purposes: one performs an audit/analysis of a domain, the other generates new brand name variations. There is slight conceptual overlap since both operate on domain/brand data, but an agent can tell them apart.
Both names use consistent snake_case and are readable. However, 'full_domain_audit' is a noun phrase while 'generate_brand_variations' follows a verb_noun pattern, so the convention isn't perfectly uniform.
Only 2 tools is thin for a domain-tools server. The pairing (audit + generate) is coherent, but the surface feels minimal for a domain-focused toolkit.
Key domain operations are absent: no availability/whois check, no TLD listing, no DNS-only lookup, and no way to inspect or manage results. The audit covers scoring and connectivity, but agents would hit dead ends for common domain tasks.