Skip to main content
Glama
Sign In
vps-ops-mcp

vps-ops-mcp

by Akdag94
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

SSL certificate status

ssl_status

Verify TLS certificate expiry dates for server domains. Auto-discovers domains from nginx configs or checks a specific domain using openssl s_client.

Instructions

Checks TLS certificate expiry dates. Without domain, auto-discovers domains from the server's nginx configs and checks each one (max 20). Read-only; runs openssl s_client on the server itself, so it also works for internal-only DNS.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "host": "<host>"
    },
    "name": "ssl_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesSSH host alias from ~/.ssh/config, or user@hostname
domainNoCheck a single specific domain instead of auto-discovering

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. It discloses read-only operation via openssl s_client, server-side execution, and auto-discovery limit of 20 domains. Could mention output format.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with purpose, every word earns its place. No wasted verbiage.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Good given no output schema, but lacks description of output format (list of domains with expiry dates? any warnings?). Adequate but could be more complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage 100% (baseline 3). Description clarifies 'host' as SSH alias and 'domain' as override for auto-discovery, adding meaning beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it checks TLS certificate expiry dates, specifies auto-discovery vs explicit domain, and is distinct from sibling tools like security_audit or server_health.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Describes when to use with/without domain, mentions internal DNS capability, but doesn't explicitly compare to sibling security_audit or state when not to use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools