namecheap-mcp

domains

Manage a Namecheap domain portfolio: list and inspect names, check availability and pricing, register or renew, update nameservers and contacts, set transfer locks, and view balances.

Instructions

Manage Namecheap domain portfolio, availability & pricing checks, registration, renewal, nameservers, contacts, transfer lock, and account balances.

Input Schema

Name	Required	Description
`page`	No	Page number for list (default: 1).
`years`	No	Number of years for register or renew (default: 1).
`action`	Yes	Domain action to perform.
`domain`	No	Target domain name (for get, set_nameservers, set_contacts, set_lock, register, renew).
`locked`	No	Whether registrar transfer lock should be enabled (action: "set_lock").
`sortBy`	No	Sort order for list.
`domains`	No	List of domain names to check availability and pricing for (action: "check").
`contacts`	No	Contact details for register or set_contacts. On set_contacts, omitted roles preserve existing domain contacts; on register, omitted roles fall back to registrant or account primary address.
`pageSize`	No	Items per page for list (10–100, default: 100).
`promoCode`	No	Optional promotional coupon code for register or renew.
`searchTerm`	No	Filter domain list by substring.
`whoisGuard`	No	Enable free WhoisGuard privacy on registration (default: true).
`nameservers`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

B3.1/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must carry the full behavioral burden. It names mutation-oriented operations like registration, renewal, and contact changes but does not disclose costs, irreversibility, permission requirements, or side effects such as transfer-lock or contact overwrites.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence that avoids filler and directly names the domain portfolio and its operations. Its long comma-separated list is efficient but offers little structural separation between read-only and mutating capabilities.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex multi-action tool with 13 parameters, nested contact objects, no annotations, and no output schema, a one-sentence capability list is not enough. It omits action-specific behavior, mutation consequences, prerequisites, and the differing return shapes an agent should expect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is high at 92%, so the schema already documents the parameters in detail, including contacts fallback behavior and nameserver formats. The description adds only a high-level capability list and does not materially clarify parameter usage beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Manage Namecheap domain portfolio') and enumerates the main operations, so an agent can tell this is the domain-management tool. It does not explicitly distinguish itself from the sibling dns tool, keeping it below 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The listed capabilities imply when to use the tool: portfolio listing, availability checks, registration, renewal, nameserver/contact/lock changes, and balance lookup. However, there is no explicit guidance on choosing among the nine actions or on when to use this instead of the sibling dns tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools

dnsB
domainsB