Skip to main content
Glama
BACH-AI-Tools

Subdomain Finder3 MCP Server

by BACH-AI-Tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Subdomain Finder3 MCP Server

English | 简体中文 | 繁體中文

用于访问 Subdomain Finder3 API 的 MCP 服务器。

🚀 使用 EMCP 平台快速体验

EMCP 是一个强大的 MCP 服务器管理平台，让您无需手动配置即可快速使用各种 MCP 服务器！

快速开始：

  1. 🌐 访问 EMCP 平台

  2. 📝 注册并登录账号

  3. 🎯 进入 MCP 广场，浏览所有可用的 MCP 服务器

  4. 🔍 搜索或找到本服务器（bach-subdomain_finder3）

  5. 🎉 点击 "安装 MCP" 按钮

  6. ✅ 完成！即可在您的应用中使用

EMCP 平台优势：

  • ✨ 零配置：无需手动编辑配置文件

  • 🎨 可视化管理：图形界面轻松管理所有 MCP 服务器

  • 🔐 安全可靠：统一管理 API 密钥和认证信息

  • 🚀 一键安装：MCP 广场提供丰富的服务器选择

  • 📊 使用统计：实时查看服务调用情况

立即访问 EMCP 平台 开始您的 MCP 之旅！

Related MCP server: Subdomain Scan1 MCP Server

简介

这是一个 MCP 服务器，用于访问 Subdomain Finder3 API。

  • PyPI 包名: bach-subdomain_finder3

  • 版本: 1.0.0

  • 传输协议: stdio

安装

从 PyPI 安装:

pip install bach-subdomain_finder3

从源码安装:

pip install -e .

运行

方式 1: 使用 uvx（推荐，无需安装）

# 运行（uvx 会自动安装并运行）
uvx --from bach-subdomain_finder3 bach_subdomain_finder3

# 或指定版本
uvx --from bach-subdomain_finder3@latest bach_subdomain_finder3

方式 2: 直接运行（开发模式）

python server.py

方式 3: 安装后作为命令运行

# 安装
pip install bach-subdomain_finder3

# 运行（命令名使用下划线）
bach_subdomain_finder3

配置

API 认证

此 API 需要认证。请设置环境变量:

export API_KEY="your_api_key_here"

环境变量

变量名

说明

必需

API_KEY

API 密钥

是

PORT

不适用

否

HOST

不适用

否

在 Cursor 中使用

编辑 Cursor MCP 配置文件 ~/.cursor/mcp.json:

{
  "mcpServers": {
    "bach-subdomain_finder3": {
      "command": "uvx",
      "args": ["--from", "bach-subdomain_finder3", "bach_subdomain_finder3"],
      "env": {
        "API_KEY": "your_api_key_here"
      }
    }
  }
}

在 Claude Desktop 中使用

编辑 Claude Desktop 配置文件 claude_desktop_config.json:

{
  "mcpServers": {
    "bach-subdomain_finder3": {
      "command": "uvx",
      "args": ["--from", "bach-subdomain_finder3", "bach_subdomain_finder3"],
      "env": {
        "API_KEY": "your_api_key_here"
      }
    }
  }
}

可用工具

此服务器提供以下工具:

list_subdomains

List Subdomains

端点: GET /v1/subdomain-finder/

参数:

  • domain (string) 必需: Domain name

技术栈

  • 传输协议: stdio

  • HTTP 客户端: httpx

许可证

MIT License - 详见 LICENSE 文件。

开发

此服务器由 API-to-MCP 工具生成。

版本: 1.0.0

Available Tools

1 tool
list_subdomainsC

List Subdomains

ParametersJSON Schema
NameRequiredDescriptionDefault
domainYesDomain name

TDQS

C2/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to explain what data is returned (array of strings? objects?), whether the operation is read-only or rate-limited, or what happens if the domain is invalid. The two-word description provides zero behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While extremely brief (two words), this represents under-specification rather than efficient conciseness. As noted in the rubric, 'Process' is under-specification, not conciseness. The description wastes no words but fails to earn its place with meaningful content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having only one parameter and no output schema, the description is incomplete. It should explain the return format or what 'listing' entails (active DNS records? registered subdomains? historical data?). For a tool with no annotations, more context is required to compensate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

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 'Domain name'. The description adds no semantic information about the parameter (e.g., whether it should include protocol, be a root domain, or format requirements). With full schema coverage, the baseline score is 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List Subdomains' is a tautology that merely restates the tool name 'list_subdomains'. While it technically identifies the verb (List) and resource (Subdomains), it fails to distinguish scope or provide any specific detail about what constitutes a subdomain in this context or what the listing entails.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives, prerequisites (e.g., whether the domain must be verified), or what to do if no subdomains exist. The absence of sibling tools does not excuse the lack of usage context for this single-parameter tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • First observedlist_subdomains
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2.5/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'list_subdomains' has a clearly distinct purpose that cannot be confused with any other tool in the set.

Naming Consistency5/5

The naming pattern is perfectly consistent as there is only one tool. It follows a clear verb_noun pattern ('list_subdomains') with no deviations or mixing of conventions to evaluate.

Tool Count2/5

A single tool is generally too few for a server's purpose, especially for a domain like subdomain finding which typically involves multiple operations such as scanning, enumerating, or verifying subdomains. This feels thin and limited in scope.

Completeness2/5

The tool set is severely incomplete for a subdomain finder domain. While listing subdomains is a core function, obvious gaps include tools for scanning, enumerating, verifying, or managing subdomains, which are essential for comprehensive coverage and will likely cause agent failures in broader tasks.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • Shodan MCP Server

    irootsec
    F
    license
    Not graded
    quality
    D
    maintenance
    Integrates Shodan search capabilities into MCP-compatible applications for discovering internet-connected devices. Enables domain searches, IP lookups, and advanced queries to identify exposed services, infrastructure mapping, and security analysis.
    3
    -