Skip to content

Subdomain API MCP server

app.subdomain/subdomainssubdomain.appstreamable-httpv1.0.1Scanned

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

2 tools: 2 only read.

Tools: 0 delete, 0 irreversible, 0 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • No findings

Sign-in required, no OAuth metadata. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Subdomain API MCP server can do

The Subdomain API MCP server is published by subdomain.app, a domain the MCP Registry verified. It has 2 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

2 tools bring in text other people can write (find_subdomains and count_subdomains).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Nov 12, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Only reads 2Show 2 read-only tools
  • count_subdomainsReturn only the total number of distinct subdomains known for a domain — no list.Reads text others writeNo findings

    Why it is in this group

    • The name "count_subdomains" says "count": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • find_subdomainsList known subdomains (hostnames) of a root domain.Reads text others writeNo findings

    Why it is in this group

    • The name "find_subdomains" says "find": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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`.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Nov 20, 2026, 18:30 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
429
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: initialize answered HTTP 429.

Posture changes

  1. Nov 20, 2026
    • HTTP status of an anonymous initialize: 200 to 429
    • tools/list served without credentials: yes to no
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 429; tools/list served without credentials: yes -> no; Protocol version: 2025-06-18 -> none.View diff
    • HTTP status of an anonymous initialize: 200 to 429
    • tools/list served without credentials: yes to no
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http subdomains https://api.subdomain.app/mcp
claude mcp add --transport http subdomains https://api.subdomain.app/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__subdomains__find_subdomains",
      "mcp__subdomains__count_subdomains"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as subdomains. Review it before you use it.

Capability tags behind 2 rules
  • mcp__subdomains__find_subdomains untrusted-input
  • mcp__subdomains__count_subdomains untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/app.subdomain/subdomains/verify?hash=76366e26dc9fd5d54e2a128c06791b6850f9114521ac446553f48a1226e4b69c" | jq -e '.changed == false'

Pinned hash 76366e26dc9f, from Nov 12, 2026, 03:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/app.subdomain/subdomains/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for app.subdomain/subdomains
[![Anlyon Radar](https://radar.anlyon.com/badge/app.subdomain/subdomains.svg)](https://radar.anlyon.com/servers/app.subdomain/subdomains)

Source: MCP Registry. Synced Oct 21, 2026, 17:45 UTC.

Subdomain API MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Subdomain API MCP server safe?

No scan can promise that. What its definitions show: 2 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the Subdomain API MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Subdomain API MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Subdomain API MCP server have?

2 tools: 2 read. find_subdomains and count_subdomains.

Does the Subdomain API MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Subdomain API MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Subdomain API MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.