Boring Utils Expiry Watch
Server Details
Check a site's TLS certificate and its domain registration expiry. Read-only, no sign-in.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 2 tools
check_certificate targets TLS certificates on port 443 while check_domain_expiry targets RDAP registration records at the registry; these are different data sources and failure modes. The descriptions reinforce the split, so an agent can pick the right one without hesitation.
Both tools use the same check_<noun> snake_case convention, with check_domain_expiry adding a qualifier rather than changing style. Predictable and readable.
Two tools is thin, sitting right at the borderline for a server framed as a general 'utils expiry watch'. However, the scope is genuinely narrow (two expiry sources), so there is no obvious padding or bloat.
The two main expiry vectors an operator watches — TLS certificates and domain registrations — are both covered with rich detail (chain, AIA renewal windows, RDAP statuses). Gaps are minor: no batch/multi-domain checking and no way to persist or schedule watches, but agents can work around these by looping calls.
Available Tools
2 toolscheck_certificateCheck a TLS certificateARead-onlyIdempotentInspect
Connects to a domain on port 443 and reports its TLS certificate: whether it is trusted and matches the name, the issuer, the expiry date and days left, the lifetime, the chain and the TLS version, what each of its server addresses serves (up to 4 IPv4 and 4 IPv6), and, for certificates from Let’s Encrypt, Google Trust Services, ZeroSSL or Sectigo, the renewal window the CA suggests (ACME Renewal Information).
Inputs: domain (required).
check_domain_expiryCheck a domain registration expiryARead-onlyIdempotentInspect
Looks up a domain registration over RDAP at the registry for its TLD: when it expires, the registrar, the statuses (flagging a hold, redemption, pending delete or pending transfer) and the nameservers. Subdomains are looked up by their registered domain (www.example.co.uk becomes example.co.uk).
Inputs: domain (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Check SSL certificate and domain expiry for any site, see plans, and get a monitoring sign-up link.
Free anonymous website, DNS, email and TLS checks, plus monitor read and opt-in write access.
Inspects live IPv4/IPv6 DNS resolution, TLS certificate issuer/expiry, and HTTP security grade.
Inspects live IPv4/IPv6 DNS resolution, TLS certificate issuer/expiry, and HTTP security grade.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceRead-only observation of a single live URL: parses static HTML to report security posture, forms, links, accessibility signals, and leaks, with described fixes. SSRF-gated and safe, never executes JavaScript.123 npmMIT
- AlicenseAqualityBmaintenanceEnables live website health checks including TLS, HTTPS, and security headers, returning an A-F grade with specific fixes.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables live TLS/SSL certificate health checks for any hostname, providing expiry, hostname match, trust verdict, and a health score. Supports both free and paid deep tiers with protocol/cipher analysis.MIT
- AlicenseNot gradedqualityCmaintenanceEnables an AI agent to check whether a site is healthy and configured correctly by reading TLS certificates and classifying handshake failures, resolving DNS records from raw wire packets, tracing HTTP redirects and timings, and grading security headers with exact fixes. Every connection passes through an SSRF guard that vets and pins addresses so the agent cannot be aimed at internal networks.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.