net.softricks/idig-dns
REMOTE · MCP.SOFTRICKS.NET
Professional DNS diagnostics: 14 tools for DNS, DNSSEC, email security, SSL, and propagation.
Available components
Last scanned (13 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Security
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 19 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 912 tokens (~48/item across 19 items; 19 tools + 0 resources), lean.Pass
- 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 Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 19 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 (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 19 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
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.
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 7 Nov 26 0
- Endpoint reachability: unreachable → reachable ▲ functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 · Probed https://mcp.softricks.net/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.softricks.net | CN=YR1,O=Let's Encrypt,C=US | 26 Oct 2026 | 24 Jan 2027 | RSA 2048 | SHA256-RSA | 520592d9c070dd1080d793231996e6189e6 |
| SANs: mcp.softricks.net | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.softricks.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| net. | DS published | 37331 | 13 | Verified |
| softricks.net. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://mcp.softricks.net/sse | Verified | 200 | |
| http (plaintext) | http://mcp.softricks.net/sse | HTTPS enforced | 301 | https://mcp.softricks.net/sse |
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 →
blacklist_check ~54
IP blacklist / DNSBL check. Tests A-record and MX IPs against Spamhaus, Barracuda, SpamCop, SORBS, and more.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
dane_validate ~57
DANE/TLSA validation: cross-validates TLSA DNS records against the live TLS certificate. Supports all four TLSA usage types.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| port | integer | – | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
diagnose ~36
Full diagnosis combining resolution + DNSSEC. Use first when something is broken.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
dns_lookup ~74
Look up DNS records for a domain. Record types: a, aaaa, ns, mx, txt, soa, caa, srv, cname, ds, tlsa, https, svcb, any, all.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| rr | string | – | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
dnssec_health ~71
DNSSEC health report: key inventory, signature expiry, algorithm assessment, DS at parent, rollover readiness, full chain of trust (Root → TLD → Domain) with chain_intact flag and broken-link identification, warnings, and recommendations.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
dnssec_validate ~41
Validate DNSSEC chain of trust. Returns: secure / insecure / bogus / indeterminate.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
domain_status ~42
Registrar lock and EPP status. Checks transfer lock, delete lock, serverHold, pendingDelete.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
email_security_audit ~46
Full SPF, DKIM, DMARC, and BIMI audit with A-F grade and prioritized fix recommendations.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
geo_lookup ~43
Geolocation and hosting: country, city, ISP, ASN, CDN detection, is_hosting flag.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
http_check ~44
HTTP/HTTPS reachability: status codes, redirect chain, HSTS header, HTTP→HTTPS redirect detection.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
mx_check ~45
MX health + provider detection: Google Workspace, M365, Proofpoint, Zoho, 35+ providers.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
propagation_check ~54
Check DNS propagation across 16 global resolvers: Google, Cloudflare, Quad9, China, Korea, Russia.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| record_type | string | – | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
resolve_check ~47
DNS resolution diagnostics. Returns status: ok / nxdomain / nodata / servfail / refused / timeout / degraded.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
ssl_check ~38
SSL certificate: validity, expiry countdown, domain match, issuer, chain completeness.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
subdomain_discover ~48
Discover subdomains by probing 75 common names plus crt.sh Certificate Transparency logs. Surfaces exposed dev/staging environments.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
ttl_check ~38
TTL advisory: flags dangerous TTLs and gives step-by-step migration lowering plan.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
whois_lookup ~48
Parsed WHOIS: registrar, creation/expiry dates, domain age, nameservers, EPP status, DNSSEC status.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
zone_axfr ~44
AXFR zone transfer vulnerability check. Tests whether any authoritative NS allows public zone transfers (critical misconfiguration).
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
zone_consistency ~42
Check all authoritative nameservers return identical answers. Catches lame delegation and SOA mismatches.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
How do I install the net.softricks/idig-dns MCP server?
net.softricks/idig-dns is a hosted endpoint at https://mcp.softricks.net/sse, 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.
remote · mcp.softricks.net
claude mcp add --transport http net-softricks-idig-dns 'https://mcp.softricks.net/sse'
What is the net.softricks/idig-dns MCP server?
net.softricks/idig-dns is an MCP server listed in the public MCP registry as net.softricks/idig-dns. Professional DNS diagnostics: 14 tools for DNS, DNSSEC, email security, SSL, and propagation. This page covers its hosted endpoint (https://mcp.softricks.net/sse).
Is the net.softricks/idig-dns MCP server safe to use?
net.softricks/idig-dns scores 69 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 net.softricks/idig-dns MCP server expose?
net.softricks/idig-dns exposes 19 tools: dns_lookup, email_security_audit, dnssec_validate, dnssec_health, resolve_check, and 14 more. Their descriptions and schemas cost roughly 912 tokens of context every time the server is loaded.
Does the net.softricks/idig-dns MCP server require authentication?
No. We connected to net.softricks/idig-dns without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the net.softricks/idig-dns MCP server still maintained?
net.softricks/idig-dns 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 did VerifyMCP test on the net.softricks/idig-dns MCP server?
VerifyMCP ran 12 checks on net.softricks/idig-dns, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about net.softricks/idig-dns: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.