DomScan

io.github.estevecastells由 GitHub 账号 estevecastells 发布v1.0.0更新于 Oct 27, 2026

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

发布方自己的服务:scan.mx Email Diagnostics

已验证Streamable HTTP可网页运行网页搜索与抓取云端与基础设施安全与监控

概览

AI 生成的概览

托管式 DomScan MCP 服务器,让助手对域名执行 DNS、WHOIS/RDAP、TLS、子域名、可用性、估值与品牌保护查询。

可以做什么
  • 查询 DNS 记录、传播情况与 DNS 安全,并导出完整记录集
  • 查询 WHOIS/RDAP 注册数据、WHOIS 历史与反向 WHOIS
  • 审计 SSL/TLS 证书、证书链、评级与到期时间,并搜索证书
  • 枚举子域名,检查域名可用性、估值与名称建议
  • 校验邮件安全(SPF、DKIM、DMARC、DNSSEC),并通过品牌监控检测仿冒域名
  • 查看基础设施信息:IP 查询、托管检测、ASN、技术栈与 MAC 厂商
适用场景
适合需要助手在一轮对话内回答域名问题的场景,例如可用性与归属核查、尽职调查、证书与邮件安全审计,以及持续的仿冒域名与品牌保护监控。
运行要求
需要远程 Streamable HTTP 端点;推荐使用 OAuth 认证,也可使用 DomScan API 密钥并以 Bearer Authorization 请求头发送。API 密钥需在 DomScan 控制台获取。无法直连远程端点的客户端可运行仓库自带的本地 stdio 包装器(npm install、DOMSCAN_API_KEY)或其 Docker 镜像。
安装前请注意
需要 DomScan 账号,并通过 OAuth 授权或提供 API 密钥,密钥属于需保密的凭据。查询内容会发送给第三方 DomScan 服务,估值、批量可用性或品牌监控等功能可能消耗付费额度。本地包装器未配置密钥时仅暴露只读的状态工具。

安装

在 SourceWeft 中

  1. 打开 控制台中的 DomScan,将其添加到工作区。
  2. 连接 所需的 凭据。它们会被私密存储,绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.estevecastells%2Fdomscan/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。

{
  "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.

来源:README.md,提交 cf71a6b

工具

0
该服务器需要登录,因此 SourceWeft 无法在没有账号的情况下读取其工具,也未收录。已连接账号所能看到的内容可能因账号及其权限而异。

版本历史

1
  1. v1.0.0最新Sep 16, 2026

评分

已满足适用检查项的 85%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

其他 Scan 集成