ShieldDNS MCP server
OfficialRelated Servers
Alternatives to ShieldDNS MCP server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents and apps to check URLs, domains, IP addresses, phone numbers, emails, crypto wallets, IBANs, mobile apps, and payment handles for scam, phishing, and fraud risk, returning verdicts, probabilities, facts, and reason codes.MIT
- AlicenseNot gradedqualityCmaintenanceProvides AI agents with zero-cost, zero-dependency trust evaluation for domains, URLs, wallets, APIs, and IPs, returning a 0-100 score with SSL, DNS, WHOIS, security header, and content sub-scores, plus batch comparison to rank multiple targets.MIT
- AlicenseAqualityCmaintenanceEnables AI agents to check URL safety before fetching content, using Google Web Risk, URLhaus, PhishTank, and AI analysis to return SAFE/SUSPICIOUS/DANGEROUS verdicts.169 npm1MIT

HTTPfyofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to run read-only network and domain diagnostics without an account or API key, covering DNS lookups and propagation, SPF/DKIM/DMARC and BIMI/MTA-STS email authentication checks, TLS certificates and CAA, WHOIS, IP/ASN and blacklist data, plus ping, traceroute and port checks from internet-facing servers. It also produces graded domain health and full DNS reports with reasons and fixes for each failed check.MIT- AlicenseAqualityCmaintenanceEnables AI agents to inspect any public domain’s web technology stack, email deliverability and DNS health (MX, SPF, DKIM, DMARC, MTA-STS, TLS-RPT, BIMI), and HTTPS security posture with typed JSON scores and remediation-ready findings, plus history, bulk checks, monitoring alerts, and reverse technology lookups.12476 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to perform cybersecurity analysis including RDAP lookup, DNS analysis, SSL inspection, security header detection, and more, returning structured security reports.-
TDQS
Scored across 3 tools
check_domain and resolve are mostly distinct: one gives a safety verdict and advice, the other returns DNS records and resolution metadata. There is some overlap because resolve also reports threat blocking and DNSSEC status, so an agent may occasionally hesitate between them.
The names mix conventions: check_domain is verb_noun, resolve is a bare verb, and service_status is noun_noun. They remain readable and understandable, but the set does not follow a predictable pattern.
Three tools fit the server's focused scope of domain safety checking, DNS resolution, and node status. The surface is small but each tool has a clear role, though it sits at the lower bound of a comfortable set.
The core lifecycle is covered: safety verdicts, raw DNS resolution with DNSSEC and blocking info, and node status. Minor gaps exist, such as no bulk domain check or blocklist/configuration inspection, but the main workflows are supported.