ssl-expiry-checker-mcp
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ssl_expiry_checkerA | |
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 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clearly defined and distinct.
With a single tool, naming is inherently consistent. The name 'ssl_expiry_checker' is descriptive and follows a clear pattern.
The server has only one tool, which is minimal for its domain. While it serves a focused purpose, it falls short of the typical 3-15 tool range for a well-scoped server.
The single tool covers the core functionality of checking SSL certificate expiry for a given URL. However, it lacks additional tools for batch checks, certificate details, or alerting, which would enhance completeness.