BlackVeil DNS & Email Security Scanner

discover_brand_domains_start

Start an async brand-domain discovery for the EXACT seed domain provided (the async sibling of discover_brand_domains, which can run ~24s and time out interactive clients). Same args as discover_brand_domains. Returns { auditId, queuedAt, etaSeconds } immediately; poll with discover_brand_domains_status and fetch ranked candidates with discover_brand_domains_findings once complete.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>",
      "discovery_mode": "<discovery_mode>"
    },
    "name": "discover_brand_domains_start"
  }
}

Input Schema

Name	Required	Description	Default
`depth`	No	Discovery depth. standard is default; deep expands candidate seeding and enrichment fanout.
`domain`	Yes	Seed domain, used verbatim: never normalize or swap in a canonical domain (clau.de stays clau.de).
`format`	No	Output verbosity.
`signals`	No	Signal modules to invoke. Defaults to all 12 discovery/enrichment signals.
`planner_mode`	No	Discovery planner: 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 the cache.
`discovery_mode`	Yes	"classic" (default) runs the public signal sweep; "tiered" adds private-binding tier lookups first.	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	Attest you own or may scan the seed domain. Required for "tiered" unless enterprise/owner/partner.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 12, 2026

changedInput schema / properties / discovery_mode / description

Previous value: -"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\"."New value: +"\"classic\" (default) runs the public signal sweep; \"tiered\" adds private-binding tier lookups first."

changedInput schema / properties / domain / description

Previous 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."New value: +"Seed domain, used verbatim: never normalize or swap in a canonical domain (clau.de stays clau.de)."

changedInput schema / properties / force_refresh / description

Previous value: -"Bypass cache and run a fresh check. Useful after DNS changes."New value: +"Bypass the cache."

changedInput schema / properties / format / description

Previous value: -"Output verbosity. Auto-detected if omitted."New value: +"Output verbosity."

changedInput schema / properties / ownership_verified / description

Previous value: -"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."New value: +"Attest you own or may scan the seed domain. Required for \"tiered\" unless enterprise/owner/partner."

changedInput schema / properties / planner_mode / description

Previous value: -"Planner mode for staged discovery fanout. observe emits metrics; enforce applies candidate-backed signal caps."New value: +"Discovery planner: observe emits metrics; enforce applies candidate-backed signal caps."

Changed1 schema field changedOct 25, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
AddedJul 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false; the description adds genuinely new behavior: it queues work rather than returning results, responds immediately with { auditId, queuedAt, etaSeconds }, and requires polling. It does not mention rate limits, cache/force_refresh implications, or the ownership_verified precondition for tiered mode, which are left to 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?

Two dense sentences, front-loaded with the sync-vs-async distinction and followed by the return shape and next steps. The mid-sentence parenthetical is slightly heavy but every clause carries operational value.

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 no output schema, the description supplies the response shape and the follow-up tool sequence, which is what an agent needs to drive the async flow. For a 12-parameter, open-world tool it stops short of covering prerequisites like the ownership attestation, but the schema fills those gaps fully.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description adds a meaningful constraint by stressing the seed domain is used EXACTLY as supplied (no canonicalization), reinforcing the high-risk usage pattern. 'Same args as discover_brand_domains' adds little since the full schema is present here.

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

Purpose5/5

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

States a specific verb and resource ('Start an async brand-domain discovery') and positions itself precisely against the sync sibling discover_brand_domains, including the reason (~24s runtime, interactive timeouts). An agent can distinguish it from the sync version without opening either schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use this instead of the sync tool when an interactive client would time out, then poll with discover_brand_domains_status and retrieve results with discover_brand_domains_findings. Both the alternative and the follow-up workflow are named.

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.