Namecheap runs on your own machine — the client starts it, so there is no endpoint to ping. 74 installs a week from npm. Last commit 16 Mar 2026.
Check domain availability across 600+ TLDs on Namecheap with pricing and purchase links
We read the source, 2 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
postinstall: node -e "console.log('\n✅ Namecheap MCP installed!\n\n⚠️ IMPORTANT: You must configure your Namecheap API credentials.\n\nQuick setup:\n\n1. Ask Claude: \"Visit https://api.ipify.org and tell me my IP address\"\n2. Enable Namecheap API and whitelist that IP\n https://www.namecheap.com → Profile → Tools → API Access\n3. Ask Claude to add credentials to ~/.claude/settings.json\n\nFull instructions:\nhttps://github.com/ziggythebot/namecheap-mcp#readme\n')"
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add namecheap -e 'NAMECHEAP_API_USER=<NAMECHEAP_API_USER>' -e 'NAMECHEAP_API_KEY=<NAMECHEAP_API_KEY>' -e 'NAMECHEAP_USERNAME=<NAMECHEAP_USERNAME>' -e 'NAMECHEAP_CLIENT_IP=<NAMECHEAP_CLIENT_IP>' -- npx -y @birdmania1/namecheap-mcp
{
"mcpServers": {
"namecheap": {
"command": "npx",
"args": [
"-y",
"@birdmania1/namecheap-mcp"
],
"env": {
"NAMECHEAP_API_KEY": "<NAMECHEAP_API_KEY>",
"NAMECHEAP_API_USER": "<NAMECHEAP_API_USER>",
"NAMECHEAP_CLIENT_IP": "<NAMECHEAP_CLIENT_IP>",
"NAMECHEAP_USERNAME": "<NAMECHEAP_USERNAME>"
}
}
}
}
[mcp_servers.namecheap]
command = "npx"
args = ["-y", "@birdmania1/namecheap-mcp"]
env = { NAMECHEAP_API_USER = "<NAMECHEAP_API_USER>", NAMECHEAP_API_KEY = "<NAMECHEAP_API_KEY>", NAMECHEAP_USERNAME = "<NAMECHEAP_USERNAME>", NAMECHEAP_CLIENT_IP = "<NAMECHEAP_CLIENT_IP>" }
{
"mcpServers": {
"namecheap": {
"command": "npx",
"args": [
"-y",
"@birdmania1/namecheap-mcp"
],
"env": {
"NAMECHEAP_API_KEY": "<NAMECHEAP_API_KEY>",
"NAMECHEAP_API_USER": "<NAMECHEAP_API_USER>",
"NAMECHEAP_CLIENT_IP": "<NAMECHEAP_CLIENT_IP>",
"NAMECHEAP_USERNAME": "<NAMECHEAP_USERNAME>"
}
}
}
}
{
"servers": {
"namecheap": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@birdmania1/namecheap-mcp"
],
"env": {
"NAMECHEAP_API_KEY": "<NAMECHEAP_API_KEY>",
"NAMECHEAP_API_USER": "<NAMECHEAP_API_USER>",
"NAMECHEAP_CLIENT_IP": "<NAMECHEAP_CLIENT_IP>",
"NAMECHEAP_USERNAME": "<NAMECHEAP_USERNAME>"
}
}
}
}
Put your own values in place of
<NAMECHEAP_API_USER> (Your Namecheap account username), <NAMECHEAP_API_KEY> (Your Namecheap API key from Profile → Tools → API Access), <NAMECHEAP_USERNAME> (Your Namecheap account username (same as API_USER)), <NAMECHEAP_CLIENT_IP> (Your whitelisted IP address (get with: curl -s https://api.ipify.org)).
The author’s registry entry marks them as required.
Check domain availability across 500+ TLDs. Single and bulk checks with UI.
MCP server for Namecheap — check availability, list domains, and get pricing
Check domain availability and live registry pricing, or search for available names.
Compare domain prices across 145+ registrars and 1,100+ TLDs, find promo codes, check availability.
Fast domain availability checker with RDAP/WHOIS — batch checks, TLD presets, and name generation.
Domain availability across 1,200+ TLDs, with renewal price, minimum term and eligibility
Check domain availability across every extension, generate names, and check social handles.
AI-powered domain & business name generation with real-time availability checks.
Answers built from our own checks of this server.