Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@scandomain-mcp search for assets on example.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
SCANDOMAIN MCP 让 OpenClaw、Hermes、Cursor 等支持 MCP 的 AI Agent 能够调用
SCANDOMAIN 进行域名、IP、端口、服务、标题、ICP、Server Header 和组件等资产
检索。项目同时提供 MCP 服务和可复制的 Agent Skill：
skills/scandomain/SKILL.md。
请访问 SCANDOMAIN 官网，注册并登录后进入 个人中心获取 API Key。每位用户应使用自己的 Key；不要将 Key 提交到 GitHub、 粘贴到公开对话或共享日志中。
本项目无需发布到 npm。它会通过 GitHub 下载并运行，因此请先安装 Node.js 20+ 和 Git。
Windows PowerShell：
winget install OpenJS.NodeJS.LTS --accept-package-agreements --accept-source-agreements
winget install Git.Git --accept-package-agreements --accept-source-agreements
node --version
git --versionmacOS：
brew install node git
node --version
git --versionUbuntu/Debian：
sudo apt update
sudo apt install -y nodejs npm git
node --version
git --version获取 Key 后，可用以下命令单独启动 MCP 服务进行排查。服务启动后会等待 MCP
客户端连接，这是正常行为；用 Ctrl+C 停止。
Windows PowerShell：
$env:SCANDOMAIN_API_TOKEN = "在 https://scandomain.cyayaa.com/ 个人中心获取的 Key"
npx --yes github:Batman0506/scandomain-mcpmacOS/Linux：
SCANDOMAIN_API_TOKEN="在 https://scandomain.cyayaa.com/ 个人中心获取的 Key" \
npx --yes github:Batman0506/scandomain-mcp在终端执行以下命令。将 YOUR_SCANDOMAIN_API_KEY 替换为你从官网获取的 Key：
openclaw mcp add scandomain \
--command npx \
--arg -y \
--arg github:Batman0506/scandomain-mcp \
--env SCANDOMAIN_API_TOKEN=YOUR_SCANDOMAIN_API_KEY
openclaw mcp doctor scandomain --probe
openclaw mcp tools scandomain出现 scandomain_search 即表示连接成功。之后可直接向 OpenClaw 发送：
使用 SCANDOMAIN 查询 domain:"baidu.com"，汇总资产数量、IP、端口和服务。将下面内容合并到 ~/.hermes/config.yaml。不要把实际 Key 提交到任何仓库：
mcp_servers:
scandomain:
command: npx
args: ["-y", "github:Batman0506/scandomain-mcp"]
env:
SCANDOMAIN_API_TOKEN: "YOUR_SCANDOMAIN_API_KEY"然后运行：
hermes chat在 Hermes 对话中输入 /reload-mcp，或重新启动 Hermes。可用下面的提示词确认：
告诉我当前可用的 MCP 工具；然后使用 SCANDOMAIN 查询 ip:"8.8.8.8"。需要 Node.js 20 或更高版本。在 OpenClaw、Hermes 或其他支持本地 stdio MCP 的 客户端中添加以下配置：
{
"mcpServers": {
"scandomain": {
"command": "npx",
"args": ["-y", "github:Batman0506/scandomain-mcp"],
"env": {
"SCANDOMAIN_API_TOKEN": "从 https://scandomain.cyayaa.com/ 获取的 API Key",
"SCANDOMAIN_API_BASE_URL": "https://api.scandomain.cyayaa.com"
}
}
}
}如果客户端支持 Skill，将 skills/scandomain/SKILL.md 复制到该客户端的 Skill
目录。配置完成后，Agent 可以调用 scandomain_search，例如查询
domain:"baidu.com" 或 port:443 AND country:CN。
scandomain_search 使用 Quake 风格 DSL 查询资产：
参数 | 必填 | 说明 |
| 是 | 查询语句；裸域名和 IPv4 会自动转换为 DSL。 |
| 否 | 页码起始值，默认 |
| 否 | UTC 开始时间。 |
| 否 | UTC 结束时间。 |
请仅将 SCANDOMAIN 用于已授权的资产梳理、防御性安全分析与风险修复工作。
Related MCP server: SurveyHub-MCP
Use SCANDOMAIN from MCP-compatible AI agents with an API key created in the
SCANDOMAIN account center. The package
provides a local stdio MCP server and a portable agent skill at
skills/scandomain/SKILL.md.
The server calls the public SCANDOMAIN API:
POST https://api.scandomain.cyayaa.com/api/getDomain
Content-Type: application/json
api-token: <SCANDOMAIN_API_TOKEN>The package requires Node.js 20 or newer. Add this MCP configuration to a client such as OpenClaw, Hermes, Cursor, or another stdio MCP client:
{
"mcpServers": {
"scandomain": {
"command": "npx",
"args": ["-y", "github:Batman0506/scandomain-mcp"],
"env": {
"SCANDOMAIN_API_TOKEN": "your-api-key",
"SCANDOMAIN_API_BASE_URL": "https://api.scandomain.cyayaa.com"
}
}
}
}Copy skills/scandomain/SKILL.md into the agent's skill directory when the
client supports skills. It tells the agent when to call scandomain_search and
how to present authorized asset-search results.
scandomain_search queries assets using Quake-style DSL.
{
"query": "domain:\"baidu.com\"",
"start": 1,
"start_time": "2026-01-01T00:00:00Z",
"end_time": "2026-01-31T23:59:59Z"
}Bare domains and IPs are normalized automatically:
baidu.com -> domain:"baidu.com"
8.8.8.8 -> ip:"8.8.8.8"
port:443 AND country:CN -> unchangedstart defaults to 1. The public SCANDOMAIN endpoint controls page size.
Name | Required | Default |
| Yes | |
| No |
|
| No |
|
SCANDOMAIN_API_KEY is accepted as a compatibility alias for the token.
npm install
npm run check
npm testRun the server locally:
SCANDOMAIN_API_TOKEN="your-api-key" npm startKeep API keys out of prompts, repositories, and shared logs. Use SCANDOMAIN only for authorized asset discovery and defensive security work.
Search SCANDOMAIN assets with Quake-style DSL. Bare domains and IPs are normalized automatically.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Query DSL, for example domain:"example.com", ip:"1.1.1.1", or port:443 AND country:CN. | |
| start | No | SCANDOMAIN public API start value. Use 1 for the first page. | |
| end_time | No | Optional UTC end time filter, for example 2026-01-31T23:59:59Z. | |
| start_time | No | Optional UTC start time filter, for example 2026-01-01T00:00:00Z. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must convey all behavioral traits. It only mentions automatic normalization of domains/IPs, which is useful but insufficient. It does not disclose whether the operation is read-only, requires authentication, has rate limits, or how errors behave.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the purpose, and contains zero unnecessary words. It is highly concise and well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema and no sibling tools, the description does not explain the return format, pagination (schema partially covers 'start'), or error handling. It covers the core functionality but leaves gaps in expected usage flow.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents all parameters. The description adds only the note about normalization, which is not parameter-specific. Thus the description contributes minimal additional meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Search', the resource 'SCANDOMAIN assets', and adds a distinguishing feature: use of 'Quake-style DSL' and automatic normalization of bare domains/IPs. This is specific and unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, nor does it mention when not to use it. There are no sibling tools listed, but even so, the description lacks context for usage decisions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.1.0scandomain_searchWith only a single tool, there is no possibility of confusion or overlap. The tool's purpose is clearly unique within the set.
The single tool name 'scandomain_search' follows a clear prefix_verb pattern that is consistent and readable. No inconsistency arises with only one tool.
Providing only one tool for scanning and searching assets feels too few. Even for a focused search server, additional tools like list, get_details, or scan_initiate would be expected for a complete workflow.
The tool surface is severely limited to only search functionality. Missing operations such as initiating scans, retrieving asset details, or managing results create significant gaps for any real-world asset management task.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Capability registry for the agentic economy. Semantic search over verified MCP server listings.
Discover 6,700+ MCP servers and 15,000+ OpenClaw skills. Agent-native search with outcome ranking.
Hosted MCP server for live public-data APIs and Skills for AI agents.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Batman0506/scandomain-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
