Other · Local MCP server

Namecheap

Check domain availability across 600+ TLDs on Namecheap with pricing and purchase links.

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.ziggythebot/namecheap
Version
1.1.3
Status
Active
Category
other
Transport
stdio (local process)
Package
npm
Published
2026-03-14
Updated
2026-03-14
Publisher
ziggythebot (GitHub)
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/ziggythebot) · how
Repository
github.com/ziggythebot/namecheap-mcp
Source
Registry API entry

Packages

RegistryPackageVersionTransportEnvironment variables
npm@birdmania1/namecheap-mcp1.1.3stdioNAMECHEAP_API_USER (required), NAMECHEAP_API_KEY (required, secret), NAMECHEAP_USERNAME (required), NAMECHEAP_CLIENT_IP (required)

How to connect Namecheap

Namecheap runs locally from a Node.js package published to the npm registry: @birdmania1/namecheap-mcp version 1.1.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @birdmania1/namecheap-mcp@1.1.3. It reads these environment variables: NAMECHEAP_API_USER (required), NAMECHEAP_API_KEY (required, secret), NAMECHEAP_USERNAME (required) and NAMECHEAP_CLIENT_IP (required); set them in the client's configuration for this server.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "namecheap": {
      "command": "npx",
      "args": [
        "-y",
        "@birdmania1/namecheap-mcp@1.1.3"
      ],
      "env": {
        "NAMECHEAP_API_USER": "<value>",
        "NAMECHEAP_API_KEY": "<secret>",
        "NAMECHEAP_USERNAME": "<value>",
        "NAMECHEAP_CLIENT_IP": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More other servers

All 8,395 →
ServerRunsEndpoint or package
Name Demographics McpHarness the power of names with our Name Demographics MCP. Using Agify, Genderize, and Nationalize.Remote · HTTPLive check: ✗ no handshakename-demographics-mcp.mcpize.run
Name Generator MCPGenerate random names, usernames, and project codenames locally. No network and no key.Local · stdionpm: name-generator-mcp
Name ToolsGenerate startup names with an available.com, checked live, then screen US and EU trademarks.Remote & Local · HTTP, stdioLive check: sign-in requiredstartupnamegenerator.com
Namecatcher SkillsScore and value collectible Telegram usernames: namability 0-100, fair price, thesis. No API key.Local · stdionpm: namecatcher-mcp
NameIntelBrand-name intelligence across 5 dimensions including AI findability. Pay-per-call via x402.Remote · HTTPLive check: ✓ handshakemcp.nameintel.io
NamemyappBrandable business names with live domain availability + one-click buy URLs.Remote & Local · HTTP, stdioLive check: ✓ handshakemcp.namemy.app
NameraCheck name availability across domains, trademarks, and social handles. Score and rank candidates.Local · stdioPyPI: namera
Namesake - baby name catalog and guidesRead-only access to Namesake's baby name catalog: meaning, origin, pronunciation, popularity trend.Remote · HTTPLive check: ✓ handshakenamesake.baby