Subdomain Scan1 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API 密钥 |
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_subdomainsC | Enter a domain here and we'll check and return all subdomains in a JSON format for you. |
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, 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.