SSL Monitor MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_domain_infoC | Get domain registration, expiration, and daysUntilExpiry using WHOIS/RDAP. |
| get_ssl_cert_infoC | Get SSL certificate information for a host and port. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.