Skip to main content
Glama

Server Details

Find known subdomains of a domain. Passive data; may include historic entries. List or count.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A4.6/5.0

Scored across 2 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count4/5

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.

Completeness5/5

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 tools
count_subdomainsCount subdomainsA
Read-onlyIdempotent
Inspect

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 subdomainsA
Read-onlyIdempotent
Inspect

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

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources