Subdomain API
Server Details
Find known subdomains of a domain. Passive data; may include historic entries. List or count.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one returns a count, the other returns a list. The descriptions explicitly highlight when to use each (e.g., 'how many subdomains' vs 'list them'), eliminating ambiguity.
Both tools follow the same verb_noun pattern with snake_case: count_subdomains and find_subdomains. The naming is consistent, predictable, and aligns with the server's domain.
With only two tools, the set is minimal but well-suited to the narrow purpose of passive subdomain enumeration. While it falls below the typical 3-15 range, the scope is so focused that two tools adequately cover the core functionality.
The tool set covers both main operations for the domain: getting a count and listing subdomains. The descriptions mention pagination/truncation for the list, but no other obvious operations are missing for the stated use cases (recon, inventory, etc.).
Available Tools
2 toolscount_subdomainsCount subdomainsARead-onlyIdempotentInspect
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.
Inputs: domain (required). Returns: total, domain
find_subdomainsFind subdomainsARead-onlyIdempotentInspect
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.
Inputs: domain (required), limit. Returns: total, domain, returned, truncated, +1 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Passive subdomain enumeration from certificate transparency (certspotter, crt.sh) with DNS checks.
WHOIS/RDAP, DNS, SSL, live subdomains with IPs, and SPF/DMARC/DKIM for any domain.
Query crt.sh SSL/TLS Certificate Transparency logs for subdomain discovery and certificate audits.
Domain data: Top 1M domain ranks, compromised checks, new domain search, registered domain lists.
Related MCP Servers
- AlicenseAqualityBmaintenanceEnables passive subdomain enumeration from certificate transparency logs and DNS, with host resolution, certificate history, and attack-surface summaries for authorized security reconnaissance.4MIT
- AlicenseCqualityDmaintenanceEnables the discovery and listing of subdomains for a given domain through the Subdomain Finder3 API. It provides a specialized tool for subdomain enumeration within the MCP ecosystem.1MIT
- AlicenseBqualityDmaintenanceEnables subdomain enumeration and discovery by querying the Subdomain Scan1 API. Returns all subdomains for a given domain in JSON format.1MIT
- AlicenseNot gradedqualityBmaintenancePassive external attack-surface mapping server that discovers subdomains, DNS records, TLS posture, HTTP headers, and registration data via public sources like CT logs, Shodan, and RDAP/WHOIS, enabling security reconnaissance without active scanning.462 npm3Apache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.