com.dechonet/mcp
NPM · DECHONET-MCP · 2 COMPONENTS
34 security tools for AI agents: phishing links, exposure maps, DNS, SSL, PQC, history, pivots.
Available components
Last scanned (21 hours ago)
Scores higher than 82% of npm servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to node-man/dechonet-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 8532 tokens (~250/item across 34 items; 34 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 34 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 35 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 15 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 1.8.0 → 1.9.0 functional
- 13 Nov 26 +1
- Stability: 0.97 → pass security
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
- Security disclosure: unverified → fail ▼ functional
- 8 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 7 Nov 26 −3
- Stability: pass → 0.80 functional
- 6 Nov 26 0
- Package version: 1.7.0 → 1.8.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed npm/dechonet-mcp@1.9.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | node-man/dechonet-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/node-man/dechonet-mcp/.github/workflows/publish.yml@refs/tags/v1.9.0 |
| Rekor log index | 3880655046 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:19442bc773b0eb6348997f8d57e768ac73c6b1bf7649c17dd5738a242095811ea8a5ebfb9fc964c132920c066cde5fb770c9c30da3e490f7b2cf392ed |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
asn_lookup ASN / BGP Lookup ~179
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). For an IPv4 address it also reports whether the address is on the Tor Project exit list, as information that does not change the result. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | An IP address (e.g., '1.1.1.1') or an AS number in 'AS####' form (e.g., 'AS13335'). |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| observation | object | – | How much was actually observed and when. A partial observation means some checks did not answer: missing parts are not verified, never clean. |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| reportUrl | string | yes | Human-facing interactive report for this exact lookup on dechonet.com |
| score | number | – | 0-100 score when the tool scores the target |
| status | string | yes | Overall verdict, e.g. 'good' | 'warning' | 'bad' | 'info' | 'unknown' |
| summary | string | – | One-paragraph interpretation of the result |
No examples provided.
check_before_action Check a Page Before Logging In or Paying ~397
Check the page an agent is about to log in, pay, download from or submit to: whether the address impersonates a brand, how new the domain is, whether DechoNet or a licensed feed has already flagged it, and — opened from Seoul (and Tokyo for Japan-targeted pages) as a phone — what the page turns into, including text it hides from people but an AI agent would read (instructions to ignore its rules, hand over secrets or keep the user out of it raise the answer to suspicious). For a payment, the caller can report the page structure as host names only (where forms submit, which origins frames come from, whether the card fields sit on the page itself or in a frame and that frame's origin): card fields outside a known payment provider (Stripe, PayPal, Braintree, Adyen, Square, Checkout.com, Toss Payments, KG Inicis, NHN KCP, NICE Payments, Naver Pay, Korean card issuers and banks) are reported as suspicious — a fake card window inside a real shop shows up only this way. Paths, queries, field values and page text are not accepted, and the structure is not stored. Verdicts: danger, suspicious, unreachable, official, no_signals. no_signals means none of the checks found a warning sign and is not a statement that the page is safe; 'unchecked' lists what was not looked at. Rate-limited. Returns signals with their source and a signed observation record (host and verdict only).
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | What is about to happen on the page |
| expectedBrand | string | – | Brand the page is believed to belong to (e.g. 'PayPal', 'Shinhan Card'); a domain without that name is noted |
| page | object | – | Optional page structure, host names only |
| url | string | yes | Address of the page (https://…) |
| Name | Type | Req | Description |
|---|---|---|---|
| ageDays | number|null | – | Days since the domain was registered, when known |
| host | string | yes | Host the address ended on (after redirects) |
| paymentProvider | string|null | – | Payment provider recognised for the page or its card frame |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| signals | array | yes | – |
| unchecked | array | yes | What was not looked at: 'page_structure' (no structure sent for a login or payment), 'rendering' (the page was not opened in a browser), 'hidden_instructions' (so hidden text aimed at AI agents was n… |
| verdict | string | yes | danger: evidence the page impersonates or attacks; suspicious: warning signs; unreachable: could not be read; official: the brand's own domain; no_signals: none of the checks found a warning sign — n… |
No examples provided.
crypto_check_before_sign Check Before Signing or Sending (Crypto) ~280
Before an agent signs or sends from a crypto wallet: send the destination address (to), the page that asked (url) and/or the wallet request it is about to approve (request: the EIP-1193 method and params). The address is checked for its chain and checksum, the US Treasury OFAC sanctions list, the addresses the FBI published in its alerts, whether Tether froze USDT at it, and pages DechoNet judged dangerous that showed it; the page goes through the phishing link check and the official exchange, wallet and dApp list; the request is read for what approving it would allow (unlimited token approval, approval for a whole NFT collection, Permit/Permit2 signatures, Seaport orders, raw eth_sign, transfers). Verdicts: danger, suspicious, no_signals. no_signals means none of the checks found a warning sign and is not a statement that the transaction is harmless; 'unchecked' lists what was not looked at (balances, token contracts, simulation). Nothing sent is stored. Rate-limited.
| Name | Type | Req | Description |
|---|---|---|---|
| request | object | – | The wallet request about to be approved |
| to | string | – | Destination wallet address (0x…, T…, bc1…, Solana) |
| url | string | – | Address of the page that asked for the signature or transfer (https://…) |
| Name | Type | Req | Description |
|---|---|---|---|
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| request | – | – | What approving the request would allow |
| signals | array | yes | – |
| unchecked | array | yes | – |
| verdict | string | yes | danger: a check found a danger sign; suspicious: a warning sign; no_signals: none of the checks found one — not a statement that the transaction is harmless (see unchecked) |
No examples provided.
crypto_dapp_check dApp & Link Check (Crypto) ~390
Open a crypto page — a dApp, airdrop, claim or mint link — and report what it asks a wallet to do. DechoNet opens it in an isolated Chromium (Seoul) with a test wallet that holds nothing (EVM, Solana and TRON): it presses the page's "Connect wallet" button once (or one "Claim" button when there is none) and the test wallet in a wallet picker once; it types nothing and submits no form, and the test wallet connects with a burn address and refuses every signature and transaction. Reported: each wallet request in order with what approving it would allow (unlimited token approvals, setApprovalForAll, Permit/Permit2 signatures, transfers, Solana transactions, TRON approvals and account-permission changes), drainer-kit code markers in the page scripts, a connect button that sends the visitor to another site, and the phishing link check verdict of the same link (including whether it is the brand's own domain). Verdicts: danger, suspicious, official, no_signals, unreachable. no_signals means none of these were seen and is not a statement that the page is harmless: drainers that wait for a second press, show nothing to an automated browser or ask only after a sign-in can go unseen, and on new drainer samples few were caught by wallet requests alone (figures on dechonet.com/methodology); 'unchecked' lists what was not looked at. Every call opens the page (no cached answer), so it takes longer than the other checks, and it has a per-minute rate limit and a daily limit shared by all callers. Only the host, the verdict and the kinds of request are kept (90 days); no API key.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Address of the page to open (https://…; a bare domain is opened over https) |
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | – | The host the page ended on |
| phishingVerdict | string|null | – | The phishing link check verdict for the same link |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| rendered | boolean | yes | False when the page could not be opened with the test wallet (then little was seen) |
| requests | array | yes | Wallet requests the page made, in order |
| signals | array | yes | – |
| unchecked | array | yes | – |
| verdict | string | yes | no_signals: none of the checks saw a warning sign — not a statement that the page is harmless (see unchecked) |
No examples provided.
crypto_exchange_check Official Crypto Exchange Address Check ~204
Check whether a domain or link is the official address of a crypto exchange, wallet or dApp — Korean exchanges (Upbit, Bithumb, Coinone, GOPAX, DigitalX/Korbit) and major global exchanges, wallets and dApps — compared with the addresses the companies publish themselves (the Korean exchanges' council member list, app store developer websites, verified GitHub organisations). Verdicts: official, danger (not official and the phishing check found impersonation evidence), not_official (uses a name but is not an official address — the name alone is not impersonation), not_exchange. A domain that uses a name also gets its registration date, the first certificate DechoNet saw for it, and a phishing check of its front page (which may render it). Read-only; no API key; rate-limited.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain or link to check (e.g. 'upbit-event.example' or 'https://…') |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| observation | object | – | How much was actually observed and when. A partial observation means some checks did not answer: missing parts are not verified, never clean. |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| reportUrl | string | yes | Human-facing interactive report for this exact lookup on dechonet.com |
| score | number | – | 0-100 score when the tool scores the target |
| status | string | yes | Overall verdict, e.g. 'good' | 'warning' | 'bad' | 'info' | 'unknown' |
| summary | string | – | One-paragraph interpretation of the result |
No examples provided.
dns_lookup DNS Lookup ~183
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| observation | object | – | How much was actually observed and when. A partial observation means some checks did not answer: missing parts are not verified, never clean. |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| reportUrl | string | yes | Human-facing interactive report for this exact lookup on dechonet.com |
| score | number | – | 0-100 score when the tool scores the target |
| status | string | yes | Overall verdict, e.g. 'good' | 'warning' | 'bad' | 'info' | 'unknown' |
| summary | string | – | One-paragraph interpretation of the result |
No examples provided.
dns_propagation DNS Propagation Check ~154
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| observation | object | – | How much was actually observed and when. A partial observation means some checks did not answer: missing parts are not verified, never clean. |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| reportUrl | string | yes | Human-facing interactive report for this exact lookup on dechonet.com |
| score | number | – | 0-100 score when the tool scores the target |
| status | string | yes | Overall verdict, e.g. 'good' | 'warning' | 'bad' | 'info' | 'unknown' |
| summary | string | – | One-paragraph interpretation of the result |
No examples provided.
domain_changes Domain Change History ~245
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. It is the first check to run when a domain looked at before comes up again. Two sources: (a) the daily watch timeline if the domain is under DechoNet monitoring, 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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain whose recorded change history to fetch (e.g., 'example.com'). Scheme and path are stripped. |
| Name | Type | Req | Description |
|---|---|---|---|
| changeCount | number | – | Number of changes recorded |
| changes | array | – | Recorded changes, newest first |
| domain | string | yes | – |
| historyChangeCount | number | – | Changes found between the last two stored lookups per tool (no watch needed) |
| historyChanges | array | – | Lookup-to-lookup changes, newest first |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| reportUrl | string | yes | Where a human can start or manage monitoring |
| watched | boolean | yes | Whether the domain is under an active daily watch |
No examples provided.
domain_history Infrastructure History ~207
Show how a domain's (or IPv4 address's) infrastructure has changed over time from DechoNet's stored observations: nameservers, A/AAAA, MX, CNAME, certificate issuer, registrar, RDAP nameservers and status, and for an IP its ASN and PTR — each value with when it was first and last seen. Use this when the question is about the past ("when did the nameservers change?", "which IPs has it used?"); use dns_lookup or rdap_lookup for the current state. Coverage: only what DechoNet itself observed (lookups, watches, own discovery, and a daily re-resolution of the Korean-brand and phishing names it tracks) — not full passive DNS. Read-only; requires no API key; rate-limited. Returns per-kind value timelines and a coverage note.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Domain (e.g., 'example.com') or IPv4 address. Scheme, path and a leading www. are stripped. |
| Name | Type | Req | Description |
|---|---|---|---|
| kinds | array | yes | – |
| note | string | – | – |
| observed | boolean | yes | – |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| reportUrl | string | yes | – |
| target | string | yes | – |
No examples provided.
email_auth Email Authentication Check ~183
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Email domain to assess — the part after '@' (e.g., 'example.com'). An IP address is also accepted for reverse/PTR-based checks. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| observation | object | – | How much was actually observed and when. A partial observation means some checks did not answer: missing parts are not verified, never clean. |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| reportUrl | string | yes | Human-facing interactive report for this exact lookup on dechonet.com |
| score | number | – | 0-100 score when the tool scores the target |
| status | string | yes | Overall verdict, e.g. 'good' | 'warning' | 'bad' | 'info' | 'unknown' |
| summary | string | – | One-paragraph interpretation of the result |
No examples provided.
email_header_analysis Email Header Analysis ~220
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, the encryption status of each hop, and whether the first sending address is on the Tor Project exit list or in a VPN provider range (information only).
| Name | Type | Req | Description |
|---|---|---|---|
| headers | string | yes | 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| observation | object | – | How much was actually observed and when. A partial observation means some checks did not answer: missing parts are not verified, never clean. |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| reportUrl | string | yes | Human-facing interactive report for this exact lookup on dechonet.com |
| score | number | – | 0-100 score when the tool scores the target |
| status | string | yes | Overall verdict, e.g. 'good' | 'warning' | 'bad' | 'info' | 'unknown' |
| summary | string | – | One-paragraph interpretation of the result |
No examples provided.
exposure_map Exposed Admin Page Check ~229
Map what an organisation exposes to the internet beyond its home page: subdomains from Certificate Transparency logs (plus hosts DechoNet has already observed), each opened once from outside and sorted into developer/ops tools, directory listings, admin screens, VPN/remote-access logins, staging servers, default install pages, login pages and so on — the forgotten assets AI-driven attack tools look for first. Use this when a user wants to know their attack surface or after a breach in their sector. Returns counts per category, a verdict (bad/warn/ok) and what to do. Public view only: the per-host list and a sensitive-file check are shown to the verified domain owner on the web report (DNS TXT), never through this tool. Read-only and passive beyond a single first-page request per host; no logins or path guessing; requires no API key; rate-limited (heavier than other tools — up to ~1 minute).
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The organisation's domain (e.g., 'example.co.kr'). Scheme, path and a leading www. are stripped. |
| Name | Type | Req | Description |
|---|---|---|---|
| counts | object | yes | hosts per category (devtool, api_docs, listing, admin, remote, staging, default_page, login, api, mail, web, …) |
| found | number | yes | – |
| issues | array | yes | – |
| probed | number | yes | – |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| reportUrl | string | yes | – |
| status | string | yes | bad | warn | ok | info |
No examples provided.
golive_check Go-Live Readiness Checklist ~198
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to check for launch/migration readiness (e.g., 'example.com'). Scheme and path are stripped. |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | – | – |
| failCount | number | – | – |
| passCount | number | – | – |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| reportUrl | string | yes | Human-facing interactive report on dechonet.com |
| verdict | string | yes | 'ready' | 'caution' | 'not_ready' |
| warnCount | number | – | – |
No examples provided.
http_security HTTP Security Headers Audit ~220
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 on the six core headers (CSP, HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy; COOP/CORP/COEP are reported but not graded) 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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| observation | object | – | How much was actually observed and when. A partial observation means some checks did not answer: missing parts are not verified, never clean. |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| reportUrl | string | yes | Human-facing interactive report for this exact lookup on dechonet.com |
| score | number | – | 0-100 score when the tool scores the target |
| status | string | yes | Overall verdict, e.g. 'good' | 'warning' | 'bad' | 'info' | 'unknown' |
| summary | string | – | One-paragraph interpretation of the result |
No examples provided.
impersonation_exposure Brand Impersonation Exposure ~246
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. Framing: a registered lookalike domain is not proof of impersonation — it may be a legitimate third party or the owner's own — so report it as exposure to verify, not as an accusation against that 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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Registrable domain to assess for impersonation exposure (e.g., 'example.com'). Scheme and path are stripped. |
| Name | Type | Req | Description |
|---|---|---|---|
| grade | string | yes | Exposure grade A+ (low exposure) to F (high exposure) |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| reportUrl | string | yes | Human-facing interactive report on dechonet.com |
| riskySubdomainCount | number | yes | Exposed operational subdomains found |
| score | number | yes | 0-100, higher = less exposed |
| typosquatCount | number | yes | Live third-party lookalike/typosquat domains (variants on the domain's own nameservers/IP are excluded) |
| wildcard | boolean | – | Whether a wildcard certificate exists |
No examples provided.
infrastructure_pivot Infrastructure Pivot ~216
Find other domains DechoNet has seen with the same infrastructure value — a nameserver, IP address, MX host, certificate issuer or registrar — with first and last seen, to map related infrastructure (e.g. other phishing domains on the same rare nameserver). Use it after domain_history or dns_lookup gives you a distinctive value. Shared infrastructure (CDN edges, public CAs, large registrars and DNS hosts) returns a count only, since sharing it says nothing about ownership. Read-only; REQUIRES a free DechoNet API key (account page; remote: send Authorization: Bearer dn_…, npm: set DECHONET_API_KEY); up to 20 rows per call (higher for some keys); rate-limited. Coverage: only DechoNet's own observations.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | Which kind of value to pivot on. |
| value | string | yes | The value itself, e.g. 'ns1.example-dns.net' or '203.0.113.9'. |
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | – |
| note | string | – | – |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| reportUrl | string | yes | – |
| sharedInfra | boolean | – | – |
| targets | array | yes | – |
| total | number | yes | – |
| value | string | yes | – |
No examples provided.
ip_info My IP Info ~113
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| observation | object | – | How much was actually observed and when. A partial observation means some checks did not answer: missing parts are not verified, never clean. |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| reportUrl | string | yes | Human-facing interactive report for this exact lookup on dechonet.com |
| score | number | – | 0-100 score when the tool scores the target |
| status | string | yes | Overall verdict, e.g. 'good' | 'warning' | 'bad' | 'info' | 'unknown' |
| summary | string | – | One-paragraph interpretation of the result |
No examples provided.
lookalike_domains Lookalike Domain Check ~200
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to protect (e.g., 'example.com'), without scheme or path. Variants of its label and TLD are generated and checked. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| observation | object | – | How much was actually observed and when. A partial observation means some checks did not answer: missing parts are not verified, never clean. |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| reportUrl | string | yes | Human-facing interactive report for this exact lookup on dechonet.com |
| score | number | – | 0-100 score when the tool scores the target |
| status | string | yes | Overall verdict, e.g. 'good' | 'warning' | 'bad' | 'info' | 'unknown' |
| summary | string | – | One-paragraph interpretation of the result |
No examples provided.
mcp_server_check MCP Server Check ~232
Check a remote MCP server from outside before connecting it to an agent: whether it requires authentication (and publishes OAuth protected-resource metadata, RFC 9728), which of its tools act on the world (run commands, write or delete files, send messages, make payments, read secrets), whether its server instructions or tool and parameter descriptions contain text that steers an agent (tool poisoning), whether a web page on any site could call it (CORS and Origin), HTTPS, and tool annotations. Sends initialize and tools/list only — no tool is ever called; query strings are removed before anything is sent or stored. Public addresses only. Findings cover what the server shows from outside: what a tool does when called, the server code and tools behind a login are not checked and are listed as not checked. Read-only; requires no API key; rate-limited. Returns status, KPIs, issues, actions, what was not checked, and a shareable report link.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The remote MCP endpoint (e.g., 'https://example.com/mcp'). Query strings are removed. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| observation | object | – | How much was actually observed and when. A partial observation means some checks did not answer: missing parts are not verified, never clean. |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| reportUrl | string | yes | Human-facing interactive report for this exact lookup on dechonet.com |
| score | number | – | 0-100 score when the tool scores the target |
| status | string | yes | Overall verdict, e.g. 'good' | 'warning' | 'bad' | 'info' | 'unknown' |
| summary | string | – | One-paragraph interpretation of the result |
No examples provided.
owasp_check OWASP Security Checkup ~334
Assess a domain's OWASP posture from EXTERNAL OBSERVATION only: the OWASP Secure Headers Project plus the externally observable OWASP Top 10:2025 subset — A04 Cryptographic Failures (TLS/cert), A02 Security Misconfiguration (header/info leaks), and A03 Software Supply Chain Failures (outdated components via version disclosure) — returning an A+ to F grade. Scope: A01 (Access Control, incl. SSRF), A05 (Injection), A06 (Insecure Design), A07 (Authentication), A08, A09 and A10 (Exceptional Conditions) are not checked — they need authenticated access or active/injection testing, so the result lists them as out-of-scope rather than "pass". The result is an external-posture check, not a full OWASP Top 10 assessment. This is PASSIVE (a normal HTTPS request, the TLS certificate and a public CT-log lookup; no port scan, no path probing), so it is suitable for domains you do not own. The sensitive-file check (.env, .git, server-status) runs only for the verified domain owner on the web report (DNS TXT), never through this tool. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Hostname to assess, without scheme (e.g., 'example.com'). The host portion of a pasted URL is also accepted. |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | yes | Per observable category: Secure Headers, A02, A05, A06 |
| grade | string | yes | OWASP posture grade A+ to F, over the observable categories only |
| notObservable | array | – | Top 10 categories NOT checked (need authenticated/active testing) |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| reportUrl | string | yes | Human-facing interactive report on dechonet.com |
| score | number | yes | 0-100 across the categories that could be evaluated |
No examples provided.
phishing_link_check Phishing / Smishing Link Check ~337
Check the links in a suspicious text message (smishing) or e-mail before anyone taps them. Paste the whole message or a single URL: every link is extracted, followed through URL shorteners to its real destination, and judged on observable signals — domain age from RDAP, impersonation of Korean banks/couriers/telecoms/portals and global brands incl. AI services such as ChatGPT/Claude/Gemini (brand keyword, lookalike spelling, or the brand domain worn as a subdomain), ClickFix pages (a fake "verify you are human" check that has the visitor paste a command into Win+R/PowerShell), Android APK downloads, punycode, public phishing/malware feeds, and DechoNet's own impersonation tracking. Use this when a user asks whether a link or message is a scam. Verdicts: danger, suspicious, unreachable, official (lands on the brand's own domain), no_signals (no warning signs found; this is not a finding that the link is safe). Reads landing-page HTML; inconclusive links may also run page scripts in isolated Chromium under the shared daily cap. DechoNet does not click, enter values or submit forms. The message text is not stored; requires no API key; rate-limited. Returns per-link verdicts with reasons and a shareable report link.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The link(s) to check — a URL, or the message text with verification codes, passwords and personal details removed (any language). Only the links are used (up to 5); the text is not stored. |
| Name | Type | Req | Description |
|---|---|---|---|
| links | array | yes | – |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| reportUrl | string | yes | – |
| verdict | string | yes | danger | suspicious | unreachable | official | no_signals | no_links |
No examples provided.
port_scan Open Port Scan ~224
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.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| observation | object | – | How much was actually observed and when. A partial observation means some checks did not answer: missing parts are not verified, never clean. |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| reportUrl | string | yes | Human-facing interactive report for this exact lookup on dechonet.com |
| score | number | – | 0-100 score when the tool scores the target |
| status | string | yes | Overall verdict, e.g. 'good' | 'warning' | 'bad' | 'info' | 'unknown' |
| summary | string | – | One-paragraph interpretation of the result |
No examples provided.
pqc_readiness Post-Quantum TLS Readiness ~270
Check whether a website's public TLS endpoint is ready for post-quantum cryptography: does it complete a TLS 1.3 handshake that offers only the hybrid X25519MLKEM768 key exchange (ML-KEM), and does the organisation's own server provide it or a CDN edge in front of it. Also reports what the certificate chain is signed with (tracked, not scored: public CAs do not issue post-quantum certificates yet). Verdicts: ready (the origin server supports it), partial (a CDN edge provides it; the CDN-to-origin leg is invisible), not_ready (the hybrid-only handshake was refused), unknown (inconclusive — not the same as "no"). Scope: only the public endpoint on port 443. Internal systems, VPNs, code, and Korean PQC algorithms (no standard TLS codepoints yet) are not observable, so the result is an external indicator of migration progress, not a full PQC audit. Read-only; requires no API key; rate-limited. Returns the verdict, a 0-100 readiness score and grade, per-check statuses, and a shareable report link.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain whose HTTPS endpoint to check (e.g., 'example.com'). Scheme and path are stripped. |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | – | – |
| grade | string|null | – | – |
| keyExchange | string|null | – | Hybrid group accepted (e.g. X25519MLKEM768), null if none |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| reportUrl | string | yes | Human-facing interactive report on dechonet.com |
| score | number|null | – | 0-100 post-quantum readiness; null when inconclusive |
| terminatedBy | string|null | – | 'origin' or the CDN name whose edge answered |
| tlsVersion | string|null | – | – |
| verdict | string | yes | 'ready' | 'partial' | 'not_ready' | 'unknown' |
No examples provided.
report_page Report a Page ~328
Report a page to DechoNet: phishing or brand impersonation, a fake payment window (card fields where a payment provider should be), hidden instructions aimed at AI agents, a malicious download, a DechoNet verdict that looks wrong (false_positive) or a danger it missed (missed), an MCP server whose tool descriptions steer agents (malicious_mcp — url is the MCP endpoint), or a network anomaly (network_anomaly — the certificate serial/issuer or addresses you saw for the host, in observed). Kept for 90 days: the host and the kind, with an anonymous reporter hash used to count independent reports; for malicious_mcp the endpoint path, for network_anomaly the observed values and the country of the connection. No query, page text or free text. This call only records the report and returns at once; it opens nothing. A report changes no verdict by itself: later, DechoNet's own hourly check visits the reported host (an outside site) with the same rules as phishing_link_check (mcp_server_check for malicious_mcp, dns_lookup and ssl_check for network_anomaly), and only what that check observes counts; hosts reported by several independent sources are checked first. Not read-only (it records the report); rate-limited.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | What is wrong with the page |
| observed | object | – | network_anomaly only: the certificate serial (hex) and issuer, and the addresses, you saw for the host |
| url | string | yes | Address of the page (only its host is kept) |
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | – |
| kind | string | yes | – |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| received | boolean | yes | – |
No examples provided.
reverse_dns Reverse DNS (PTR) Lookup ~172
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| observation | object | – | How much was actually observed and when. A partial observation means some checks did not answer: missing parts are not verified, never clean. |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| reportUrl | string | yes | Human-facing interactive report for this exact lookup on dechonet.com |
| score | number | – | 0-100 score when the tool scores the target |
| status | string | yes | Overall verdict, e.g. 'good' | 'warning' | 'bad' | 'info' | 'unknown' |
| summary | string | – | One-paragraph interpretation of the result |
No examples provided.
security_scan Full Domain Security Scan ~313
One-shot comprehensive audit of a domain, scored 0-100 with an A+ to F grade and a prioritized action list. Five scored areas: the web connection (TLS certificate and HTTP security headers, measured on www when only www has an address), mail spoofing defence (SPF/DKIM/DMARC; a domain that uses no mail is judged only on SPF -all and an enforced DMARC policy), domain registration and DNS, exposure (admin screens, developer tools and the like on hosts named in public certificate logs — counts only), and reputation (DechoNet verdict store and licensed phishing feeds). DNS propagation, reverse DNS and ASN are returned as reference information and not scored. A warning costs a quarter of its area and a critical half; data that could not be read in full is flagged, not charged, and an exposure or reputation lookup that fails is reported as not checked. Call the individual tools (e.g., ssl_check, email_auth, exposure_map) for depth on one area. BEHAVIOR: passive — public lookups and ordinary HTTPS requests only; open ports are NOT scanned (port_scan is the separate, active check). Takes up to about a minute (the exposure lookup). Read-only; requires no API key; rate-limited (it makes multiple backend calls). Returns the score, per-area breakdown, reference areas, top actions, and per-area summaries.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to audit (e.g., 'example.com'). Scheme and path are stripped. |
| Name | Type | Req | Description |
|---|---|---|---|
| actions | array | – | Top recommended actions |
| areas | array | yes | Per-area verdicts of the scored areas (ssl, http, email, rdap, dns, exposure, reputation) |
| grade | string | yes | Letter grade A+ to F |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| reference | array | – | Reference areas, not scored (propagation, reverseDns, asn): the tool status |
| reportUrl | string | yes | Human-facing interactive report on dechonet.com |
| score | number | yes | Health Score 0-100 |
No examples provided.
set_expectations Set Outside Expectations (daily re-check) ~348
Record what a domain should show from outside and check it now — HSTS or another header present, DMARC enforcing, an issue key no longer reported, an HTTP or TLS grade at or above a level, a certificate with enough days left, a DNS record present, absent or containing a value, HTTPS answering. DechoNet reads the domain fresh (not from cache) with its public dns / ssl / http / email tools, from its own servers and the Seoul observation point, and then re-checks the set every day. Each result is pass, fail or unknown; unknown (a tool or part of it did not answer) is never a pass. Without an API key the set is anonymous: no alerts, kept 30 days after its last check, reachable by id and status page. With an API key (Authorization: Bearer dn_…) the set belongs to that key's account, and a set that held and stops holding is reported in the account's daily mail. Not read-only (it stores the set); public checks only, so any domain is accepted. Typical use: after changing DNS, TLS, headers or mail settings, to state the intended result and be told if it is ever reverted. Returns the set id, status page, per-check results with where to fix what does not hold (for the platform the site runs on), and signed observation receipts.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain the checks are about (e.g. 'example.com'); scheme and path are stripped |
| expect | array | yes | Checks, 1-20 |
| label | string | – | Optional short name for the set (shown on its page and in the mail) |
| Name | Type | Req | Description |
|---|---|---|---|
| checkedAt | string|null | – | – |
| domain | string | yes | – |
| expiresAt | string|null | – | Anonymous sets: removed after this unless checked again |
| id | string | – | Expectation set id (stored sets) |
| owner | string | – | 'account' (alerts by the API key account's daily mail) or 'anonymous' (no alerts) |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| results | array | yes | – |
| state | string|null | yes | 'pass' (every check holds) | 'fail' (at least one does not) | 'unknown' (some could not be read — not a pass) |
| stored | boolean | yes | Whether DechoNet keeps re-checking this set daily |
| url | string | – | Status page of the set: last results and recent checks |
No examples provided.
ssl_check SSL Certificate Check ~334
Inspect a host's served TLS/SSL certificate and connection: expiry date, issuer, SAN list, chain integrity, revocation (OCSP, then CRL; unknown when neither answers — not graded unless revoked), TLS version, and HSTS, returning an A+ to F grade weighted by certificate validity (40%), TLS version (25%), chain trust (15%), and HSTS (20%). From Seoul it also lists the protocol versions and cipher suites the server accepts — including SSL 3.0, RC4, 3DES, export, NULL and anonymous suites and the Korean SEED/ARIA ciphers — with TLS compression, secure renegotiation, TLS_FALLBACK_SCSV, DH group size and TLS 1.3 key exchange groups; weak findings cap the grade as SSL Labs does (F, C or B). 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: one full TLS handshake plus opening ClientHello messages whose first answer is read; no application data and no vulnerability probes; requires no API key; rate-limited. Returns a text report: grade, expiry/issuer KPIs, issues, and actions.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| observation | object | – | How much was actually observed and when. A partial observation means some checks did not answer: missing parts are not verified, never clean. |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| reportUrl | string | yes | Human-facing interactive report for this exact lookup on dechonet.com |
| score | number | – | 0-100 score when the tool scores the target |
| status | string | yes | Overall verdict, e.g. 'good' | 'warning' | 'bad' | 'info' | 'unknown' |
| summary | string | – | One-paragraph interpretation of the result |
No examples provided.
subdomain_discovery Subdomain Discovery ~184
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Registrable domain to enumerate (e.g., 'example.com'), without scheme or path. Subdomains found in CT logs for this domain are returned. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| observation | object | – | How much was actually observed and when. A partial observation means some checks did not answer: missing parts are not verified, never clean. |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| reportUrl | string | yes | Human-facing interactive report for this exact lookup on dechonet.com |
| score | number | – | 0-100 score when the tool scores the target |
| status | string | yes | Overall verdict, e.g. 'good' | 'warning' | 'bad' | 'info' | 'unknown' |
| summary | string | – | One-paragraph interpretation of the result |
No examples provided.
subnet_calc IPv4 Subnet Calculator ~159
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cidr | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| broadcast | string | yes | Broadcast address |
| firstHost | string | yes | First usable host |
| lastHost | string | yes | Last usable host |
| network | string | yes | Network address |
| prefix | number | yes | CIDR prefix length |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| reportUrl | string | yes | Human-facing interactive report on dechonet.com |
| subnetMask | string | yes | Dotted-decimal subnet mask |
| totalHosts | number | yes | Usable host count |
| wildcardMask | string | yes | Wildcard (inverse) mask |
No examples provided.
verify_expectations Verify Outside Expectations Now ~187
Check expectations from outside now, with fresh reads: either a stored set by id (from set_expectations — its state is updated and an anonymous set is kept another 30 days), or a domain plus a list of checks once, storing nothing. Same checks and outcomes as set_expectations (pass / fail / unknown, unknown is never a pass), each tool read once with a signed observation receipt. Typical use: right after a change, to see whether it is visible from outside yet — DNS and CDN changes can take minutes to hours to show. Rate-limited (a few checks per minute).
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Domain to check once (with expect), when there is no stored set |
| expect | array | – | Checks for a one-off verify, 1-20 |
| id | string | – | Stored set id ('ex_…') to re-check |
| Name | Type | Req | Description |
|---|---|---|---|
| checkedAt | string|null | – | – |
| domain | string | yes | – |
| expiresAt | string|null | – | Anonymous sets: removed after this unless checked again |
| id | string | – | Expectation set id (stored sets) |
| owner | string | – | 'account' (alerts by the API key account's daily mail) or 'anonymous' (no alerts) |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| results | array | yes | – |
| state | string|null | yes | 'pass' (every check holds) | 'fail' (at least one does not) | 'unknown' (some could not be read — not a pass) |
| stored | boolean | yes | Whether DechoNet keeps re-checking this set daily |
| url | string | – | Status page of the set: last results and recent checks |
No examples provided.
wallet_address_check Wallet Address Check ~257
Check one crypto wallet address: which chain it belongs to (EVM, TRON, Bitcoin, Solana — from the format alone), whether its checksum is valid (EIP-55, Base58Check, bech32/bech32m), whether it is on the US Treasury OFAC SDN sanctions list (read daily) or among the addresses the FBI published in an alert (the Binance theft of October 2026, 628 addresses), whether Tether has frozen USDT at it (Ethereum and TRON addresses, read from the USDT contract), and how many pages DechoNet's phishing check judged dangerous showed it. Listed means on that day's list, not a finding about the owner; not listed is not a statement that the address is clean (most scam addresses are on no list). Balances, transaction history and the owner are not looked at — see 'Not checked'. The address is not stored. Use crypto_check_before_sign to judge an address together with the page that asked and the wallet request. Read-only; no API key; rate-limited.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address (0x…, T…, bc1…/1…/3…, or a Solana address) |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| observation | object | – | How much was actually observed and when. A partial observation means some checks did not answer: missing parts are not verified, never clean. |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| reportUrl | string | yes | Human-facing interactive report for this exact lookup on dechonet.com |
| score | number | – | 0-100 score when the tool scores the target |
| status | string | yes | Overall verdict, e.g. 'good' | 'warning' | 'bad' | 'info' | 'unknown' |
| summary | string | – | One-paragraph interpretation of the result |
No examples provided.
watch_domain Watch a Domain (daily re-check) ~292
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).
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | 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, 'pqc'… |
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| failed | array | – | Tools that could not be watched (rate limit or error) |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| reportUrl | string | yes | – |
| watches | array | yes | One entry per tool now under a daily watch |
No examples provided.
whois_lookup WHOIS / RDAP Domain Lookup ~141
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Registered domain name to look up (e.g., 'example.com'). A subdomain is normalized to its registrable domain. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| observation | object | – | How much was actually observed and when. A partial observation means some checks did not answer: missing parts are not verified, never clean. |
| receipts | array | – | Signed observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature. |
| reportUrl | string | yes | Human-facing interactive report for this exact lookup on dechonet.com |
| score | number | – | 0-100 score when the tool scores the target |
| status | string | yes | Overall verdict, e.g. 'good' | 'warning' | 'bad' | 'info' | 'unknown' |
| summary | string | – | One-paragraph interpretation of the result |
No examples provided.
How do I install the com.dechonet/mcp server?
com.dechonet/mcp runs locally as an npm package, launched with npx -y dechonet-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · dechonet-mcp
claude mcp add com-dechonet-mcp -- npx -y dechonet-mcp
What is the com.dechonet/mcp server?
com.dechonet/mcp is listed in the public MCP registry as com.dechonet/mcp. 34 security tools for AI agents: phishing links, exposure maps, DNS, SSL, PQC, history, pivots. This page covers its npm package (dechonet-mcp).
Is the com.dechonet/mcp server safe to use?
com.dechonet/mcp scores 88 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 34 tools: dns_lookup, ssl_check, http_security, email_auth, port_scan, and 29 more. Their descriptions and schemas cost roughly 8,176 tokens of context every time the server is loaded.
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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the com.dechonet/mcp server under?
com.dechonet/mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the com.dechonet/mcp server?
VerifyMCP ran 16 checks on com.dechonet/mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.