All servers · Cloud & networking
Subdomain API
app.subdomain/subdomains · v1.0.1
No registry update 90+ days
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Read-only (all tools declare readOnlyHint) |
| Capabilities declared | tools |
| Tool definitions | 2 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
Find known subdomains of a domain. Passive data; may include historic entries. List or count.
Connect
streamable-http · https://api.subdomain.app/mcp
claude mcp add --transport http subdomains https://api.subdomain.app/mcp{
"mcpServers": {
"subdomains": {
"url": "https://api.subdomain.app/mcp"
}
}
}Tools as reported by the server
find_subdomainsList 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-querycount_subdomainsReturn 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 change
Website · JSON · Text for agents · Registry updated 2026-06-26