SSL Monitor MCP Server
Related Servers
Alternatives to SSL Monitor MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceProvides comprehensive tools for real-time DNS queries across 53 record types, global propagation checks, and SSL certificate analysis. It also enables domain security scans for SPF/DKIM/DMARC configurations and HTTP uptime monitoring.858 npm23Apache 2.0
- AlicenseAqualityCmaintenanceDomain intelligence for DNS, WHOIS/RDAP, SSL/TLS, subdomain discovery, availability, valuation, email security, and typosquatting and brand protection.11MIT
- -licenseNot gradedqualityNot gradedmaintenanceEnables ethical security testing and attack surface management through SSL certificate validation, CVE queries, subdomain enumeration, security header analysis, and comprehensive reconnaissance capabilities. Designed for authorized penetration testing workflows with responsible disclosure practices.-
- FlicenseNot gradedqualityDmaintenanceEnables domain intelligence lookups including RDAP registration data, DNS records, and Certificate Transparency searches.1-
- AlicenseNot gradedqualityBmaintenanceEnables domain intelligence lookups including current and historical WHOIS, reverse WHOIS by registrant info, and DNS record retrieval through the WhoisXML API.245 npmMIT
- AlicenseAqualityFmaintenanceProvides comprehensive domain research tools including RDAP, WHOIS, and DNS lookup capabilities, with automatic fallback and support for 50+ TLDs.19 npm1MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one retrieves domain registration and expiration details via WHOIS/RDAP, while the other focuses on SSL certificate information for a host and port. There is no overlap in functionality, making it easy for an agent to select the appropriate tool based on the task.
Both tools follow a consistent verb_noun pattern with 'get_' as the prefix, followed by a descriptive noun phrase (domain_info, ssl_cert_info). This uniformity makes the tool set predictable and easy to understand.
With only two tools, the server feels thin for a monitoring purpose, as it lacks operations like checking SSL expiration alerts, updating or deleting monitored domains, or listing multiple domains. A more comprehensive monitoring server would typically include more tools to cover core workflows.
The tool set is severely incomplete for an SSL monitoring domain. It only provides read-only information (get_domain_info and get_ssl_cert_info) without any management capabilities such as adding domains to monitor, setting up alerts, or handling SSL renewal processes. This leaves significant gaps that could cause agent failures in automated monitoring tasks.