Developer · Local MCP server

Namecheap Api MCP

Namecheap API - domains, DNS, contacts, registrar lock, SSL listing, and pricing.

What the MCP Registry states

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

Registry name
io.github.lanternrow/namecheap-api-mcp
Version
1.0.1
Status
Active
Category
developer
Transport
stdio (local process)
Package
npm
Published
2026-06-29
Updated
2026-06-29
Publisher
lanternrow (GitHub) · 4 servers with pages here
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/lanternrow) · how
Repository
github.com/lanternrow/namecheap-api-mcp
Source
Registry API entry

Packages

RegistryPackageVersionTransportEnvironment variables
npmnamecheap-api-mcp1.0.1stdioNAMECHEAP_API_USER (required), NAMECHEAP_API_KEY (required, secret), NAMECHEAP_CLIENT_IP (required), NAMECHEAP_USERNAME, NAMECHEAP_ENVIRONMENT

How to connect Namecheap Api MCP

Namecheap Api MCP runs locally from a Node.js package published to the npm registry: namecheap-api-mcp version 1.0.1. 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 namecheap-api-mcp@1.0.1. It reads these environment variables: NAMECHEAP_API_USER (required), NAMECHEAP_API_KEY (required, secret), NAMECHEAP_CLIENT_IP (required), NAMECHEAP_USERNAME and NAMECHEAP_ENVIRONMENT; 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-api-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "namecheap-api-mcp@1.0.1"
      ],
      "env": {
        "NAMECHEAP_API_USER": "<value>",
        "NAMECHEAP_API_KEY": "<secret>",
        "NAMECHEAP_CLIENT_IP": "<value>",
        "NAMECHEAP_USERNAME": "<value>",
        "NAMECHEAP_ENVIRONMENT": "<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 from lanternrow (GitHub)

All 4 →
ServerRunsEndpoint or package
Facebook Pages MCPFacebook Pages organic analytics, post management, and insights via Meta Graph API v25.0.Local · stdionpm: facebook-pages-mcp
Tiktok Organic MCPTikTok organic analytics - video performance, engagement metrics, and profile insights.Local · stdionpm: tiktok-organic-mcp
Youtube Organic MCPYouTube organic analytics - channel stats, video performance, watch time & audience insights.Local · stdionpm: youtube-organic-mcp

More developer servers

All 5,152 →
ServerRunsEndpoint or package
N8n MCPMCP server for n8n: generate, lint, explain failed executions, drive live n8n via REST.Local · stdionpm: @automatelab/n8n-mcp
nableSee where your cloud and AI bills go, and spend less. Local-first, in your terminal or editor.Local · stdioPyPI: finops-mcp
NahookManage Nahook webhooks from your AI client: endpoints, deliveries, retries, environments.Remote · HTTPLive check: sign-in requiredmcp.nahook.com
NahualiTrust-aware agent memory with evidence-backed recall, self-inspection, and audit history.Local · stdioOCI image (Docker): ghcr.io/arakiss/nahuali-mcp:0.8.0-beta.10
NamefiSearch, buy, and manage domains, DNS records, orders, and NFSC balance on Namefi.Remote · HTTPLive check: sign-in requiredapi.namefi.io
NameresolverNameResolver: The ViewCaller API empowers developers with phone number intelligence and.Remote · HTTPLive check: ✓ handshakemcp.jojapi.com
NamliChecks if a project, brand or app name already exists: trademarks, domains, web and GitHub.Remote · HTTPLive check: ✓ handshakenamli.vercel.app
Nan ForgetAI that remembers. Local-first cross-session, cross-project long-term memory for coding tools.Local · stdionpm: nan-forget