Skip to content
Subdomain API logo

Subdomain API MCP server

Which servers in the official MCP registry are Subdomain API's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-14

← Back to Subdomain API

Whose server it is
  • Registry nameapp.subdomain/subdomainsverified in the MCP registry

The registry name sits under subdomain.app. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-14
  • Stateanswerschecked 2026-10-14
  • Tools2
  • Server calls itselfsubdomain-app
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-14 the server answered initialize and tools/list without a sign-in. First answer in 392 ms.

Tools it offers2 tools · read 2026-10-14
  • find_subdomains

    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…

  • count_subdomains

    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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "subdomains": {
      "type": "http",
      "url": "https://api.subdomain.app/mcp"
    }
  }
}

OpenAPI spec

1 paths, read 2026-10-14. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.