namebeta-mcp
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lookup_domainA | Query NameBeta's full suffix list for a keyword. Always return: total suffixes, how many are registered vs available, which domains are taken (with creation/expiry dates when registered), and the complete available list. Call this whenever the user types a keyword, brand, product name, or domain — e.g.「google flow video」or「naruto character generator」. Spaces are stripped and .com is the primary domain unless a TLD is already present. |
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 1 tool
With only a single tool, there is no possibility of overlap or confusion. The tool's purpose is unique by default.
The single tool uses a clear verb_noun pattern (lookup_domain), establishing a consistent convention even with an isolated example.
A single tool is minimal for a server; while the tool is non-trivial and well-scoped, the server feels incomplete for broad use cases like domain search or management.
For a pure lookup service, the tool covers the core workflow well (search, availability, registration details). However, adjacent operations like domain suggestions or WHOIS history are absent, leaving minor gaps.