BlackVeil DNS & Email Security Scanner

discover_brand_domains

Read-onlyIdempotent

Discover all domains that belong to a brand's portfolio by aggregating certificate, DNS, redirect, and mail-policy signals. Use when asked what domains are part of a brand portfolio, or to find all domains related to a brand. Pass the EXACT seed domain verbatim — do NOT normalize or substitute a canonical domain.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`depth`	No	Discovery depth. standard is default; deep expands candidate seeding and enrichment fanout.
`domain`	Yes	The exact seed domain to expand, scanned verbatim (e.g., example.com). Do NOT normalize, resolve, or substitute a brand's canonical/main domain — pass the literal domain the user named (e.g. pass `clau.de`, not `anthropic.com`). Use `brand_aliases` for related brand labels.
`format`	No	Output verbosity. Auto-detected if omitted.
`signals`	No	Signal modules to invoke. Defaults to all 12 discovery/enrichment signals.
`planner_mode`	No	Planner mode for staged discovery fanout. observe emits metrics; enforce applies candidate-backed signal caps.
`brand_aliases`	No	Optional public brand aliases to seed, such as product or legal-entity labels.
`force_refresh`	No	Bypass cache and run a fresh check. Useful after DNS changes.
`discovery_mode`	Yes	Discovery mode. "classic" (default, BSL-licensed) runs the public signal-sweep pipeline. "tiered" layers Tier 0 (tenant-declared portfolio), Tier 1 (infrastructure-graph), and Tier 2 (declared-evidence) lookups in front of the legacy sweep, falling back to Tier 3 (the existing sweep) only on cache miss / very_stale fingerprint / uncovered caller candidates. Tiered mode requires private BlackVeil service bindings — BSL self-hosts should leave this on "classic".	classic
`dkim_selectors`	No	Optional DKIM selectors to probe. Defaults to a built-in common-selector list.
`min_confidence`	No	Drop candidates whose combined confidence falls below this threshold (0-1, default 0.5).
`candidate_domains`	No	Optional candidate domains supplied by the caller for corroboration.
`ownership_verified`	No	Caller attests that the seed domain is owned or authorized for scanning. Required when discovery_mode is "tiered" and the caller is not an enterprise/owner/partner principal. Prevents unauthorized mass reconnaissance via deep tier lookups.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`score`	Yes
`passed`	Yes
`partial`	No
`category`	Yes
`findings`	Yes
`checkStatus`	No
`verdictWithheld`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 5, 2026
- addedOutput schema / properties / verdictWithheld
```
Added value: +{
+  "type": "boolean"
+}
```
Changed2 schema fields changedAug 18, 2026
- addedOutput schema / properties / checkStatus
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / partial
```
Added value: +{
+  "type": "boolean"
+}
```

Changed2 schema fields changedJul 2, 2026

changedInput schema / properties / domain / description

Previous value: -"Seed domain whose brand portfolio to expand (e.g., example.com)."New value: +"The exact seed domain to expand, scanned verbatim (e.g., example.com). Do NOT normalize, resolve, or substitute a brand's canonical/main domain — pass the literal domain the user named (e.g. pass `clau.de`, not `anthropic.com`). Use `brand_aliases` for related brand labels."

addedInput schema / properties / force_refresh

Added value: +{
+  "description": "Bypass cache and run a fresh check. Useful after DNS changes.",
+  "type": "boolean"
+}

Changed1 schema field changedMay 26, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": {},
+  "properties": {
+    "category": {
+      "type": "string"
+    },
+    "findings": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "passed": {
+      "type": "boolean"
+    },
+    "score": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "category",
+    "score",
+    "passed",
+    "findings"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 24, 2026

addedInput schema / properties / ownership_verified

Added value: +{
+  "description": "Caller attests that the seed domain is owned or authorized for scanning. Required when discovery_mode is \"tiered\" and the caller is not an enterprise/owner/partner principal. Prevents unauthorized mass reconnaissance via deep tier lookups.",
+  "type": "boolean"
+}

Changed2 schema fields changedMay 20, 2026

addedInput schema / properties / discovery_mode

Added value: +{
+  "default": "classic",
+  "description": "Discovery mode. \"classic\" (default, BSL-licensed) runs the public signal-sweep pipeline. \"tiered\" layers Tier 0 (tenant-declared portfolio), Tier 1 (infrastructure-graph), and Tier 2 (declared-evidence) lookups in front of the legacy sweep, falling back to Tier 3 (the existing sweep) only on cache miss / very_stale fingerprint / uncovered caller candidates. Tiered mode requires private BlackVeil service bindings — BSL self-hosts should leave this on \"classic\".",
+  "enum": [
+    "classic",
+    "tiered"
+  ],
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "domain"
-]New value: +[
+  "domain",
+  "discovery_mode"
+]

Changed1 schema field changedMay 19, 2026

addedInput schema / properties / planner_mode

Added value: +{
+  "description": "Planner mode for staged discovery fanout. observe emits metrics; enforce applies candidate-backed signal caps.",
+  "enum": [
+    "off",
+    "observe",
+    "enforce"
+  ],
+  "type": "string"
+}

Changed7 schema fields changedMay 18, 2026

addedInput schema / properties / brand_aliases

Added value: +{
+  "description": "Optional public brand aliases to seed, such as product or legal-entity labels.",
+  "items": {
+    "maxLength": 64,
+    "minLength": 2,
+    "type": "string"
+  },
+  "maxItems": 20,
+  "type": "array"
+}

changedInput schema / properties / candidate_domains / description

Previous value: -"Optional candidate domains to test (used by ns and dkim_key_reuse signals). Max 200."New value: +"Optional candidate domains supplied by the caller for corroboration."

changedInput schema / properties / candidate_domains / maxItems
```
Previous value: -200New value: +250
```

addedInput schema / properties / depth

Added value: +{
+  "description": "Discovery depth. standard is default; deep expands candidate seeding and enrichment fanout.",
+  "enum": [
+    "standard",
+    "deep"
+  ],
+  "type": "string"
+}

changedInput schema / properties / signals / description

Previous value: -"Signal modules to invoke. Defaults to all 10 (san, san_recursive, ns, dmarc_rua, dkim_key_reuse, http_redirect, mx_overlap, spf_include, spf_include_seed, cname_alignment)."New value: +"Signal modules to invoke. Defaults to all 12 discovery/enrichment signals."

changedInput schema / properties / signals / items / enum

Previous value: -[
-  "san",
-  "san_recursive",
-  "ns",
-  "dmarc_rua",
-  "dkim_key_reuse",
-  "http_redirect",
-  "mx_overlap",
-  "spf_include",
-  "spf_include_seed",
-  "cname_alignment"
-]New value: +[
+  "san",
+  "san_recursive",
+  "ns",
+  "dmarc_rua",
+  "dkim_key_reuse",
+  "http_redirect",
+  "mx_overlap",
+  "txt_verification",
+  "mx_platform",
+  "spf_include",
+  "spf_include_seed",
+  "cname_alignment"
+]

changedInput schema / properties / signals / maxItems
```
Previous value: -10New value: +12
```

Changed3 schema fields changedMay 17, 2026

changedInput schema / properties / signals / description

Previous value: -"Signal modules to invoke. Defaults to all 8 (san, ns, dmarc_rua, dkim_key_reuse, http_redirect, mx_overlap, spf_include, cname_alignment)."New value: +"Signal modules to invoke. Defaults to all 10 (san, san_recursive, ns, dmarc_rua, dkim_key_reuse, http_redirect, mx_overlap, spf_include, spf_include_seed, cname_alignment)."

changedInput schema / properties / signals / items / enum

Previous value: -[
-  "san",
-  "ns",
-  "dmarc_rua",
-  "dkim_key_reuse",
-  "http_redirect",
-  "mx_overlap",
-  "spf_include",
-  "cname_alignment"
-]New value: +[
+  "san",
+  "san_recursive",
+  "ns",
+  "dmarc_rua",
+  "dkim_key_reuse",
+  "http_redirect",
+  "mx_overlap",
+  "spf_include",
+  "spf_include_seed",
+  "cname_alignment"
+]

changedInput schema / properties / signals / maxItems
```
Previous value: -8New value: +10
```

Changed3 schema fields changedMay 15, 2026

changedInput schema / properties / signals / description

Previous value: -"Signal modules to invoke. Defaults to all four (san, ns, dmarc_rua, dkim_key_reuse)."New value: +"Signal modules to invoke. Defaults to all 8 (san, ns, dmarc_rua, dkim_key_reuse, http_redirect, mx_overlap, spf_include, cname_alignment)."

changedInput schema / properties / signals / items / enum

Previous value: -[
-  "san",
-  "ns",
-  "dmarc_rua",
-  "dkim_key_reuse"
-]New value: +[
+  "san",
+  "ns",
+  "dmarc_rua",
+  "dkim_key_reuse",
+  "http_redirect",
+  "mx_overlap",
+  "spf_include",
+  "cname_alignment"
+]

changedInput schema / properties / signals / maxItems
```
Previous value: -4New value: +8
```

AddedMay 9, 2026

TDQS

A3.9/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered structurally. The description adds real value beyond that by disclosing the seed-handling contract ("scanned verbatim, do NOT normalize or substitute a canonical domain"), which is a behavioral trap that would otherwise silently produce wrong results. It omits cost/latency and the tiered-mode authorization constraint, which live only in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, all front-loaded and free of filler, ending on the highest-risk instruction (verbatim seed). The middle sentence's two clauses ("what domains are part of a brand portfolio" / "all domains related to a brand") restate the same trigger twice and could be collapsed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be described, and annotations cover the safety profile. The description adequately conveys purpose and triggering context for a 12-parameter tool. It stops short of flagging that `discovery_mode: tiered` requires private service bindings and `ownership_verified`, which are the main ways a caller can misuse this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% across all 12 parameters, so the schema already carries the semantics and a baseline of 3 is warranted. The description reinforces the critical `domain` constraint but merely echoes the schema's own wording, and adds nothing for the other eleven parameters (depth, signals, discovery_mode, ownership_verified, confidence thresholds).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb (Discover) and resource (all domains in a brand's portfolio) and even names the aggregation mechanism — certificate, DNS, redirect, and mail-policy signals. That is well beyond a restatement of the name. It does not, however, distinguish this synchronous tool from its sibling family (discover_brand_domains_start/_status/_findings), so an agent cannot tell from the text alone which entry point to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states clear triggering conditions: "Use when asked what domains are part of a brand portfolio, or to find all domains related to a brand." There is no explicit when-not guidance and no named alternative (e.g., discover_subdomains, check_shadow_domains, or the async start/status siblings), so routing among them is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All BlackVeil DNS & Email Security Scanner tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

discover_brand_domains

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources