{
  "markdown": "# iDig DNS MCP Server\n\nA remote MCP server exposing **19 professional DNS diagnostic tools** from the [iDig API](https://api.softricks.net/idig/docs) \n— built by Kedar Bhave ( [Softricks](https://softricks.net) ).\n\nConnect 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.\n\n**Live endpoint:** `https://mcp.softricks.net/sse`\n\n---\n\n## Quickstart\n\n### Claude Desktop\n\nEdit `~/Library/Application Support/Claude/claude_desktop_config.json`:\n\n```json\n{\n  \"mcpServers\": {\n    \"idig-dns\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"mcp-remote\",\n        \"https://mcp.softricks.net/sse\"\n      ]\n    }\n  }\n}\n```\n\nRestart Claude Desktop. You'll see **idig-dns** appear under Connectors.\n\n### Cursor / Windsurf\n\nAdd to your MCP settings:\n\n```json\n{\n  \"mcpServers\": {\n    \"idig-dns\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"mcp-remote\",\n        \"https://mcp.softricks.net/sse\"\n      ]\n    }\n  }\n}\n```\n\n### Authentication\n\nAll tools require a `token` parameter. Get your token at [api.softricks.net/idig/docs](https://api.softricks.net/idig/docs).\n\n---\n\n## Tools\n\n| Tool | Description |\n|---|---|\n| `dns_lookup` | Look up any DNS record type: A, AAAA, MX, NS, TXT, SOA, CAA, SRV, CNAME, DS, TLSA, HTTPS, SVCB |\n| `resolve_check` | Resolution diagnostics — returns ok / nxdomain / servfail / timeout / degraded |\n| `diagnose` | Full diagnosis combining resolution + DNSSEC — start here when something is broken |\n| `email_security_audit` | SPF, DKIM, DMARC, and BIMI audit with A–F grade and prioritized fix recommendations |\n| `mx_check` | MX health + provider detection (Google Workspace, M365, Proofpoint, 35+ providers) |\n| `dnssec_validate` | DNSSEC chain of trust — returns secure / insecure / bogus / indeterminate |\n| `dnssec_health` | Key inventory, signature expiry, algorithm assessment, rollover readiness |\n| `propagation_check` | Check propagation across 16 global resolvers: Google, Cloudflare, Quad9, China, Korea, Russia |\n| `ssl_check` | Certificate validity, expiry countdown, domain match, issuer, chain completeness |\n| `ttl_check` | TTL advisory with step-by-step migration lowering plan |\n| `zone_consistency` | Compare all authoritative nameservers — catches lame delegation and SOA mismatches |\n| `subdomain_discover` | Probe 75 common subdomains + crt.sh Certificate Transparency logs — surfaces exposed dev/staging environments |\n| `geo_lookup` | Geolocation, ISP, ASN, CDN detection, hosting flag |\n| `domain_status` | EPP registrar lock status — transfer-ready, delete lock, serverHold, pendingDelete |\n| `blacklist_check` | IP blacklist / DNSBL check — Spamhaus, Barracuda, SpamCop, SORBS, and more |\n| `whois_lookup` | Parsed WHOIS data — registrar, expiry, domain age, nameservers, EPP status |\n| `http_check` | HTTP/HTTPS reachability — status codes, redirect chain, HSTS, HTTP→HTTPS redirect |\n| `zone_axfr` | AXFR zone transfer vulnerability check — tests if any NS allows public zone transfers |\n| `dane_validate` | DANE/TLSA validation — cross-validates TLSA records against live TLS certificate |\n\n---\n\n## Example prompts\n\n```\nMy emails are going to spam for example.com — token is YOUR_TOKEN\n```\n```\nDid my DNS changes propagate yet for example.com? token: YOUR_TOKEN\n```\n```\nRun a full security audit on example.com, token YOUR_TOKEN\n```\n```\nIs the SSL cert for example.com about to expire? token YOUR_TOKEN\n```\n```\nWe're migrating example.com to a new host next week — are the TTLs safe? token YOUR_TOKEN\n```\n```\nWhat subdomains does example.com have exposed? token YOUR_TOKEN\n```\n```\nAre any of example.com's IPs on a blacklist? token YOUR_TOKEN\n```\n```\nGet WHOIS info for example.com — token YOUR_TOKEN\n```\n```\nIs example.com reachable over HTTPS? token YOUR_TOKEN\n```\n```\nCheck if example.com is vulnerable to zone transfers — token YOUR_TOKEN\n```\n```\nValidate DANE/TLSA records for example.com — token YOUR_TOKEN\n```\n\n---\n\n## Architecture\n\n```\nClaude Desktop / Cursor / Windsurf\n        │\n        │  MCP over SSE\n        ▼\nmcp.softricks.net          ← Railway (always-on Python/FastMCP server)\n        │\n        │  HTTPS\n        ▼\napi.softricks.net/idig     ← AWS Lambda (iDig REST API)\n        │\n        │  DNS queries\n        ▼\nLive DNS infrastructure\n```\n\n---\n\n## Self-hosting\n\nClone this repo and deploy your own instance:\n\n```bash\ngit clone https://github.com/kbhave/MCP-Service-iDig\ncd MCP-Service-iDig\npip install -r requirements.txt\npython mcp_server.py\n```\n\nOr deploy to Railway in one click — connect your GitHub repo and Railway handles the rest.\n\n**Requirements:**\n- Python 3.11+\n- `mcp==1.26.0`\n- `httpx`\n\n---\n\n## Related\n\n- **iDig REST API docs:** https://api.softricks.net/idig/docs\n- **DNS Doctor AI Agent:** https://agent.softricks.net\n- **iOS App:** https://apps.apple.com/us/app/softricks-idig/id522550738\n\n---\n\n## License\n\nMIT",
  "bytes": 5008,
  "sha": "54d640ac8e3820890e6854da24a3e5b2fe6b3e72ad779dc69c211b4399b73372",
  "repo_slug": "kbhave/mcp-service-idig",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_net_softricks_idig_dns_3f81357e/readme"
}