This server provides domain registration information and SSL certificate monitoring capabilities.
• Get domain registration details: Retrieve registration date, expiration date, registrar name, registrant information (when available), and domain status using WHOIS lookup. • Monitor SSL certificates: Obtain certificate validity periods (valid from/to dates), issuer, subject, current validity status, and days until expiry for any domain, with optional port specification (defaults to 443).
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@SSL Monitor MCP Server check SSL certificate for google.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
Name: sslmon
URL: https://sslmon.dev/mcp
# 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/mcpMac/Linux:
# Add to Claude Desktop
claude mcp add sslmon -- npx -y sslmon-mcpWindows:
# Add to Claude Desktop
claude mcp add sslmon -- cmd /c npx -y sslmon-mcp{
"mcpServers": {
"sslmon": {
"command": "npx",
"args": ["-y", "sslmon-mcp"],
"env": {}
}
}
}[mcp_servers.sslmon]
command = "npx"
args = ["-y", "sslmon-mcp"]Related MCP server: nslookup.io MCP Server
🔍 Domain Registration Info - Get domain registration and expiration dates
🔒 SSL Certificate Info - Check SSL certificate validity periods and details
get_domain_infoGet 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_infoGet 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
sslmon-cli — Standalone CLI binary (Go) for domain WHOIS and SSL certificate queries, ideal for shell scripts and CI/CD pipelines.
Get domain registration, expiration, and daysUntilExpiry using WHOIS/RDAP.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | The top-level domain to check (e.g., sslmon.dev) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the data sources (WHOIS/RDAP) but fails to describe critical behaviors such as rate limits, authentication requirements, error handling, or response format. For a read operation with external dependencies, this lack of detail is a significant gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that front-loads the key information (what data is retrieved and how). There is no wasted verbiage or redundancy, making it highly concise and well-structured for quick comprehension.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (involving external WHOIS/RDAP lookups) and the absence of both annotations and an output schema, the description is insufficient. It does not explain the return values, error conditions, or operational constraints, leaving the agent under-informed about how to interpret results or handle failures.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage, with the single parameter 'domain' clearly documented in the schema. The description does not add any additional meaning or examples beyond what the schema provides (e.g., it doesn't elaborate on domain format or validation). Thus, it meets the baseline of 3 where the schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Get') and the specific information retrieved ('domain registration, expiration, and daysUntilExpiry'), along with the method ('using WHOIS/RDAP'). It distinguishes from the sibling tool 'get_ssl_cert_info' by focusing on domain metadata rather than SSL certificates. However, it doesn't explicitly contrast with the sibling, so it falls short of a perfect 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives like the sibling 'get_ssl_cert_info', nor does it mention any prerequisites or exclusions. It simply states what the tool does without contextual usage advice, leaving the agent to infer based on tool names alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get SSL certificate information for a host and port.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | The domain to check SSL certificate for (e.g., www.sslmon.dev) | |
| port | No | Port number to check (default: 443) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It states what the tool does but fails to describe key behaviors such as network connectivity requirements, error handling, rate limits, or the format and content of the returned certificate information. This leaves significant gaps for an agent to understand operational constraints.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and appropriately sized for a simple tool, with no wasted information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what certificate information is returned (e.g., issuer, expiry, validation status), potential errors, or dependencies like network access. For a tool that likely involves external queries and returns structured data, this omission reduces its usefulness for an agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with both parameters ('domain' and 'port') well-documented in the schema. The description mentions 'host and port' but adds no additional meaning beyond what the schema provides, such as examples of valid domains or port usage beyond the default. This meets the baseline for high schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Get SSL certificate information') and the target ('for a host and port'), which is specific and unambiguous. However, it doesn't explicitly differentiate from the sibling tool 'get_domain_info', which might provide overlapping or related information about domains.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives like 'get_domain_info'. It lacks context about use cases, prerequisites, or exclusions, leaving the agent to infer usage based solely on the tool name and parameters.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.0.0get_domain_info2 fields changedInput schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#"Input schema / additionalPropertiesAdded value: +falseget_ssl_cert_info4 fields changedInput schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#"Input schema / additionalPropertiesAdded value: +falseInput schema / properties / port / exclusiveMinimumAdded value: +0Input schema / properties / port / typePrevious value: -"number"New value: +"integer"get_domain_infoget_ssl_cert_infoThe 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.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
DNS lookups, health reports, SSL certs, security scans, GEO scoring, uptime checks
Domain intelligence for DNS, WHOIS/RDAP, TLS, reputation, valuation, and brand protection.
SSL/TLS scanning, free Let's Encrypt issuance, and certificate-expiry monitoring.
Domain availability over RDAP, watchlists with daily checks, change history and email alerts.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/firesh/sslmon-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
