# com.dechonet/mcp (remote · dechonet.com)

20 domain recon tools for AI agents: DNS, SSL, headers, email, subdomains, lookalikes, changes.

- Trust score: 76/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-22

## Components

- remote · `dechonet.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/com-dechonet-mcp/dechonet.md), [page](https://verifymcp.io/servers/com-dechonet-mcp/dechonet)
- npm · `dechonet-mcp`: 80/100, [markdown](https://verifymcp.io/servers/com-dechonet-mcp/dechonet-mcp.md), [page](https://verifymcp.io/servers/com-dechonet-mcp/dechonet-mcp)

## Channel facts

- Endpoint: `https://dechonet.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-22.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 4153 tokens (~188/item across 22 items; 20 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the com.dechonet/mcp server?

com.dechonet/mcp is a hosted endpoint at https://dechonet.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-dechonet-mcp 'https://dechonet.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-dechonet-mcp": {
      "url": "https://dechonet.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-dechonet-mcp": {
      "type": "http",
      "url": "https://dechonet.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-dechonet-mcp]
url = "https://dechonet.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-dechonet-mcp": {
      "type": "remote",
      "url": "https://dechonet.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-dechonet-mcp --url 'https://dechonet.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-dechonet-mcp:
    url: "https://dechonet.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-dechonet-mcp": {
      "Transport": "http",
      "Url": "https://dechonet.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-dechonet-mcp -t streamable-http -u 'https://dechonet.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-dechonet-mcp": {
      "type": "http",
      "url": "https://dechonet.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 74, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-16 (score 73)

First indexed and scored.

## MCP tools (20)

### `dns_lookup` (~183 tokens)

DNS Lookup

Query DNS records (A, AAAA, MX, TXT, NS, SOA, CAA) for a domain and validate email-related records, including DNSSEC presence and SPF/DMARC syntax, returning severity-rated diagnostics. Use this for a single authoritative answer about one domain. Use dns_propagation instead when you need to compare answers across multiple global resolvers (e.g., right after a change), or email_auth for a full SPF/DKIM/DMARC deliverability assessment. Read-only; requires no API key or authentication; subject to rate limiting. Returns a text report: status, KPI summary, detected issues, and recommended actions.

Input parameters:

- `domain` (string, required): Registrable domain or hostname to query, without scheme or path (e.g., 'example.com' or 'mail.example.com'). Do not include 'http://' or a trailing slash.

Output parameters:

- `actions` (array): Recommended next actions, most important first
- `grade` (string): Letter grade (A+ to F) when the tool grades the target
- `issues` (array): Detected problems, severity-rated
- `kpis` (array): Key metrics as label/value pairs
- `reportUrl` (string): Human-facing interactive report for this exact lookup on dechonet.com
- `score` (number): 0-100 score when the tool scores the target
- `status` (string): Overall verdict, e.g. 'good' | 'warning' | 'bad' | 'info' | 'unknown'
- `summary` (string): One-paragraph interpretation of the result

### `ssl_check` (~212 tokens)

SSL Certificate Check

Inspect a host's served TLS/SSL certificate and connection: expiry date, issuer, SAN list, chain integrity, TLS version, and HSTS, returning an A+ to F grade weighted by certificate validity (40%), TLS version (25%), chain trust (15%), and HSTS (20%). Use this to diagnose certificate or HTTPS-handshake problems for one host. Use http_security instead to audit response security headers, or security_scan for an all-in-one domain report. Read-only: it completes a TLS handshake but sends no application data; requires no API key; rate-limited. Returns a text report: grade, expiry/issuer KPIs, issues, and actions.

Input parameters:

- `host` (string, required): Hostname to inspect, without scheme (e.g., 'example.com'). The host portion of a pasted URL is also accepted.
- `port` (number): TCP port for the TLS handshake. Defaults to 443 (standard HTTPS); set this only for a non-standard HTTPS port such as 8443.

Output parameters:

- `actions` (array): Recommended next actions, most important first
- `grade` (string): Letter grade (A+ to F) when the tool grades the target
- `issues` (array): Detected problems, severity-rated
- `kpis` (array): Key metrics as label/value pairs
- `reportUrl` (string): Human-facing interactive report for this exact lookup on dechonet.com
- `score` (number): 0-100 score when the tool scores the target
- `status` (string): Overall verdict, e.g. 'good' | 'warning' | 'bad' | 'info' | 'unknown'
- `summary` (string): One-paragraph interpretation of the result

### `http_security` (~172 tokens)

HTTP Security Headers Audit

Follow a URL's HTTP redirect chain and audit response security headers (CSP, HSTS, X-Frame-Options, COOP, CORP, COEP, Permissions-Policy), grading A+ to F and flagging information leaks such as server-version disclosure. Use this for HTTP-layer/header posture. Use ssl_check instead for certificate or TLS-handshake issues, or security_scan for a full domain report. Read-only (an HTTP GET-style probe that sends no payload); requires no API key; rate-limited. Returns a text report: grade, header findings, redirect trace, issues, and actions.

Input parameters:

- `url` (string, required): Full URL including scheme (e.g., 'https://example.com/path'). If the scheme is omitted, https:// is assumed. Redirects are followed starting from this URL.

Output parameters:

- `actions` (array): Recommended next actions, most important first
- `grade` (string): Letter grade (A+ to F) when the tool grades the target
- `issues` (array): Detected problems, severity-rated
- `kpis` (array): Key metrics as label/value pairs
- `reportUrl` (string): Human-facing interactive report for this exact lookup on dechonet.com
- `score` (number): 0-100 score when the tool scores the target
- `status` (string): Overall verdict, e.g. 'good' | 'warning' | 'bad' | 'info' | 'unknown'
- `summary` (string): One-paragraph interpretation of the result

### `email_auth` (~183 tokens)

Email Authentication Check

Assess a domain's email authentication and deliverability posture: MX records, SPF, DMARC, DKIM (probes 15 common selectors), BIMI, MTA-STS, TLS-RPT, and DANE, plus a blacklist check across all MX hosts, returning a 0-100 deliverability score. Use this for a full sending/receiving readiness review of a domain. Use dns_lookup instead if you only need raw TXT/MX records, or email_header_analysis to diagnose a specific message that was already sent. Read-only; requires no API key; rate-limited. Returns a text report: score, per-mechanism KPIs, issues, and actions.

Input parameters:

- `domain` (string, required): Email domain to assess — the part after '@' (e.g., 'example.com'). An IP address is also accepted for reverse/PTR-based checks.

Output parameters:

- `actions` (array): Recommended next actions, most important first
- `grade` (string): Letter grade (A+ to F) when the tool grades the target
- `issues` (array): Detected problems, severity-rated
- `kpis` (array): Key metrics as label/value pairs
- `reportUrl` (string): Human-facing interactive report for this exact lookup on dechonet.com
- `score` (number): 0-100 score when the tool scores the target
- `status` (string): Overall verdict, e.g. 'good' | 'warning' | 'bad' | 'info' | 'unknown'
- `summary` (string): One-paragraph interpretation of the result

### `port_scan` (~224 tokens)

Open Port Scan

Probe a host for a fixed set of common TCP ports (HTTP, HTTPS, SSH, FTP, SMTP, DNS, and common databases) and report which are open, the service name, and the response time. BEHAVIOR: this makes an ACTIVE TCP connection to the target. It is non-intrusive — a connect probe only; it does not authenticate, send exploits, or transfer data — and changes nothing on the target (read-only), but the connection is visible in the target's logs, so only scan hosts you own or are explicitly authorized to test. Use this to confirm which services are exposed. Use ssl_check or http_security instead to assess a specific service's configuration. Requires no API key; rate-limited. Returns a per-port open/closed list with service names.

Input parameters:

- `host` (string, required): Hostname or IP to probe (e.g., 'example.com' or '203.0.113.10'). A 'host:port' form is accepted to hint a specific port. Only supply targets you own or are authorized to test.

Output parameters:

- `actions` (array): Recommended next actions, most important first
- `grade` (string): Letter grade (A+ to F) when the tool grades the target
- `issues` (array): Detected problems, severity-rated
- `kpis` (array): Key metrics as label/value pairs
- `reportUrl` (string): Human-facing interactive report for this exact lookup on dechonet.com
- `score` (number): 0-100 score when the tool scores the target
- `status` (string): Overall verdict, e.g. 'good' | 'warning' | 'bad' | 'info' | 'unknown'
- `summary` (string): One-paragraph interpretation of the result

### `dns_propagation` (~154 tokens)

DNS Propagation Check

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 parameters:

- `domain` (string, required): Domain whose record to compare across resolvers (e.g., 'example.com'), without scheme or path.
- `type` (string): DNS record type to compare across resolvers. Defaults to A (IPv4 address), the most common propagation check.

Output parameters:

- `actions` (array): Recommended next actions, most important first
- `grade` (string): Letter grade (A+ to F) when the tool grades the target
- `issues` (array): Detected problems, severity-rated
- `kpis` (array): Key metrics as label/value pairs
- `reportUrl` (string): Human-facing interactive report for this exact lookup on dechonet.com
- `score` (number): 0-100 score when the tool scores the target
- `status` (string): Overall verdict, e.g. 'good' | 'warning' | 'bad' | 'info' | 'unknown'
- `summary` (string): One-paragraph interpretation of the result

### `reverse_dns` (~172 tokens)

Reverse DNS (PTR) Lookup

Resolve the PTR (reverse DNS) record for an IPv4 or IPv6 address and verify forward-confirmed reverse DNS (FCrDNS) by checking that the PTR hostname resolves back to the same IP. Infers the hosting provider from PTR naming patterns. Use this to validate mail-server rDNS or identify a single IP's host. Use asn_lookup instead for network/BGP ownership of the IP. Read-only; requires no API key; rate-limited. Returns the PTR hostname, FCrDNS pass/fail, and a provider guess.

Input parameters:

- `ip` (string, required): IP address to reverse-resolve, IPv4 or IPv6 (e.g., '8.8.8.8' or '2001:4860:4860::8888'). Must be an IP, not a hostname.

Output parameters:

- `actions` (array): Recommended next actions, most important first
- `grade` (string): Letter grade (A+ to F) when the tool grades the target
- `issues` (array): Detected problems, severity-rated
- `kpis` (array): Key metrics as label/value pairs
- `reportUrl` (string): Human-facing interactive report for this exact lookup on dechonet.com
- `score` (number): 0-100 score when the tool scores the target
- `status` (string): Overall verdict, e.g. 'good' | 'warning' | 'bad' | 'info' | 'unknown'
- `summary` (string): One-paragraph interpretation of the result

### `asn_lookup` (~151 tokens)

ASN / BGP Lookup

Look up Autonomous System (ASN) / BGP information for an IP address or AS number: the network operator, announced prefixes, abuse contact, and a classification (cloud, CDN, ISP, hosting, or enterprise). Use this to identify who runs a network or whether an IP is cloud/CDN-hosted. Use reverse_dns instead for the host-level PTR name of a single IP. Read-only; requires no API key; rate-limited. Returns operator, prefixes, classification, and abuse contact.

Input parameters:

- `query` (string, required): An IP address (e.g., '1.1.1.1') or an AS number in 'AS####' form (e.g., 'AS13335').

Output parameters:

- `actions` (array): Recommended next actions, most important first
- `grade` (string): Letter grade (A+ to F) when the tool grades the target
- `issues` (array): Detected problems, severity-rated
- `kpis` (array): Key metrics as label/value pairs
- `reportUrl` (string): Human-facing interactive report for this exact lookup on dechonet.com
- `score` (number): 0-100 score when the tool scores the target
- `status` (string): Overall verdict, e.g. 'good' | 'warning' | 'bad' | 'info' | 'unknown'
- `summary` (string): One-paragraph interpretation of the result

### `whois_lookup` (~141 tokens)

WHOIS / RDAP Domain Lookup

Retrieve domain registration data via RDAP (with WHOIS fallback): registrar, creation/expiry/update dates, nameservers, and EPP status flags, highlighting risk states such as clientHold and pendingDelete. Use this for ownership, lifecycle, and expiry questions about a registered domain. Use dns_lookup instead for live DNS records, or reverse_dns/asn_lookup for IP-level ownership. Read-only; requires no API key; rate-limited. Returns registrar, key dates, nameservers, and status flags.

Input parameters:

- `domain` (string, required): Registered domain name to look up (e.g., 'example.com'). A subdomain is normalized to its registrable domain.

Output parameters:

- `actions` (array): Recommended next actions, most important first
- `grade` (string): Letter grade (A+ to F) when the tool grades the target
- `issues` (array): Detected problems, severity-rated
- `kpis` (array): Key metrics as label/value pairs
- `reportUrl` (string): Human-facing interactive report for this exact lookup on dechonet.com
- `score` (number): 0-100 score when the tool scores the target
- `status` (string): Overall verdict, e.g. 'good' | 'warning' | 'bad' | 'info' | 'unknown'
- `summary` (string): One-paragraph interpretation of the result

### `subdomain_discovery` (~184 tokens)

Subdomain Discovery

Enumerate the subdomains of a domain from Certificate Transparency logs — fully passive (no packets are sent to the target; CT logs are public records of every TLS certificate ever issued). Flags operational-looking names (dev, staging, admin, vpn, legacy) and wildcard certificates, because forgotten subdomains are a common takeover path. Use this as the first recon step to map a domain's attack surface. Use dns_lookup to check whether a discovered name still resolves, or lookalike_domains for typosquat variants of the domain name itself. Read-only; requires no API key; rate-limited. Returns the subdomain count, risky-name count, wildcard flag, and the hostname list.

Input parameters:

- `domain` (string, required): Registrable domain to enumerate (e.g., 'example.com'), without scheme or path. Subdomains found in CT logs for this domain are returned.

Output parameters:

- `actions` (array): Recommended next actions, most important first
- `grade` (string): Letter grade (A+ to F) when the tool grades the target
- `issues` (array): Detected problems, severity-rated
- `kpis` (array): Key metrics as label/value pairs
- `reportUrl` (string): Human-facing interactive report for this exact lookup on dechonet.com
- `score` (number): 0-100 score when the tool scores the target
- `status` (string): Overall verdict, e.g. 'good' | 'warning' | 'bad' | 'info' | 'unknown'
- `summary` (string): One-paragraph interpretation of the result

### `lookalike_domains` (~200 tokens)

Lookalike Domain Check

Generate the typosquat/lookalike variants of a domain that phishers actually register — homoglyph swaps (l→1, o→0, rn→m), TLD swaps (.com→.co), character omissions, transpositions, repetitions, hyphenations — and check which of them are currently registered (live NS delegation via DoH). Use this to assess brand-impersonation and phishing exposure for a domain the user is responsible for. A registered variant is NOT proof of abuse (it may be an unrelated legitimate site) — follow up with whois_lookup on each hit for its owner and registration date. Read-only; requires no API key; rate-limited. Returns generated/checked counts and the registered variants with the technique that produced each.

Input parameters:

- `domain` (string, required): Domain to protect (e.g., 'example.com'), without scheme or path. Variants of its label and TLD are generated and checked.

Output parameters:

- `actions` (array): Recommended next actions, most important first
- `grade` (string): Letter grade (A+ to F) when the tool grades the target
- `issues` (array): Detected problems, severity-rated
- `kpis` (array): Key metrics as label/value pairs
- `reportUrl` (string): Human-facing interactive report for this exact lookup on dechonet.com
- `score` (number): 0-100 score when the tool scores the target
- `status` (string): Overall verdict, e.g. 'good' | 'warning' | 'bad' | 'info' | 'unknown'
- `summary` (string): One-paragraph interpretation of the result

### `ip_info` (~113 tokens)

My IP Info

Report information about the caller's own public IP as seen by the server: IPv4/IPv6 address, ISP, ASN, approximate geolocation, and proxy/VPN heuristics. Takes no input — it reflects the egress IP of THIS MCP server's network, which is usually NOT the end user's IP. Use this to discover the server's outbound IP or test connectivity. To inspect a specific, known IP instead, use asn_lookup or reverse_dns. Read-only; requires no API key; rate-limited.

Output parameters:

- `actions` (array): Recommended next actions, most important first
- `grade` (string): Letter grade (A+ to F) when the tool grades the target
- `issues` (array): Detected problems, severity-rated
- `kpis` (array): Key metrics as label/value pairs
- `reportUrl` (string): Human-facing interactive report for this exact lookup on dechonet.com
- `score` (number): 0-100 score when the tool scores the target
- `status` (string): Overall verdict, e.g. 'good' | 'warning' | 'bad' | 'info' | 'unknown'
- `summary` (string): One-paragraph interpretation of the result

### `email_header_analysis` (~198 tokens)

Email Header Analysis

Parse raw email headers to reconstruct the delivery path (each Received hop in order), extract SPF/DKIM/DMARC authentication results, measure per-hop delays, and flag unencrypted (non-TLS) hops. Use this to diagnose a specific message that was already delivered — spoofing, delays, or where mail was lost. Use email_auth instead to assess a domain's sending configuration before sending. Read-only; requires no API key; rate-limited. INPUT is the full raw header block. OUTPUT is a text report containing: the ordered hop route, per-mechanism auth results (pass/fail), detected inter-hop delays, and the encryption status of each hop.

Input parameters:

- `headers` (string, required): The complete raw email header block, copied verbatim — every line from the first 'Received:'/'From:' down to the blank line before the body. Paste as-is, including folded continuation lines; do not i…

Output parameters:

- `actions` (array): Recommended next actions, most important first
- `grade` (string): Letter grade (A+ to F) when the tool grades the target
- `issues` (array): Detected problems, severity-rated
- `kpis` (array): Key metrics as label/value pairs
- `reportUrl` (string): Human-facing interactive report for this exact lookup on dechonet.com
- `score` (number): 0-100 score when the tool scores the target
- `status` (string): Overall verdict, e.g. 'good' | 'warning' | 'bad' | 'info' | 'unknown'
- `summary` (string): One-paragraph interpretation of the result

### `subnet_calc` (~159 tokens)

IPv4 Subnet Calculator

Compute IPv4 subnet details from CIDR notation entirely locally — no network call: network and broadcast addresses, usable host range, total usable hosts, subnet mask, and wildcard mask. /31 and /32 are handled per RFC 3021 (point-to-point / single host). Use this for IPv4 address planning. It does not query DNS or contact any host, so it is purely computational. Requires no API key and is NOT rate-limited (computed in-process). Returns the calculated fields as text.

Input parameters:

- `cidr` (string, required): IPv4 address with a CIDR prefix length 0-32 (e.g., '192.168.1.0/24'). IPv4 only; host bits may be any address inside the block.

Output parameters:

- `broadcast` (string): Broadcast address
- `firstHost` (string): First usable host
- `lastHost` (string): Last usable host
- `network` (string): Network address
- `prefix` (number): CIDR prefix length
- `reportUrl` (string): Human-facing interactive report on dechonet.com
- `subnetMask` (string): Dotted-decimal subnet mask
- `totalHosts` (number): Usable host count
- `wildcardMask` (string): Wildcard (inverse) mask

### `security_scan` (~216 tokens)

Full Domain Security Scan

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 parameters:

- `domain` (string, required): 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 parameters:

- `actions` (array): Top recommended actions
- `areas` (array): Per-area verdicts (dns, ssl, http, email, port, propagation, rdap, reverseDns, asn)
- `grade` (string): Letter grade A+ to F
- `reportUrl` (string): Human-facing interactive report on dechonet.com
- `score` (number): Health Score 0-100

### `owasp_check` (~282 tokens)

OWASP Security Checkup

Assess a domain's OWASP posture from EXTERNAL OBSERVATION only: the OWASP Secure Headers Project plus the externally observable Top 10 subset — A02 Cryptographic Failures (TLS/cert), A05 Security Misconfiguration (header/info leaks), and A06 Vulnerable & Outdated Components (version disclosure) — returning an A+ to F grade. IMPORTANT SCOPE: this does NOT check A01 (Access Control), A03 (Injection), A04, A07 (Authentication), A08, A09, or A10 (SSRF) — those require authenticated access or active/injection testing and are explicitly reported as out-of-scope, never as "pass". Do not present this as a full OWASP Top 10 assessment. Unlike security_scan this is fully PASSIVE (a normal HTTP GET plus a public CT-log lookup, no port scan), so it is safe and lawful to run on domains you do not own. Use http_security or ssl_check for depth on one layer. Read-only; requires no API key; rate-limited. Returns a text report: grade, per-category findings, the out-of-scope list, and a shareable report link.

Input parameters:

- `host` (string, required): Hostname to assess, without scheme (e.g., 'example.com'). The host portion of a pasted URL is also accepted.

Output parameters:

- `checks` (array): Per observable category: Secure Headers, A02, A05, A06
- `grade` (string): OWASP posture grade A+ to F, over the observable categories only
- `notObservable` (array): Top 10 categories NOT checked (need authenticated/active testing)
- `reportUrl` (string): Human-facing interactive report on dechonet.com
- `score` (number): 0-100 across the categories that could be evaluated

### `impersonation_exposure` (~252 tokens)

Brand Impersonation Exposure

Assess how exposed a domain is to brand impersonation and phishing, PASSIVELY: live typosquat/lookalike domains (homoglyph, omission, transposition, TLD swap) that actually resolve, operational subdomains (dev/staging/admin) exposed in CT logs, and whether a wildcard certificate exists — returning an A+ (low exposure) to F (high exposure) grade. NEUTRAL FRAMING (important): a registered lookalike domain is NOT proof of impersonation — it may be a legitimate third party or the owner's own. Report it as exposure to verify, never as an accusation against a specific domain. Fully passive: public DNS delegation checks plus public CT-log queries, sending nothing to the target or the lookalike domains, so it is safe and lawful to run. Use lookalike_domains or subdomain_discovery for the raw per-tool detail. Read-only; requires no API key; rate-limited. Returns a text report: grade, counts, per-category findings, and a shareable report link.

Input parameters:

- `domain` (string, required): Registrable domain to assess for impersonation exposure (e.g., 'example.com'). Scheme and path are stripped.

Output parameters:

- `grade` (string): Exposure grade A+ (low exposure) to F (high exposure)
- `reportUrl` (string): Human-facing interactive report on dechonet.com
- `riskySubdomainCount` (number): Exposed operational subdomains found
- `score` (number): 0-100, higher = less exposed
- `typosquatCount` (number): Live third-party lookalike/typosquat domains (variants on the domain's own nameservers/IP are excluded)
- `wildcard` (boolean): Whether a wildcard certificate exists

### `domain_changes` (~246 tokens)

Domain Change History

Report what has CHANGED for a domain over time — the security regressions and drift that DechoNet's daily monitoring has recorded across every watch on the domain (SSL grade, headers, DNS, OWASP posture, impersonation exposure, etc.). Use this to answer "what changed on my domain since yesterday/last week?" — a question that requires persistent snapshots and therefore cannot be reconstructed from a single live lookup. Call it FIRST whenever a domain you have looked at before comes up again. Two sources: (a) the daily watch timeline if the domain is watched (start one with watch_domain), and (b) even without a watch, the difference between the last two stored lookups of each tool — so a second lookup already yields a comparison. The point-in-time tools (security_scan, owasp_check, ssl_check) give the current state instead. Read-only; requires no API key; rate-limited. Returns the monitored tools, a newest-first change timeline, lookup-to-lookup changes, and a link to manage monitoring.

Input parameters:

- `domain` (string, required): Domain whose recorded change history to fetch (e.g., 'example.com'). Scheme and path are stripped.

Output parameters:

- `changeCount` (number): Number of changes recorded
- `changes` (array): Recorded changes, newest first
- `domain` (string)
- `historyChangeCount` (number): Changes found between the last two stored lookups per tool (no watch needed)
- `historyChanges` (array): Lookup-to-lookup changes, newest first
- `reportUrl` (string): Where a human can start or manage monitoring
- `watched` (boolean): Whether the domain is under an active daily watch

### `watch_domain` (~256 tokens)

Watch a Domain (daily re-check)

Start (or reuse) a daily DechoNet watch on a domain so that changes are recorded over time — SSL grade/issuer/expiry, DNS records, HTTP security headers, domain registration, and optionally OWASP posture and impersonation exposure. Use this once when the user cares about a domain beyond a one-off check (their own domain, a client, a vendor, a target under investigation). After this, domain_changes answers "what changed since last time?" from real daily snapshots. Not read-only (it creates a watch record) but idempotent: watching an already-watched domain returns the existing watch. No account, no email, no PII — a watch is keyed by domain+tool and its history page is a public unguessable URL you can share with the user. Rate-limited (a few watches per minute).

Input parameters:

- `domain` (string, required): Registered domain to watch (e.g., 'example.com'). Scheme and path are stripped.
- `tools` (array): Which checks to re-run daily. Default ['ssl','dns','http','rdap'] (certificate, DNS, security headers, registration). Add 'owasp' and/or 'impersonation' for posture and brand-exposure tracking.

Output parameters:

- `domain` (string)
- `failed` (array): Tools that could not be watched (rate limit or error)
- `reportUrl` (string)
- `watches` (array): One entry per tool now under a daily watch

### `golive_check` (~198 tokens)

Go-Live Readiness Checklist

Check whether a domain is ready to launch or migrate — a go/no-go verdict over five essentials: DNS resolves to an IP, has propagated consistently across global resolvers, SSL/TLS is ready, the site is reachable over HTTPS, and the domain registration is not about to expire. Use this right before flipping DNS to a new server, or to confirm a migration has landed. It answers "can I switch over yet?"; use security_scan for a security posture grade or the individual tools for depth. Any failing essential yields not_ready; only cautions yields caution; all clear yields ready. Read-only (a passive multi-probe, though it does resolve and fetch the domain); requires no API key; rate-limited. Returns the verdict, per-check statuses, and a shareable report link.

Input parameters:

- `domain` (string, required): Domain to check for launch/migration readiness (e.g., 'example.com'). Scheme and path are stripped.

Output parameters:

- `checks` (array)
- `failCount` (number)
- `passCount` (number)
- `reportUrl` (string): Human-facing interactive report on dechonet.com
- `verdict` (string): 'ready' | 'caution' | 'not_ready'
- `warnCount` (number)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-dechonet-mcp/dechonet#diagnostics

## Score history

- 2026-09-22: 76
- 2026-09-21: 76
- 2026-09-20: 75
- 2026-09-19: 75
- 2026-09-18: 74
- 2026-09-17: 74
- 2026-09-16: 73

## Common questions

### What is the com.dechonet/mcp server?

com.dechonet/mcp is listed in the public MCP registry as com.dechonet/mcp. 20 domain recon tools for AI agents: DNS, SSL, headers, email, subdomains, lookalikes, changes. This page covers its hosted endpoint (https://dechonet.com/mcp).

### Is the com.dechonet/mcp server safe to use?

com.dechonet/mcp scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the com.dechonet/mcp server expose?

com.dechonet/mcp exposes 20 tools: dns_lookup, ssl_check, http_security, email_auth, port_scan, and 15 more. Their descriptions and schemas cost roughly 3,896 tokens of context every time the server is loaded.

### Does the com.dechonet/mcp server require authentication?

No. We connected to com.dechonet/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the com.dechonet/mcp server still maintained?

com.dechonet/mcp is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://dechonet.com/mcp
- Repository: https://github.com/node-man/dechonet-mcp
- Website: https://dechonet.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-dechonet-mcp/dechonet.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-dechonet-mcp/dechonet.json
- HTML version of this page: https://verifymcp.io/servers/com-dechonet-mcp/dechonet