Dechonet MCP

DNS Propagation Check

dns_propagation

Read-onlyIdempotent

Compare a DNS record across 8+ global resolvers to see which return stale or updated values and confirm worldwide propagation after changes.

Instructions

Query one DNS record across 8+ global public resolvers (Google, Cloudflare, Quad9, OpenDNS, and more) simultaneously and report which resolvers return stale versus updated values. Use this after changing a record to confirm worldwide propagation. Use dns_lookup instead for a single authoritative answer with SPF/DMARC validation. Read-only; requires no API key; rate-limited. Returns per-resolver values and a consistency verdict.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`type`	No	DNS record type to compare across resolvers. Defaults to A (IPv4 address), the most common propagation check.	A
`domain`	Yes	Domain whose record to compare across resolvers (e.g., 'example.com'), without scheme or path.

Output Schema

TableJSON Schema

Name	Required	Description
`kpis`	No	Key metrics as label/value pairs
`grade`	No	Letter grade (A+ to F) when the tool grades the target
`score`	No	0-100 score when the tool scores the target
`issues`	No	Detected problems, severity-rated
`status`	Yes	Overall verdict, e.g. 'good' \| 'warning' \| 'bad' \| 'info' \| 'unknown'
`actions`	No	Recommended next actions, most important first
`summary`	No	One-paragraph interpretation of the result
`receipts`	No	Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature.
`reportUrl`	Yes	Human-facing interactive report for this exact lookup on dechonet.com
`observation`	No	How much was actually observed and when. A partial observation means some checks did not answer: missing parts are not verified, never clean.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.5.14Oct 15, 2026

addedOutput schema / properties / observation

Added value: +{
+  "additionalProperties": false,
+  "description": "How much was actually observed and when. A partial observation means some checks did not answer: missing parts are not verified, never clean.",
+  "properties": {
+    "ageMinutes": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "cached": {
+      "type": "boolean"
+    },
+    "observedAt": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "state": {
+      "enum": [
+        "complete",
+        "partial",
+        "unknown"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "state",
+    "observedAt",
+    "cached",
+    "ageMinutes"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / receipts

Added value: +{
+  "description": "Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "type": "string"
+      },
+      "tool": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "tool",
+      "id",
+      "url"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedv1.1.0Sep 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "actions": {
+      "description": "Recommended next actions, most important first",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "grade": {
+      "description": "Letter grade (A+ to F) when the tool grades the target",
+      "type": "string"
+    },
+    "issues": {
+      "description": "Detected problems, severity-rated",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "key": {
+            "type": "string"
+          },
+          "severity": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "severity",
+          "key"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "kpis": {
+      "description": "Key metrics as label/value pairs",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "label": {
+            "type": "string"
+          },
+          "value": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "label",
+          "value"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "reportUrl": {
+      "description": "Human-facing interactive report for this exact lookup on dechonet.com",
+      "type": "string"
+    },
+    "score": {
+      "description": "0-100 score when the tool scores the target",
+      "type": "number"
+    },
+    "status": {
+      "description": "Overall verdict, e.g. 'good' | 'warning' | 'bad' | 'info' | 'unknown'",
+      "type": "string"
+    },
+    "summary": {
+      "description": "One-paragraph interpretation of the result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "reportUrl"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedv1.0.3Jun 17, 2026

changedInput schema / properties / domain / description

Previous value: -"Domain to check"New value: +"Domain whose record to compare across resolvers (e.g., 'example.com'), without scheme or path."

changedInput schema / properties / type / description

Previous value: -"Record type"New value: +"DNS record type to compare across resolvers. Defaults to A (IPv4 address), the most common propagation check."

First observedv0.1.0Jun 17, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the bar is lower. The description still adds real operational context: named resolver set, no API key required, and rate-limited. It stops short of quantifying the rate limit or describing concurrency/retry behavior.

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?

Four tight sentences, purpose front-loaded before the routing guidance and behavioral notes. The final sentence on return values ('per-resolver values and a consistency verdict') partially duplicates the existing output schema, which slightly dilutes the conciseness.

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?

An output schema exists so return values need not be spelled out, and annotations carry the safety profile. The description supplies the routing and resolver-coverage context an agent needs; only minor gaps remain around rate-limit specifics and failure behavior when a resolver is unreachable.

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 both parameters (domain, type with enum and default) are already fully documented in the schema. The description adds only the framing that one record type is compared across resolvers, not new syntax or format guidance, 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 gives a specific verb (query/compare) and resource (one DNS record across 8+ named public resolvers) and explicitly frames the outcome (stale vs updated per resolver). It is immediately distinguishable from dns_lookup, which it names as the single-answer alternative.

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 states the exact trigger ('use this after changing a record to confirm worldwide propagation') and routes to the sibling with an explicit condition ('use dns_lookup instead for a single authoritative answer with SPF/DMARC validation'). Both when-to-use and when-not-to-use are covered.

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