DechoNet

DechoNet checks domains, links and IP addresses from the outside, using only public information, for site owners, developers, security staff, people building AI agents and anyone who got a suspicious link.

Seen. Remembered.

What you can ask

What an organisation exposes beyond its home page — before an attack tool finds it — with fixes in priority order.
Example path

MCP connector

Server URL: https://dechonet.com/mcp
Login: None
Protocol: MCP 2026-07-28 · io.modelcontextprotocol/tasks
Instructions: DechoNet domain-reconnaissance tools: public, passive checks of domains, URLs and IP addresses (DNS, TLS certificates, HTTP security headers, email authentication, registration data, phishing links, exposure) and the change history DechoNet has observed. No account is needed; an optional DechoNet API key (Authorization: Bearer dn_…) gives a separate rate-limit bucket. Terms of use: https://dechonet.com/terms. Typical flow: for an overall verdict, then the specific tool for each flagged area (, , , , , , , ). reports what changed since DechoNet last looked at a domain (grade drops, new issues, certificate renewals, DNS drift). A few tools save something (a domain to monitor with , expectations to re-check daily, a page report that DechoNet then checks itself); their annotations mark them as not read-only, and every other tool only reads. looks at a page before a login, payment, form submission or download and lists what it did not check. Domain, host and IP lookups carry a signed observation receipt (public keys: https://dechonet.com/.well-known/dechonet-receipts.json). Each result gives a status, key numbers, issues with severity and confidence, recommended fixes and a link to the full report on dechonet.com. Signed-in DechoNet business accounts (session cookie) also see asm_nuclei_start/status/cancel, an active check limited to domains they have verified. Setup guide: https://dechonet.com/mcp

Tools

Reads data26

Changes data4

Skills

None in the store listings or on the server

What you can ask

What an organisation exposes beyond its home page — before an attack tool finds it — with fixes in priority order.

Example path

MCP connector

Server URL

https://dechonet.com/mcp

None

Protocol

MCP 2026-07-28 · io.modelcontextprotocol/tasks

Instructions

DechoNet domain-reconnaissance tools: public, passive checks of domains, URLs and IP addresses (DNS, TLS certificates, HTTP security headers, email authentication, registration data, phishing links, exposure) and the change history DechoNet has observed. No account is needed; an optional DechoNet API key (Authorization: Bearer dn_…) gives a separate rate-limit bucket. Terms of use: https://dechonet.com/terms. Typical flow: for an overall verdict, then the specific tool for each flagged area (, , , , , , , ). reports what changed since DechoNet last looked at a domain (grade drops, new issues, certificate renewals, DNS drift). A few tools save something (a domain to monitor with , expectations to re-check daily, a page report that DechoNet then checks itself); their annotations mark them as not read-only, and every other tool only reads. looks at a page before a login, payment, form submission or download and lists what it did not check. Domain, host and IP lookups carry a signed observation receipt (public keys: https://dechonet.com/.well-known/dechonet-receipts.json). Each result gives a status, key numbers, issues with severity and confidence, recommended fixes and a link to the full report on dechonet.com. Signed-in DechoNet business accounts (session cookie) also see asm_nuclei_start/status/cancel, an active check limited to domains they have verified. Setup guide: https://dechonet.com/mcp

Tools