DomScan

io.github.estevecastellsPublished by GitHub account estevecastellsv1.0.0Updated Oct 27, 2026

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

The publisher's own server: scan.mx Email Diagnostics

Overview

AI-generated overview

Hosted DomScan MCP server that lets an assistant run DNS, WHOIS/RDAP, TLS, subdomain, availability, valuation and brand-protection lookups on domains.

What you can do
  • Look up DNS records, propagation and DNS security, and dump full record sets
  • Query WHOIS/RDAP registration data, WHOIS history and reverse WHOIS
  • Audit SSL/TLS certificates, chains, grades and expiry, and search certificates
  • Enumerate subdomains and check domain availability, appraisals and name suggestions
  • Validate email security (SPF, DKIM, DMARC, DNSSEC) and detect typosquatting with brand monitors
  • Inspect infrastructure: IP lookup, hosting, ASN, technology stack and MAC vendor
When to use it
Useful when an assistant needs to answer domain questions in one turn, such as availability and ownership checks, due diligence, certificate and email-security audits, or ongoing brand-protection and typosquatting monitoring.
Requirements
A remote Streamable HTTP endpoint; OAuth is the recommended authentication, or a DomScan API key sent as a Bearer Authorization header. An API key is obtained from the DomScan dashboard. Clients that cannot connect remotely can run the repository's local stdio wrapper (npm install, DOMSCAN_API_KEY) or its Docker image.
Before you install
Requires a DomScan account and either OAuth consent or an API key, which is a credential to keep secret. Lookups are sent to the third-party DomScan service, and some features such as valuation, bulk availability or brand monitors may consume paid quota. The local wrapper without a key exposes only a read-only status tool.

Installation

In SourceWeft

  1. Open DomScan in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.estevecastells%2Fdomscan/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "domscan": {
      "type": "http",
      "url": "https://domscan.net/mcp"
    }
  }
}

README

DomScan MCP Server

Domain intelligence for AI agents. Connect DomScan to Claude, Cursor, VS Code and any Model Context Protocol 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. 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 installDOMSCAN_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 and MCP setup guide.

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

License

MIT. See LICENSE.

Source: README.md at commit cf71a6b

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Scan integrations