BlackVeil DNS & Email Security Scanner

check_dane

Read-onlyIdempotent

Check DANE/TLSA pinning for SMTP: looks up TLSA records at _25._tcp. for each MX and validates their fields and DNSSEC backing. Records are reported present but UNVERIFIED: there is no port-25 certificate probe, so a pin is never compared to the certificate actually served. Use for SMTP DANE; use check_dane_https for port 443. Part of the scan_domain audit.

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>"
    },
    "name": "check_dane"
  }
}

Input Schema

Name	Required	Description
`domain`	Yes	Domain, e.g. example.com
`format`	No	Output verbosity.
`force_refresh`	No	Bypass the cache.

Output 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.

Changed3 schema fields changedNov 12, 2026

changedInput schema / properties / domain / description

Previous value: -"Domain to check (e.g., example.com)"New value: +"Domain, e.g. example.com"

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."

Changed1 schema field changedOct 25, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
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"
+}
```

Changed1 schema field changedJul 2, 2026

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"
+}

First observedApr 21, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses a real functional limitation: records are reported present but UNVERIFIED because there is no port-25 certificate probe, so the pin is never compared to the served certificate. That is exactly the kind of caveat an agent cannot get from structured fields.

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

Conciseness5/5

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

It is front-loaded with the action, moves through the lookup mechanics, the UNVERIFIED caveat, and the sibling routing, with no wasted sentences.

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

Completeness5/5

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

An output schema exists, so return values need not be explained, and the description covers scope, lookup mechanics, the major validation caveat, and the alternative tool. Nothing essential to calling it correctly is missing.

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%, so the schema already documents domain, format, and force_refresh. The description only implies how domain is used (MX hosts) and adds nothing about format verbosity or cache-bypass behavior, so baseline 3 applies.

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?

The description names a specific verb and resource ("Check DANE/TLSA pinning for SMTP") and specifies the exact lookup it performs (_25._tcp.<mx-host> for each MX), which immediately distinguishes it from the sibling check_dane_https.

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?

It gives an explicit routing rule: "Use for SMTP DANE; use check_dane_https for port 443." That names the alternative and the condition that selects it, so an agent needs no inference to pick between the two.

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.