SSL Monitor MCP Server
# Domain/HTTPS/SSL MCP Server
[](https://modelcontextprotocol.io/) [](https://www.npmjs.com/package/sslmon-mcp) [](https://opensource.org/licenses/MIT) [](https://nodejs.org/)
**Languages:** [English](README.md) | [中文](README-zh.md) | [日本語](README-ja.md)
A Model Context Protocol (MCP) server that provides domain registration information and SSL certificate monitoring capabilities. Perfect for security monitoring, domain management, and certificate lifecycle tracking.
<a href="https://glama.ai/mcp/servers/@firesh/sslmon-mcp">
<img width="380" height="200" src="https://glama.ai/mcp/servers/@firesh/sslmon-mcp/badge" alt="SSL Monitor Server MCP server" />
</a>
## 🚀 Quick Start
### HTTP (Remote MCP server)
- **Name:** `sslmon`
- **URL:** `https://sslmon.dev/mcp`
```bash
# Claude Code
claude mcp add -t http sslmon https://sslmon.dev/mcp
# Gemini CLI
gemini mcp add -t http sslmon https://sslmon.dev/mcp
# Qwen Code
qwen mcp add -t http sslmon https://sslmon.dev/mcp
# Codex
codex mcp add sslmon --url https://sslmon.dev/mcp
```
### NPX (Local MCP server)
Mac/Linux:
```bash
# Add to Claude Desktop
claude mcp add sslmon -- npx -y sslmon-mcp
```
Windows:
```bash
# Add to Claude Desktop
claude mcp add sslmon -- cmd /c npx -y sslmon-mcp
```
### Configuration (Local MCP server)
```JSON
{
"mcpServers": {
"sslmon": {
"command": "npx",
"args": ["-y", "sslmon-mcp"],
"env": {}
}
}
}
```
```toml
[mcp_servers.sslmon]
command = "npx"
args = ["-y", "sslmon-mcp"]
```
## ✨ Features
- 🔍 **Domain Registration Info** - Get domain registration and expiration dates
- 🔒 **SSL Certificate Info** - Check SSL certificate validity periods and details
## 🛠️ Available Tools
### `get_domain_info`
Get domain registration and expiration information.
**Parameters:**
- `domain` (string, required): The top-level domain to check (e.g., "example.com")
**Returns:** JSON object with:
- `domain`: The queried domain
- `registrationDate`: Domain registration date
- `expirationDate`: Domain expiration date
- `registrar`: Domain registrar name
- `registrant`: Domain registrant information (when available)
- `status`: Domain status
- `daysUntilExpiry`: Number of days until domain expires
### `get_ssl_cert_info`
Get SSL certificate information and validity status for any domain.
**Parameters:**
- `domain` (string, required): The domain to check SSL certificate for
- `port` (number, optional): Port number to check (default: 443)
**Returns:** JSON object with:
- `domain`: The queried domain
- `validFrom`: Certificate valid from date (ISO string)
- `validTo`: Certificate valid to date (ISO string)
- `issuer`: Certificate issuer
- `subject`: Certificate subject
- `isValid`: Boolean indicating if certificate is currently valid
- `daysUntilExpiry`: Number of days until certificate expires
## Related Projects
- [sslmon-cli](https://github.com/firesh/sslmon-cli) — Standalone CLI binary (Go) for domain WHOIS and SSL certificate queries, ideal for shell scripts and CI/CD pipelines.
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.