DechoNet is a domain-reconnaissance MCP server for AI agents. Point it at a domain or IP and it returns a graded, severity-rated diagnosis with concrete remediation steps — not just raw records. **Start here** - `security_scan` — one-shot audit (DNS, SSL, HTTP, email, ports, propagation, rDNS, ASN) → 0–100 health score with a prioritized action list. **Then drill in** - `dns_lookup` — A/AAAA/MX/TXT/NS/SOA/CAA + DNSSEC and SPF/DMARC syntax checks - `dns_propagation` — one record across 8+ global resolvers (stale vs updated) - `ssl_check` — served certificate, chain, TLS version, HSTS → A+…F grade - `http_security` — CSP/HSTS/X-Frame-Options and redirect-chain audit → grade - `email_auth` — MX, SPF, DKIM (15 selectors), DMARC, BIMI, MTA-STS, DANE - `email_header_analysis` — parse a raw header block: hops, auth results, delays - `port_scan` — common TCP ports, open/closed + service names - `reverse_dns` — PTR + FCrDNS verification - `asn_lookup` — operator, prefixes, cloud/CDN/ISP classification, abuse contact - `whois_lookup` — registrar, lifecycle dateags - `ip_info` — the server's own egress IP details - `subnet_calc` — IPv4 CIDR math, fully loca **Notes** - Read-only. `port_scan` and `security_scan` make active TCP connect probes, so only run them on hosts you own or are auth - Free, no API key, no authentication. Rate-limited to keep it fair. - Also available as an npm stdio package (`dlls.
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 24/25 | Endpoint answers the MCP initialize handshake (3829 ms); slow response -1. |
| Protocol revision | 8/10 | Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 30/30 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 34 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 4/5 | seen in a source within 7 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 88% of peers
- This listing 87 · peer median 81
- Latency
- Faster than 4% of peers
- This listing 2,170 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Auth declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
- Protocol revision −2
— Support the current protocol revision.
Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/nodeman/dechonet/mcpcurl -X POST https://server.smithery.ai/nodeman/dechonet/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'