Provides access to the Subdomain Scan1 API for checking and retrieving all subdomains for a given domain in JSON format.
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., "@Subdomain Scan1 MCP Server scan subdomains for 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.
用于访问 Subdomain Scan1 API 的 MCP 服务器。
EMCP 是一个强大的 MCP 服务器管理平台，让您无需手动配置即可快速使用各种 MCP 服务器！
🌐 访问 EMCP 平台
📝 注册并登录账号
🎯 进入 MCP 广场，浏览所有可用的 MCP 服务器
🔍 搜索或找到本服务器（bach-subdomain_scan1）
🎉 点击 "安装 MCP" 按钮
✅ 完成！即可在您的应用中使用
✨ 零配置：无需手动编辑配置文件
🎨 可视化管理：图形界面轻松管理所有 MCP 服务器
🔐 安全可靠：统一管理 API 密钥和认证信息
🚀 一键安装：MCP 广场提供丰富的服务器选择
📊 使用统计：实时查看服务调用情况
立即访问 EMCP 平台 开始您的 MCP 之旅！
Related MCP server: Subdomain Finder3 MCP Server
这是一个 MCP 服务器，用于访问 Subdomain Scan1 API。
PyPI 包名: bach-subdomain_scan1
版本: 1.0.0
传输协议: stdio
pip install bach-subdomain_scan1pip install -e .# 运行（uvx 会自动安装并运行）
uvx --from bach-subdomain_scan1 bach_subdomain_scan1
# 或指定版本
uvx --from bach-subdomain_scan1@latest bach_subdomain_scan1python server.py# 安装
pip install bach-subdomain_scan1
# 运行（命令名使用下划线）
bach_subdomain_scan1此 API 需要认证。请设置环境变量:
export API_KEY="your_api_key_here"变量名 | 说明 | 必需 |
| API 密钥 | 是 |
| 不适用 | 否 |
| 不适用 | 否 |
编辑 Cursor MCP 配置文件 ~/.cursor/mcp.json:
{
"mcpServers": {
"bach-subdomain_scan1": {
"command": "uvx",
"args": ["--from", "bach-subdomain_scan1", "bach_subdomain_scan1"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}编辑 Claude Desktop 配置文件 claude_desktop_config.json:
{
"mcpServers": {
"bach-subdomain_scan1": {
"command": "uvx",
"args": ["--from", "bach-subdomain_scan1", "bach_subdomain_scan1"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}此服务器提供以下工具:
get_subdomainsEnter a domain here and we'll check and return all subdomains in a JSON format for you.
端点: GET /
参数:
domain (string) 必需: Example value: rapidapi.com
传输协议: stdio
HTTP 客户端: httpx
MIT License - 详见 LICENSE 文件。
此服务器由 API-to-MCP 工具生成。
版本: 1.0.0
Enter a domain here and we'll check and return all subdomains in a JSON format for you.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Example value: rapidapi.com |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It mentions the tool will 'check and return' subdomains, implying a read-only operation, but doesn't disclose behavioral traits like rate limits, authentication needs, data sources, or whether it performs active scanning vs. cached lookups. For a tool with no annotations, this is insufficient.
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 a single, clear sentence that efficiently states the action and output. It's front-loaded with the core purpose and avoids unnecessary details. However, it could be slightly more structured by separating usage from output format, but it's still highly concise.
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 the tool's low complexity (1 parameter, no annotations, no output schema), the description is minimally adequate. It covers the basic purpose and output format, but lacks details on behavioral aspects and doesn't explain the return values beyond 'JSON format'. For a simple tool, it meets the minimum but leaves gaps in transparency.
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?
The input schema has 100% description coverage, with the 'domain' parameter documented as 'Example value: rapidapi.com'. The description adds minimal value beyond this, only reinforcing that you 'Enter a domain here'. With high schema coverage, the baseline is 3, as the description doesn't significantly enhance parameter understanding.
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 tool's purpose: 'check and return all subdomains' for a given domain. It specifies the verb ('check and return') and resource ('subdomains'), and mentions the output format ('JSON format'). However, it doesn't differentiate from siblings since there are none, so it can't achieve a perfect 5.
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 minimal guidance: 'Enter a domain here' implies usage when you have a domain to analyze. However, it lacks explicit when-to-use scenarios, alternatives (though none exist), or exclusions. It's basic usage instruction rather than strategic guidance.
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.
v1.0.0get_subdomainsWith only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to confuse it with. The tool's purpose is clearly defined and distinct by default.
The single tool name 'get_subdomains' follows a clear verb_noun pattern, and with only one tool, consistency is inherently perfect as there are no other names to compare it against.
A single tool is too few for a server focused on subdomain scanning, as it lacks essential operations like scanning specific ports, checking DNS records, or validating subdomains, making the scope feel incomplete and limiting for agents.
The tool surface is severely incomplete for subdomain scanning; it only retrieves subdomains without supporting related tasks like enumeration, validation, or security checks, which are core to this domain and will likely cause agent failures.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Find known subdomains of a domain. Passive data; may include historic entries. List or count.
Normalized JSON for any domain across 1,200+ TLDs, reading WHOIS where no RDAP server exists.
Email-domain intelligence: MX capability, provider, disposable status, SPF, DMARC, and MTA-STS.
Certificate Transparency search: subdomains, certificate history and hostname keyword search.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/BACH-AI-Tools/bachai-subdomain-scan1'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
