Skip to content

idig-dns MCP server

net.softricks/idig-dnssoftricks.netssev1.0.0Scanned

Professional DNS diagnostics: 14 tools for DNS, DNSSEC, email security, SSL, and propagation.

19 tools: 12 change things and 7 only read.

Tools: 0 delete, 0 irreversible, 12 write, 7 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

Anlyon alternative

12 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the idig-dns MCP server can do

The idig-dns MCP server is published by softricks.net, a domain the MCP Registry verified. It has 19 tools. It can create or change data (12 tools: email_security_audit, dnssec_health, diagnose, propagation_check and 8 more), but cannot delete data. 7 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 18, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

19 tools

Changes things 12Claude Code: ask
  • blacklist_checkIP blacklist / DNSBL check.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    IP blacklist / DNSBL check. Tests A-record and MX IPs against Spamhaus, Barracuda, SpamCop, SORBS, and more.
  • diagnoseFull diagnosis combining resolution + DNSSEC.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Full diagnosis combining resolution + DNSSEC. Use first when something is broken.
  • dnssec_healthDNSSEC 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 …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • email_security_auditFull SPF, DKIM, DMARC, and BIMI audit with A-F grade and prioritized fix recommendations.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Full SPF, DKIM, DMARC, and BIMI audit with A-F grade and prioritized fix recommendations.
  • http_checkHTTP/HTTPS reachability: status codes, redirect chain, HSTS header, HTTP→HTTPS redirect detection.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    HTTP/HTTPS reachability: status codes, redirect chain, HSTS header, HTTP→HTTPS redirect detection.
  • mx_checkMX health + provider detection: Google Workspace, M365, Proofpoint, Zoho, 35+ providers.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    MX health + provider detection: Google Workspace, M365, Proofpoint, Zoho, 35+ providers.
  • propagation_checkCheck DNS propagation across 16 global resolvers: Google, Cloudflare, Quad9, China, Korea, Russia.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Check DNS propagation across 16 global resolvers: Google, Cloudflare, Quad9, China, Korea, Russia.
  • ssl_checkSSL certificate: validity, expiry countdown, domain match, issuer, chain completeness.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    SSL certificate: validity, expiry countdown, domain match, issuer, chain completeness.
  • subdomain_discoverDiscover subdomains by probing 75 common names plus crt.sh Certificate Transparency logs.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Discover subdomains by probing 75 common names plus crt.sh Certificate Transparency logs. Surfaces exposed dev/staging environments.
  • ttl_checkTTL advisory: flags dangerous TTLs and gives step-by-step migration lowering plan.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    TTL advisory: flags dangerous TTLs and gives step-by-step migration lowering plan.
  • zone_axfrAXFR zone transfer vulnerability check.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    AXFR zone transfer vulnerability check. Tests whether any authoritative NS allows public zone transfers (critical misconfiguration).
  • zone_consistencyCheck all authoritative nameservers return identical answers.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Check all authoritative nameservers return identical answers. Catches lame delegation and SOA mismatches.
Only reads 7Show 7 read-only tools
  • dane_validateDANE/TLSA validation: cross-validates TLSA DNS records against the live TLS certificate.No findings

    Why it is in this group

    • The name "dane_validate" says "validate": a word for reading.
    Description, as the server wrote it
    DANE/TLSA validation: cross-validates TLSA DNS records against the live TLS certificate. Supports all four TLSA usage types.
  • dns_lookupLook up DNS records for a domain.No findings

    Why it is in this group

    • The name "dns_lookup" says "lookup": a word for reading.
    Description, as the server wrote it
    Look up DNS records for a domain. Record types: a, aaaa, ns, mx, txt, soa, caa, srv, cname, ds, tlsa, https, svcb, any, all.
  • dnssec_validateValidate DNSSEC chain of trust.No findings

    Why it is in this group

    • The name "dnssec_validate" says "validate": a word for reading.
    Description, as the server wrote it
    Validate DNSSEC chain of trust. Returns: secure / insecure / bogus / indeterminate.
  • domain_statusRegistrar lock and EPP status.No findings

    Why it is in this group

    • The name "domain_status" says "status": a word for reading.
    Description, as the server wrote it
    Registrar lock and EPP status. Checks transfer lock, delete lock, serverHold, pendingDelete.
  • geo_lookupGeolocation and hosting: country, city, ISP, ASN, CDN detection, is_hosting flag.No findings

    Why it is in this group

    • The name "geo_lookup" says "lookup": a word for reading.
    Description, as the server wrote it
    Geolocation and hosting: country, city, ISP, ASN, CDN detection, is_hosting flag.
  • resolve_checkDNS resolution diagnostics.No findings

    Why it is in this group

    • The name "resolve_check" says "resolve": a word for reading.
    Description, as the server wrote it
    DNS resolution diagnostics. Returns status: ok / nxdomain / nodata / servfail / refused / timeout / degraded.
  • whois_lookupParsed WHOIS: registrar, creation/expiry dates, domain age, nameservers, EPP status, DNSSEC status.No findings

    Why it is in this group

    • The name "whois_lookup" says "lookup": a word for reading.
    Description, as the server wrote it
    Parsed WHOIS: registrar, creation/expiry dates, domain age, nameservers, EPP status, DNSSEC status.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:16 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
202
tools/list served without credentials
yes
Tools that change things, listed without credentials
12
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
yes
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 12 tools that change things (12 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.softricks.net/sse: tools/list returned 19 tools to an anonymous client, including email_security_audit (write), dnssec_health (write), diagnose (write), propagation_check (write), mx_check (write) and 7 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport sse idig-dns https://mcp.softricks.net/sse
claude mcp add --transport sse idig-dns https://mcp.softricks.net/sse

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__idig-dns__dns_lookup",
      "mcp__idig-dns__dnssec_validate",
      "mcp__idig-dns__resolve_check",
      "mcp__idig-dns__domain_status",
      "mcp__idig-dns__geo_lookup",
      "mcp__idig-dns__whois_lookup",
      "mcp__idig-dns__dane_validate"
    ],
    "ask": [
      "mcp__idig-dns__email_security_audit",
      "mcp__idig-dns__dnssec_health",
      "mcp__idig-dns__diagnose",
      "mcp__idig-dns__propagation_check",
      "mcp__idig-dns__mx_check",
      "mcp__idig-dns__ttl_check",
      "mcp__idig-dns__zone_consistency",
      "mcp__idig-dns__ssl_check",
      "mcp__idig-dns__subdomain_discover",
      "mcp__idig-dns__blacklist_check",
      "mcp__idig-dns__http_check",
      "mcp__idig-dns__zone_axfr"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as idig-dns. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/net.softricks/idig-dns/verify?hash=d75b96f1731324f29a59ebca1e8042a71f69cb36c3ec08d54259810abafce389" | jq -e '.changed == false'

Pinned hash d75b96f17313, from Nov 18, 2026, 00:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/net.softricks/idig-dns/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for net.softricks/idig-dns
[![Anlyon Radar](https://radar.anlyon.com/badge/net.softricks/idig-dns.svg)](https://radar.anlyon.com/servers/net.softricks/idig-dns)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:53 UTC.

idig-dns MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the idig-dns MCP server safe?

No scan can promise that. What its definitions show: 19 tools, 12 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the idig-dns MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the idig-dns MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the idig-dns MCP server have?

19 tools: 12 write, 7 read. email_security_audit, dnssec_health, diagnose, propagation_check, mx_check, ttl_check, zone_consistency, ssl_check and 11 more.

Does the idig-dns MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the idig-dns MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the idig-dns MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.