Subdomain API
Find known subdomains of a domain. Passive data; may include historic entries. List or count.
使うべきか
品質と安全性
ツール定義とプロトコルへの準拠に関する自動分析に基づいています。
コンテキストコスト
これは、サーバーのツールがモデルのコンテキストに読み込まれるたびに消費されるおおよそのトークン数です。数が多いほど、ほかのタスクに使える注意が減ります。
インストール
ワンクリックインストール
これを `claude_desktop_config.json` ファイルに追加してください:
{
"mcpServers": {
"subdomains": {
"url": "https://api.subdomain.app/mcp"
}
}
}リモートエンドポイント
https://api.subdomain.app/mcpstreamable-httpできること
ツール一覧
ツール（2）
🟢find_subdomains(domain, limit)
List known subdomains (hostnames) of a root domain. Data is passive (not active scanning): results are historic observations and may include subdomains that no longer resolve or are no longer live. Results are a point-in-time snapshot that changes over time as new subdomains are observed — re-query rather than caching the result. Use for attack-surface mapping, security recon, asset inventory, or SEO host discovery. Hostnames are returned most-recently-seen first. The response always reports `total` (full distinct count known) and a `truncated` flag, so you can tell when more exist beyond `limit`.
入力スキーマ
{
"type": "object",
"properties": {
"domain": {
"type": "string",
"description": "Root (registrable) domain as a bare hostname, e.g. \"example.com\". No scheme, path, port, or leading \"www.\" — these are stripped."
},
"limit": {
"default": 200,
"description": "Max subdomains to return (1-1000, default 200). `total` always reports the full count regardless of this cap.",
"type": "integer",
"minimum": 1,
"maximum": 1000
}
},
"required": [
"domain"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}出力スキーマ
{
"type": "object",
"properties": {
"domain": {
"type": "string"
},
"total": {
"type": "integer",
"minimum": -9007199254740991,
"maximum": 9007199254740991,
"description": "Total distinct subdomains known."
},
"returned": {
"type": "integer",
"minimum": -9007199254740991,
"maximum": 9007199254740991,
"description": "Number in `subdomains`."
},
"truncated": {
"type": "boolean",
"description": "True if more exist beyond `limit`."
},
"subdomains": {
"type": "array",
"items": {
"type": "string"
}
}
},
"required": [
"domain",
"total",
"returned",
"truncated",
"subdomains"
],
"$schema": "http://json-schema.org/draft-07/schema#",
"additionalProperties": false
}🟢count_subdomains(domain)
Return only the total number of distinct subdomains known for a domain — no list. Cheap and low-token. Use when the user asks "how many subdomains" or you only need the size of the attack surface. Count includes historic subdomains that may no longer be live. It is a point-in-time figure that changes over time, so treat it as current-as-of-query, not a fixed value.
入力スキーマ
{
"type": "object",
"properties": {
"domain": {
"type": "string",
"description": "Root (registrable) domain as a bare hostname, e.g. \"example.com\". No scheme, path, port, or leading \"www.\" — these are stripped."
}
},
"required": [
"domain"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}出力スキーマ
{
"type": "object",
"properties": {
"domain": {
"type": "string"
},
"total": {
"type": "integer",
"minimum": -9007199254740991,
"maximum": 9007199254740991,
"description": "Total distinct subdomains known."
}
},
"required": [
"domain",
"total"
],
"$schema": "http://json-schema.org/draft-07/schema#",
"additionalProperties": false
}推奨プロンプト
find_subdomainsfind_subdomainsコミュニティ
エビデンス