Dechonet MCP

Full Domain Security Scan

security_scan

Read-onlyIdempotent

Audit a domain's security and health in one scan: checks DNS, SSL, HTTP headers, email auth, ports, and more, then returns a 0-100 score with prioritized fixes.

Instructions

One-shot comprehensive audit of a domain: runs DNS, SSL, HTTP headers, email auth, port scan, DNS propagation, reverse DNS, and ASN/RDAP checks in parallel, then computes a 0-100 Health Score with an A-F grade and a prioritized action list. Use this as the default starting point for "is this domain healthy/secure?" questions. Call the individual tools (e.g., ssl_check, email_auth) instead when you need depth on one area. BEHAVIOR: this includes an ACTIVE port_scan of the domain's host, so only run it on domains you own or are authorized to test. Read-only otherwise; requires no API key; rate-limited (it makes multiple backend calls). Returns the score, per-area breakdown, top actions, and per-area summaries.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`domain`	Yes	Domain to audit end-to-end (e.g., 'example.com'). Scheme and path are stripped. NOTE: the host is also port-scanned, so use only targets you are authorized to test.

Output Schema

TableJSON Schema

Name	Required	Description
`areas`	Yes	Per-area verdicts
`grade`	Yes	Letter grade A+ to F
`score`	Yes	Health Score 0-100
`actions`	No	Top recommended actions
`reportUrl`	Yes	Human-facing interactive report on dechonet.com

Schema Changelog

Changes observed during successful MCP inspections.

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": "Top recommended actions",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "areas": {
+      "description": "Per-area verdicts",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "area": {
+            "type": "string"
+          },
+          "verdict": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "area",
+          "verdict"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "grade": {
+      "description": "Letter grade A+ to F",
+      "type": "string"
+    },
+    "reportUrl": {
+      "description": "Human-facing interactive report on dechonet.com",
+      "type": "string"
+    },
+    "score": {
+      "description": "Health Score 0-100",
+      "type": "number"
+    }
+  },
+  "required": [
+    "score",
+    "grade",
+    "areas",
+    "reportUrl"
+  ],
+  "type": "object"
+}

Changed1 schema field changedv1.0.3Jun 17, 2026

changedInput schema / properties / domain / description

Previous value: -"Domain to scan comprehensively (e.g., example.com)"New value: +"Domain to audit end-to-end (e.g., 'example.com'). Scheme and path are stripped. NOTE: the host is also port-scanned, so use only targets you are authorized to test."

First observedv0.1.0Jun 17, 2026

TDQS

A5/5.0

Behavior5/5

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

The description explicitly discloses the active port scan behavior, the authorization requirement, the read-only nature of the rest of the checks, and the rate-limiting. This goes well beyond the annotations and gives users a clear understanding of what the tool does and any risks involved.

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?

The description is dense but well-structured, using a colon-separated summary, a usage sentence, and a behavior warning. Every sentence adds necessary information with no fluff or redundancy, making it long but appropriately scannable.

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?

Given the output schema is present and the description names the key return components (score, per-area breakdown, top actions, summaries), there is enough context for an agent to call the tool correctly. The warning about authorization and the distinction from single-purpose tools round out the context.

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

Parameters5/5

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

The single 'domain' parameter is fully described with an example, clarification that schemes and paths are stripped, and a note that the host is also port-scanned. Schema description coverage is 100%, and the description adds important operational context not present in the schema.

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 clearly states the tool performs a one-shot comprehensive security audit of a domain, listing all checks (DNS, SSL, HTTP headers, email auth, port scan, etc.) and the outputs (Health Score, grade, action list). It also explicitly positions it as the default tool for domain health/security questions.

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?

The description provides explicit guidance on when to use this tool versus sibling tools, stating it is the default starting point and directing users to individual tools like ssl_check and email_auth when depth in one area is needed. It also includes an authorization warning for the active port scan.

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

Deploy Server