mcpField
I
Idig Dns Api

Idig Dns Api

Remote
github.com/kbhaveDeveloper Tools0Updated 31w ago
Repository

About Idig Dns Api

Idig Dns Api is a remote MCP server that makes iDig DNS diagnostics available to MCP-compatible AI clients. Its checks cover resolution, DNSSEC, email security, certificates, and domain status; tool calls require a token.

Key features

  1. 01Look up multiple DNS record types
  2. 02Diagnose resolution and DNSSEC status
  3. 03Audit SPF, DKIM, DMARC, and BIMI
  4. 04Check propagation and SSL certificates
  5. 05Check subdomains, blacklists, and WHOIS
  6. 06Test HTTP reachability and zone transfers

Use cases

  1. 01Troubleshoot domain resolution failures
  2. 02Audit domain email security settings
  3. 03Check whether DNS changes have propagated
  4. 04Review certificate expiry and blacklist status

MCP support

This remote MCP server connects over SSE and exposes iDig DNS and domain diagnostic tools to MCP clients. All tool calls require a token.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://mcp.softricks.net/sse
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

19
ParameterTypeRequiredDescription
domainstringYes
tokenstringYes
rrstringNo

Details

From the project README

iDig DNS MCP Server

A remote MCP server exposing 19 professional DNS diagnostic tools from the iDig API — built by Kedar Bhave ( Softricks ).

Connect any MCP-compatible AI client (Claude Desktop, Cursor, Windsurf, and more) to real DNS infrastructure. Diagnose outages, audit email security, validate DNSSEC, check SSL certificates, trace propagation across 16 global resolvers, and more — all in plain English.

Live endpoint: https://mcp.softricks.net/sse


Quickstart

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "idig-dns": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.softricks.net/sse"
      ]
    }
  }
}

Restart Claude Desktop. You'll see idig-dns appear under Connectors.

Cursor / Windsurf

Add to your MCP settings:

{
  "mcpServers": {
    "idig-dns": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.softricks.net/sse"
      ]
    }
  }
}
Authentication

All tools require a token parameter. Get your token at api.softricks.net/idig/docs.


Tools

ToolDescription
dns_lookupLook up any DNS record type: A, AAAA, MX, NS, TXT, SOA, CAA, SRV, CNAME, DS, TLSA, HTTPS, SVCB
resolve_checkResolution diagnostics — returns ok / nxdomain / servfail / timeout / degraded
diagnoseFull diagnosis combining resolution + DNSSEC — start here when something is broken
email_security_auditSPF, DKIM, DMARC, and BIMI audit with A–F grade and prioritized fix recommendations
mx_checkMX health + provider detection (Google Workspace, M365, Proofpoint, 35+ providers)
dnssec_validateDNSSEC chain of trust — returns secure / insecure / bogus / indeterminate
dnssec_healthKey inventory, signature expiry, algorithm assessment, rollover readiness
propagation_checkCheck propagation across 16 global resolvers: Google, Cloudflare, Quad9, China, Korea, Russia
ssl_checkCertificate validity, expiry countdown, domain match, issuer, chain completeness
ttl_checkTTL advisory with step-by-step migration lowering plan
zone_consistencyCompare all authoritative nameservers — catches lame delegation and SOA mismatches
subdomain_discoverProbe 75 common subdomains + crt.sh Certificate Transparency logs — surfaces exposed dev/staging environments
geo_lookupGeolocation, ISP, ASN, CDN detection, hosting flag
domain_statusEPP registrar lock status — transfer-ready, delete lock, serverHold, pendingDelete
blacklist_checkIP blacklist / DNSBL check — Spamhaus, Barracuda, SpamCop, SORBS, and more
whois_lookupParsed WHOIS data — registrar, expiry, domain age, nameservers, EPP status
http_checkHTTP/HTTPS reachability — status codes, redirect chain, HSTS, HTTP→HTTPS redirect
zone_axfrAXFR zone transfer vulnerability check — tests if any NS allows public zone transfers
dane_validateDANE/TLSA validation — cross-validates TLSA records against live TLS certificate

Example prompts

My emails are going to spam for example.com — token is YOUR_TOKEN
Did my DNS changes propagate yet for example.com? token: YOUR_TOKEN
Run a full security audit on example.com, token YOUR_TOKEN
Is the SSL cert for example.com about to expire? token YOUR_TOKEN
We're migrating example.com to a new host next week — are the TTLs safe? token YOUR_TOKEN
What subdomains does example.com have exposed? token YOUR_TOKEN
Are any of example.com's IPs on a blacklist? token YOUR_TOKEN
Get WHOIS info for example.com — token YOUR_TOKEN
Is example.com reachable over HTTPS? token YOUR_TOKEN
Check if example.com is vulnerable to zone transfers — token YOUR_TOKEN
Validate DANE/TLSA records for example.com — token YOUR_TOKEN

Architecture

Claude Desktop / Cursor / Windsurf
        │
        │  MCP over SSE
        ▼
mcp.softricks.net          ← Railway (always-on Python/FastMCP server)
        │
        │  HTTPS
        ▼
api.softricks.net/idig     ← AWS Lambda (iDig REST API)
        │
        │  DNS queries
        ▼
Live DNS infrastructure

Self-hosting

Clone this repo and deploy your own instance:

git clone https://github.com/kbhave/MCP-Service-iDig
cd MCP-Service-iDig
pip install -r requirements.txt
python mcp_server.py

Or deploy to Railway in one click — connect your GitHub repo and Railway handles the rest.

Requirements:

  • Python 3.11+
  • mcp==1.26.0
  • httpx

Related


License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.