@rezlazy/namesilo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NAMESILO_BATCH | No | Set to 'true' to send all calls to /apibatch. Required for high-volume jobs; see batch policy. | false |
| NAMESILO_API_KEY | Yes | API key from API Manager | |
| NAMESILO_API_URL | No | Override the standard API base | |
| NAMESILO_SANDBOX | No | Set to 'true' to use https://sandbox.namesilo.com (request sandbox credentials from NameSilo) | false |
| NAMESILO_BATCH_URL | No | Override the batch API base |
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
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 67 tools
Most tools target a distinct resource and action, with clear one-line descriptions. A few pairs like getDomainInfo/whoisInfo or viewAuction/viewAuctions could be confused, but the descriptions resolve the intended difference.
Most names follow an action+object camelCase pattern, but there are notable inconsistencies: listDomains vs. contactList, dnsAddRecord vs. dnsListRecords, and object-first names like domainLock and emailVerification. The pattern is readable but not uniform.
67 tools is an extreme count for an MCP server, even for a broad domain-management API. Many operations could be consolidated into parameterized commands to reduce agent selection overhead.
The tool surface covers the domain lifecycle comprehensively: registration, renewal, transfers, DNS, DNSSEC, contacts, WHOIS, privacy, forwarding, email forwarding, portfolios, auctions, marketplace, billing, and orders. There are no obvious dead ends for the stated domain.