Log inSubmit server
Dechonet MCP logo

Dechonet MCP

by node-man

Audits domains through MCP with DNS, TLS, HTTP, email, network, registration, and subnet analysis tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Dechonet MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "node-man-dechonet-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "dechonet-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 20 tools correctly (1mo ago).

Overview

The node-man/dechonet-mcp MCP server gives AI agents domain reconnaissance tools for DNS, TLS, HTTP headers, email authentication, ports, registration data, and network ownership. It runs locally through npx and calls DechoNet's public API, returning reports with status, KPIs, issues, severity, confidence, and remediation steps. Use it for authorized domain health checks, focused diagnostics, DNS propagation checks, email troubleshooting, or offline IPv4 subnet calculations; no API key is required.

Use cases

  • Audit a domain's overall security posture
  • Diagnose TLS certificate and HTTPS header issues
  • Verify DNS changes across public resolvers
  • Assess email authentication and deliverability
  • Calculate IPv4 subnet ranges locally

Key features

  • DNS, DNSSEC, SPF, and DMARC diagnostics
  • TLS certificate and HTTP security grading
  • Email authentication and header analysis
  • TCP port and domain reconnaissance
  • RDAP, WHOIS, ASN, and reverse DNS lookups
  • Combined 0-100 security health score

Tools20

What Dechonet MCP lets your agent do. Expand a tool for its parameters.

Verified live~5.0k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

4/4 checks healthy over the last 78d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · dechonet-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads474Package downloads in the last 30 days.
Last commit8d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed20Callable tools this server registers over MCP.
Directory activity6 viewsConfig copies, upvotes, and views on AllMCPs.

How Dechonet MCP works

What node-man/dechonet-mcp MCP server does

The node-man/dechonet-mcp MCP server exposes domain and network reconnaissance functions through the Model Context Protocol. It covers DNS records and DNSSEC, TLS certificates and connection properties, HTTP security headers, email authentication, TCP port exposure, DNS propagation, reverse DNS, ASN and BGP ownership, RDAP/WHOIS registration data, certificate-transparency subdomain discovery, lookalike-domain checks, caller IP information, raw email-header analysis, IPv4 subnet calculations, and a combined security scan.

Results are returned as text reports. Depending on the tool, reports include grades, scores, key indicators, detected issues, severity and confidence levels, raw data, resolver comparisons, or recommended actions. The combined scan produces a 0–100 Health Score with an A–F grade and runs several checks in parallel.

How it works

The node-man/dechonet-mcp MCP server uses DechoNet's public API at https://dechonet.com/api/util/*, the same backend used by the site's web tools. The underlying data comes from public DNS, HTTP, TLS, RDAP, Certificate Transparency, and related sources. The server does not require an API key or other authentication.

Most checks are read-only observations. subdomain_discovery uses public Certificate Transparency records without sending packets to the target, while subnet_calc performs its calculation locally and does not make a network request. email_header_analysis accepts a complete raw header block and reconstructs its delivery route, authentication results, delays, and TLS status.

port_scan is different: it makes active TCP connect probes against a fixed set of common ports. The comprehensive security_scan includes that port scan, so use either tool only against systems you own or are authorized to test. The connection can appear in the target's logs, although the probe does not authenticate, exploit, or transfer data.

Setup and configuration

For a local stdio connection, run:

Terminal
npx -y dechonet-mcp

Claude Desktop can launch the package with npx and the arguments -y and dechonet-mcp. The README identifies Claude Desktop as a supported client and also describes a local Node build and an optional SSE mode for development or remote-style HTTP connections.

Configuration can use DECHONET_URL to change the API base URL, DECHONET_LOCALE to select English or Korean responses, and PORT to set the SSE port. Their documented defaults are https://dechonet.com, en, and 3100, respectively. None is required for the default npx setup.

Tools and capabilities

  • Inspect A, AAAA, MX, TXT, NS, SOA, and CAA records, including SPF, DMARC, and DNSSEC diagnostics.
  • Compare DNS answers across eight or more public resolvers to identify stale propagation.
  • Grade certificates, TLS versions, chain trust, HSTS, redirect chains, and HTTP security headers.
  • Review SPF, DKIM, DMARC, BIMI, MTA-STS, TLS-RPT, DANE, and MX-host blacklist status.
  • Identify open common TCP ports, PTR and forward-confirmed reverse DNS, ASN ownership, prefixes, and abuse contacts.
  • Retrieve domain registration dates, registrar data, nameservers, and EPP status flags through RDAP with WHOIS fallback.
  • Discover certificate-log subdomains, generate registered lookalike variants, inspect the server's observed public IP, analyze email headers, and calculate IPv4 subnet ranges.

Limitations and notes

The node-man/dechonet-mcp MCP server is subject to rate limits for network-backed checks. Its IP information describes the MCP server's egress address, which may not be the end user's address. A registered lookalike domain is not evidence of abuse, and findings should be investigated in context. The port and combined security scans require authorization for the targets being tested.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Dechonet MCP

Run `npx -y dechonet-mcp` for a local stdio server, or add that command and its arguments to an MCP client configuration.

Yes. The README provides Claude Desktop configuration using npx and identifies Claude Desktop as a supported client.

No. The tools use DechoNet's public API and require no API key or authentication.

Yes. `port_scan` probes a fixed set of common TCP ports, and `security_scan` includes an active port scan. Scan only authorized targets.

Yes. `dns_propagation` compares a DNS record across eight or more public resolvers and reports stale or updated responses.

Related MCP servers

All in Security All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewDechonet MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/node-man-dechonet-mcp?style=directory)](https://allmcps.com/mcp/node-man-dechonet-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/node-man-dechonet-mcp"><img src="https://allmcps.com/api/badge/node-man-dechonet-mcp?style=directory" alt="Dechonet MCP on AllMCPs" /></a>