Data · Local MCP server
Domain Search MCP
Naming engine with availability intelligence: score names, check domains, socials and registries.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.dorukardahan/domain-search-mcp- Version
- 1.13.1
- Status
- Active
- Category
- data
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-07-29
- Updated
- 2026-07-29
- Publisher
- dorukardahan (GitHub) · 3 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/dorukardahan) · how
- Repository
- github.com/dorukardahan/domain-search-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | domain-search-mcp | 1.13.1 | stdio |
How to connect Domain Search MCP
Domain Search MCP runs locally from a Node.js package published to the npm registry: domain-search-mcp version 1.13.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 domain-search-mcp@1.13.1. It reads these environment variables: PRICING_API_BASE_URL, PRICING_API_TOKEN (secret), PORKBUN_API_KEY (secret), PORKBUN_API_SECRET (secret), NAMECHEAP_API_KEY (secret) and NAMECHEAP_API_USER; 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": {
"domain-search-mcp": {
"command": "npx",
"args": [
"-y",
"domain-search-mcp@1.13.1"
],
"env": {
"PRICING_API_BASE_URL": "<value>",
"PRICING_API_TOKEN": "<secret>",
"PORKBUN_API_KEY": "<secret>",
"PORKBUN_API_SECRET": "<secret>",
"NAMECHEAP_API_KEY": "<secret>",
"NAMECHEAP_API_USER": "<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 dorukardahan (GitHub)
| Server | Runs |
|---|---|
| Twitterapi Docs MCPOffline access to TwitterAPI.io docs for AI assistants. 52 endpoints, guides, pricing. | Local · stdio |
| Twitterapi Io MCPOffline access to TwitterAPI.io docs for AI assistants. 67 endpoints, 32 pages, 24 blog posts. | Local · stdio |
More data servers
| Server | Runs |
|---|---|
| Domain MemoryLocal-first MCP server serving a project's business-domain knowledge to MCP-compatible agents. | Local · stdio |
| Domain MonitorQuery domain expiration data from domain-monitor.io via AI assistants like Claude. | Local · stdio |
| Domain RDAP MCPFree, keyless domain registration lookup via RDAP: registered, available, registrar, expiration. | Remote · HTTPLive check: ✓ handshake |
| Domain Search King MCPDomain search MCP:.com names verified available live via Verisign RDAP - not AI guess lists. | Remote · HTTPLive check: ✓ handshake |
| Domainium SearchAI-powered domain & business name generation with real-time availability checks. | Remote · HTTPLive check: ✓ handshake |
| DomainsDomains MCP - domain registration lookup + availability search over live. | Remote · HTTPLive check: ✓ handshake |
| DomandataBuild, preview, deploy and export academic surveys: blocks, flow logic, experiments, quotas, data. | Remote · HTTPLive check: sign-in required |
| DomduckDomain reputation over time: Domain Rating, Tranco rank, TLS, and AI crawler policy. | Remote · HTTPLive check: ✓ handshake |