Namecheap logo

Namecheap

Checks Namecheap domain availability across 600+ TLDs and returns pricing and purchase links.

Install Namecheap

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "namecheap-2": {
      "command": "npx",
      "args": [
        "-y",
        "@birdmania1/namecheap-mcp"
      ],
      "env": {
        "NAMECHEAP_API_USER": "YOUR_VALUE_HERE",
        "NAMECHEAP_API_KEY": "YOUR_VALUE_HERE",
        "NAMECHEAP_USERNAME": "YOUR_VALUE_HERE",
        "NAMECHEAP_CLIENT_IP": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @birdmania1/namecheap-mcp

Process exited before answering initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 7d ago.

Overview

The namecheap MCP server checks domain availability through Namecheap across more than 600 TLDs. It runs through npx as an MCP process and uses Namecheap API credentials supplied through environment variables. Results include availability, pricing, and purchase links, with support for checking multiple domains in one request. Reach for it when researching names, comparing TLDs, or finding alternatives to an unavailable domain.

Use cases

  • Check batches of candidate domains
  • Find alternatives to an unavailable domain
  • Compare prices across TLDs
  • Research single-word domains in a chosen TLD

Key features

  • Availability checks across 600+ TLDs
  • Batch checks for up to 100 domains
  • Pricing in availability results
  • Purchase links
  • Direct Namecheap API access

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

8/8 checks healthy over the last 44d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · @birdmania1/namecheap-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads181Package downloads in the last 30 days.
Last commit7mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Namecheap works

What the namecheap MCP server does

The namecheap MCP server lets an MCP-compatible AI client query Namecheap for domain availability. It covers more than 600 TLDs, including common and newer extensions such as .com, .io, .ai, .xyz, and .tech. Responses include the current price and a link to purchase an available domain.

The server supports both individual and batch checks. A single request can check up to 100 domains, which is useful when comparing variations of a product name or reviewing several TLDs. You can also use conversational requests to look for startup names, investigate alternatives when a preferred domain is taken, or search for available single-word domains in a selected extension.

How it works

The package runs as a local MCP process through npx. Your MCP client sends domain lookup requests to the process, and the process calls the Namecheap API directly.

Namecheap API access must be enabled for the account, and the client IP address must be added to Namecheap's whitelist. The API request uses the account's API user, API key, username, and whitelisted client IP. Because Namecheap checks the request IP, a changed public IP can cause requests to fail until the whitelist is updated.

Setup and configuration

Install and run the package with:

Terminal
npx @birdmania1/namecheap-mcp

Configure these environment variables in the MCP client entry:

  • NAMECHEAP_API_USER
  • NAMECHEAP_API_KEY
  • NAMECHEAP_USERNAME
  • NAMECHEAP_CLIENT_IP

Before starting the namecheap MCP server, enable API access in the Namecheap account and add the current public IP to the account's allowed IP list. The documented setup obtains that address from api.ipify.org. Replace all placeholder credential values with the actual account values.

The README provides a Claude Code configuration using the npx command and the package name. Add the entry to the same MCP configuration file used by the rest of the client's servers. After changing the configuration, fully quit and reopen Claude Code. Keep only one namecheap entry across the possible Claude configuration files to avoid duplicate-server problems.

Tools and capabilities

The namecheap MCP server supports:

  • Checking whether domain names are available
  • Checking as many as 100 domains in one request
  • Querying more than 600 TLDs
  • Returning domain pricing with availability results
  • Providing purchase links for domains
  • Exploring alternatives when a requested domain is unavailable
  • Investigating domains within a particular TLD, including single-word options

Limitations and notes

This server depends on valid Namecheap API credentials, enabled API access, and a currently whitelisted client IP. An Invalid request IP error usually means the public IP changed or does not match the Namecheap whitelist. An API-access error indicates that API access still needs to be enabled in the Namecheap account.

The supplied setup instructions document Claude Code usage. If the server does not appear, check for duplicate namecheap entries, validate the JSON configuration, remove trailing commas, and restart the client. The documented license is MIT.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Namecheap

namecheap is an MCP server that connects an AI client to the Namecheap API for domain research. Its main tools check availability across more than 600 TLDs, support batches of up to 100 domains, return pricing, and provide purchase links. It requires Namecheap API credentials and a whitelisted client IP.

Install it with `npx @birdmania1/namecheap-mcp`, then add the required Namecheap credentials to your MCP client configuration. Enable Namecheap API access, whitelist the client IP, restart the client, and test with a domain availability request.

The server requires `NAMECHEAP_API_USER`, `NAMECHEAP_API_KEY`, `NAMECHEAP_USERNAME`, and `NAMECHEAP_CLIENT_IP`. The first three identify the Namecheap account and API credentials; the last must match an IP address whitelisted for Namecheap API access.

The server can check up to 100 domains in one request. Results can include availability, pricing, and purchase links, making batch requests suitable for comparing multiple names or TLD variations.

Update the IP whitelist in Namecheap because the public client IP may have changed or may not match the configured value. Obtain the current IP, replace the whitelisted address in Namecheap, and retry the request.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewNamecheap AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/namecheap-2?style=directory)](https://allmcps.com/mcp/namecheap-2)
HTML Embed
<a href="https://allmcps.com/mcp/namecheap-2"><img src="https://allmcps.com/api/badge/namecheap-2?style=directory" alt="Namecheap on AllMCPs" /></a>