# DomScan [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/estevecastells/domscan-mcp  
**GitHub Stars:** 1  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/domscan

## Description
Domain intelligence for DNS, WHOIS/RDAP, TLS, reputation, valuation, and brand protection.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "domscan": {
    "command": "npx",
    "args": ["-y","mcp-remote","https://domscan.net/mcp","--header","Authorization: Bearer ${DOMSCAN_API_KEY}"]
  }
}
```

## Documentation & README

# DomScan MCP Server

> Domain intelligence for AI agents. Connect [DomScan](https://domscan.net) to Claude, Cursor, VS Code and any [Model Context Protocol](https://modelcontextprotocol.io/) client to run DNS, WHOIS/RDAP, SSL/TLS, subdomain, availability, valuation, email-security and brand-protection lookups straight from your assistant.

DomScan is a domain intelligence platform that exposes its data over one REST API and a hosted MCP server. This repository documents the MCP server: how to connect it, what tools it exposes, and how to use it in agent pipelines.

- Website: https://domscan.net
- MCP endpoint: `https://domscan.net/mcp` (Streamable HTTP)
- Transport: Streamable HTTP (remote)
- Auth: OAuth discovery (recommended) or a DomScan API key

## Quick start

### OAuth-aware clients

Add `https://domscan.net/mcp` as a remote MCP server. DomScan publishes OAuth protected-resource and authorization-server metadata, so compatible clients can discover and complete authentication without a manually configured API key.

```json
{
  "mcpServers": {
    "domscan": {
      "url": "https://domscan.net/mcp"
    }
  }
}
```

### Claude Desktop / Claude Code with an API key

Add to your MCP config (`claude_desktop_config.json` or `.mcp.json`):

```json
{
  "mcpServers": {
    "domscan": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://domscan.net/mcp",
        "--header",
        "Authorization: Bearer ${DOMSCAN_API_KEY}"
      ],
      "env": { "DOMSCAN_API_KEY": "your-api-key" }
    }
  }
}
```

### Native remote URL with an API key

```json
{
  "mcpServers": {
    "domscan": {
      "url": "https://domscan.net/mcp",
      "headers": { "Authorization": "Bearer your-api-key" }
    }
  }
}
```

Get an API key from the [DomScan dashboard](https://domscan.net/dashboard). OAuth is preferred when the client supports it. API keys remain available for clients that need explicit header authentication.

## Local MCP wrapper

This repository includes a runnable stdio wrapper for clients that cannot connect directly to the hosted Streamable HTTP endpoint. It forwards requests to `https://domscan.net/mcp` using `DOMSCAN_API_KEY`.

```bash
npm install
DOMSCAN_API_KEY=your-api-key npm start
```

If no API key is configured, the wrapper still starts and exposes only the read-only `domscan_mcp_status` tool. This lets MCP registries inspect and validate the server without granting access to domain-intelligence operations.

### Docker

```bash
docker build -t domscan-mcp .
docker run --rm -i -e DOMSCAN_API_KEY=your-api-key domscan-mcp
```

The local wrapper uses API-key authentication. Clients that support remote Streamable HTTP and OAuth should continue connecting directly to `https://domscan.net/mcp`; OAuth remains the recommended option for those clients.

## What it can do

The server exposes domain-intelligence tools across these areas:

- **DNS**: record lookups (A, AAAA, MX, TXT, NS, CNAME, CAA), full record dumps, propagation checks, DNS security.
- **WHOIS / RDAP**: registration data, WHOIS history, reverse WHOIS, RDAP.
- **SSL/TLS**: certificate audit, chain inspection, grade, expiry checks, deep scan, certificate search.
- **Subdomains**: subdomain enumeration and discovery.
- **Availability and valuation**: domain availability (single and bulk), appraisal, name suggestions.
- **Email security**: SPF, DKIM, DMARC validation and DNSSEC posture.
- **Brand protection**: typosquatting detection, brand monitors and scans.
- **Infrastructure**: IP lookup, hosting detection, ASN, technology/stack detection, MAC vendor lookup.

See the [DomScan API documentation](https://domscan.net/docs) and [MCP setup guide](https://domscan.net/mcp-domain-checker).

## Why MCP

MCP lets an AI assistant call DomScan directly: ask "is acme.io available, and who owns the look-alikes?" and the agent runs availability, WHOIS and typosquatting tools and answers in one turn. The same server powers automated workflows (monitoring, due diligence, brand protection) without custom integration code.

## Links

- Product: https://domscan.net
- API documentation: https://domscan.net/docs
- MCP setup guide: https://domscan.net/mcp-domain-checker
- MCP spec: https://modelcontextprotocol.io/
- Datasets and APIs: https://domscan.net/tools

## License

MIT. See [LICENSE](https://github.com/estevecastells/domscan-mcp/blob/HEAD/LICENSE).