Subdomain Finder3 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | 不适用 (Not applicable) | |
| PORT | No | 不适用 (Not applicable) | |
| API_KEY | Yes | API 密钥 (API Key) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_subdomainsC | List Subdomains |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
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.
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.
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.
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.